Page Comparison

...

Excerpt
name Create a new Environment
Create a new Environment To get started, simply open your API Control Plane instance and follow the instructions below. Add an Environment Navigate to “Environments” in the menu on the left side Click on the “Create New Environment” button in the top right corner Choose your provider by clicking on it Confirm by clicking on the "Next" button Add Environment Information Fill in Complete the form (as exemplarily shown below)below following the example below: Confirm by clicking on the "Register Environment" button Click Next here to start the Connection Wizard. You’ve completed the first step!

...

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 AcessAccess' 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 execution role Task IAM Role for your container in AWS that 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 execution role Task IAM Role instead of providing accessKey and secretAccessKey.

• 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.

...