On this page, you will learn find a step-by-step guide on how to connect your AWS API Gateway to APIIDA´s Boomi's API Control Plane step-by-step.
Prerequisites
The following is required to proceedTo proceed, you will need the following:
A running instance of APIIDA´s Boomi´s API Control Plane
Access to the Amazon API Gateway Service with at least one API deployed in a stage
Docker to use utilize the image of our agent (that , which acts as an intermediary).
Any other container environment is also possible. Helm Charts are available here:
https://github.com/apiida/CPagent-Helm
...
Excerpt | ||
---|---|---|
| ||
Create a new EnvironmentTo get started, simply open your API Control Plane instance and follow the instructions below. Add an Environment
Add Environment Information
You’ve completed the first step! |
...
The following describes how to create the gateway configuration for an AWS API Gateway Agent.
Gateway Configuration
...
Use AWS Internal Access:
You can choose this option if you plan to run the agent container within AWS (ECS or EKS).
...
accessKey
/secretAccessKey
: Insert your AWS access keys
...
region
: Insert the region that is assigned to your APIs in AWS
...
You have two options to grant your agent access to your AWS API Gateway, depending on whether you plan to host the agent inside AWS itself or elsewhere.
Agents running outside AWS
This is the default, where you run the agent container outside of AWS, e.g. inside your local network or within another cloud provider. For the agent to be able to access the AWS API Gateway, you must provide credentials in form of Access Key and Secret Access Key.
...
Agents running inside AWS
For agents running within one of the AWS container services (e.g. ECS or EKS) and pointing to AWS API Gateway you can choose to 'Use AWS Internal Access' instead of providing explicit credentials. This eliminates the storing or transmission of gateway credentials by the agent - Hence tighter security.
In this case you must configure a Task IAM Role for your container in AWS which has the necessary permissions to access the API Gateway.
Here is the documentation from Amazon describing the process:
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-iam-roles.html
...
Use AWS Internal Access:
Enable this if you intend to run your agent container inside AWS and want to use a Task IAM Role instead of providingaccessKey
andsecretAccessKey
.accessKey
/secretAccessKey
: Id and secret access key of an AWS long-term access key for programmatic access.region
: The region in which your AWS API Gateway is hosted.stage
: The stage to which your APIs are deployed in AWS.
Info |
---|
See our Q&A below if you want to learn more about how to get these values. |
...
Excerpt | ||
---|---|---|
| ||
Check the Agent's Status
Admin Portal
You’ve completed the last step! You can now interact with your Gateways through APIIDA´s Boomi´s API Control Plane. Try it right now and discover your APIs! 💡 Tip: It is easy to add more agents! Repeat this guide or that of another gateway and simply add the agents to the existing Docker compose file. |
...