Task metadata endpoint. For more information, see Task Metadata Endpoint version 3 or Task Metadata Endpoint version 2. The following is an example output from a task that runs as part of a service (MyService). 4. These endpoints expose valuable information about running tasks and containers. . From the container, you can use curl followed by the task meta data endpoint to query the endpoint for example curl $ {ECS_CONTAINER_METADATA_URI_V4}/task. The task metadata version 2 endpoint is no longer being actively maintained. I want to troubleshoot metadata errors that I receive when I use AWS Software Development Kits (AWS SDK) in my Amazon Elastic Container Service (Amazon ECS) for AWS Fargate tasks. We recommend that you update the task metadata version 4 endpoint to get the latest metadata endpoint information. We will not remove any existing metadata or change the metadata field names. 0, an environment variable named ECS_CONTAINER_METADATA_URI_V4 is injected into each container in a task. As accessing the endpoint programmatically involves a few steps, I've created wrapper in Go, which will send a request to the task metadata endpoint, and deserialize the response into a struct. Amazon ECS provides earlier versions of the task metadata endpoint. Jul 31, 2020 · Depending on the Fargate or ECS container agent version you're using, you will be able to access different versions of the metadata endpoint. To avoid the need to create new task metadata endpoint versions in the future, additional metadata may be added to the version 4 output. The task metadata endpoint version 4 functions like the version 3 endpoint but provides additional network metadata for your containers and tasks. These are the only en 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. The following examples show sample outputs from the task metadata endpoints for Amazon ECS tasks run on AWS Fargate. Aug 20, 2023 · It says on the docs that: Beginning with Fargate platform version 1. Jan 13, 2025 · To enhance the usability and manageability of tasks running on ECS, AWS provides metadata endpoints. Example container metadata response If your Amazon ECS task is hosted on Amazon EC2, you can also access task host metadata using the Instance Metadata Service (IMDS) endpoint. When querying the $ {ECS_CONTAINER_METADATA_URI_V4} endpoint you are returned only metadata about the container itself. Task metadata endpoint The Amazon ECS container agent injects an environment variable into each container, referred to as the task metadata endpoint which provides various task metadata and Docker stats to the container. When a container queries the metadata endpoint, the container agent can determine which task the container belongs to based on its unique IP address, and metadata and stats for that task are returned. 0, the task metadata version 3 and 2 endpoint are supported. Additional network metrics are available when querying the /stats endpoints as well. Jul 20, 2020 · For tasks using the Fargate launch type and platform versions prior to 1. Oct 7, 2022 · Today, Amazon Elastic Container Service (Amazon ECS) has announced the availability of additional metadata attributes for tasks running on Amazon EC2 capacity. The following command, when run from within the instance hosting the task, lists the ID of the host instance. You can now use the Amazon ECS task metadata endpoint to retrieve the service name of a task as well as the Amazon VPC ID of Amazon EC2 instance that the task is running on. fhrpmu mjqr umpyw fyfig pkcbz qykuc vsc fwewbe znajx llklkrh