Aws Ecs Container Metadata

The task metadata and network rate stats are sent to cloudwatch container insights and can be viewed in the aws management console.

Aws ecs container metadata.

Welcome to part 3 of this blog post series on how to use amazon efs with amazon ecs and aws fargate. By enabling this feature you can query the information about a task container and container instance from within the container or the host container instance. Task metadata endpoint version 2 available for amazon ecs tasks on aws fargate that use platform version 1 1 0 or later and tasks that are launched on amazon ec2 infrastructure that use the awsvpc network mode and are running at least version 1 17 0 of the amazon ecs container agent. All containers belonging to tasks that are launched with the awsvpc network mode receive a local ipv4 address within a predefined link local address range.

You should not use your production credentials locally if you provide the ecs local endpoints with an aws profile that has access to your production account then your application will be able to. You can use the curl command from within the container instance to query the amazon ecs container agent port 51678 and return container instance metadata or task information. Beginning with version 1 15 0 of the amazon ecs container agent various container metadata is available within your containers or the host container instance. The metadata file is created on the host instance and mounted in the.

Your container will now be running and will be using temporary credentials obtained from your default aws command line interface profile. Short description if you run containers in an amazon ec2 instance it s a best practice for security reasons to avoid allowing your applications to assume an instance role. Amazon ec2 container service amazon ecs now allows applications running in containers to directly access metadata about their environment. Previously if an application running in a container managed by amazon ecs required access to information about its environment you needed to manually call this metadata using the docker or amazon ecs.

For reference these are the blog posts in this series. This blog provides the background about the need for this integration its scope and provides a high level view of the use cases. I want to prevent containers from accessing amazon elastic compute cloud amazon ec2 instance metadata in amazon elastic container service amazon ecs. To test your container locally run.