amazon/amazon-ecs-local-container-endpoints pulls statistics

Amazon ECS Local Container Endpoints

This image provides local versions of the ECS Task IAM Roles Endpoint and the ECS Task Metadata Endpoints. This image will help you test applications locally before you deploy to Fargate & ECS.

The source code for this image is available on GitHub.

Benefits of using ECS Local Container Endpoints

ECS Local Container Endpoints supports three endpoints for your local application container: • The Task IAM Roles Endpoint • The Task Metadata V2 Endpoint • The Task Metadata V3 Endpoint

If your application code interacts with any of these endpoints when deployed to Fargate or ECS, this image can help you to run and test your application locally against local versions of these endpoints. For example, your application might use the Task IAM Roles Endpoint (likely through one of the AWS SDKs) to obtain credentials for interacting with other AWS services, or it might query one of the Task Metadata Endpoints to determine the container's Docker ID or to log Docker stats. Without ECS Local Container Endpoints, you might need to deploy to Fargate or ECS just to test changes you are making to this code. When you connect your local containers to the ECS Local Container Endpoints, your application code can use these endpoints and you can test any changes locally.

See the post on the AWS Compute blog for more examples of how ECS Local Container Endpoints can help with local development.

Getting started with ECS Local Container Endpoints

We recommend using Docker Compose to start and connect your application containers with the ECS Local Container Endpoints. To get started, see the example Compose file on GitHub.

For other options for starting and connecting to the ECS Local Container Endpoints, as well as a full list of configuration options, see the README on GitHub.