Amazon ECS and AWS Fargate now allow resources tagging
You can now tag your Amazon Elastic Container Service (Amazon ECS) and AWS Fargate resources such as services, task definitions, tasks, clusters, and container instances . This will enable you to better allocate cost, improve visibility into your workloads, easily search and identify your containerized applications, implement programmatic infrastructure management actions, and define fine-grained resource-level permissions.
Many ECS customers are managing thousands of resources such as task definitions, services, tasks, and clusters, spread across different teams, products, business units, and environments. Without tagging, it was difficult to manage the entire infrastructure and the underlying cost in a systematic manner. Now, you can tag your ECS resources at creation or at runtime using the ECS APIs and Console. Customers using the AWS Fargate launch-type can now easily allocate the cost of their ECS Tasks using tags. For customers using the EC2 launch-type, ECS now provides detailed ECS Tasks usage data in the Cost & Usage Report, which customers can use to allocate the cost of the underlying EC2 instances.
To take advantage of tagging, you will need to opt-in to the new Amazon Resource Names (ARN) and resource identifiers (ID) format for tasks, container instances, and services. These new ARNs and IDs are necessary to introduce the new tagging functionality and all its underlying benefits.
Additional information about the new ARN and ID formats can be found in the FAQ and documentation. You can also read our post to learn more about moving to new ARN and ID. If you have questions, please reach out to your account team or contact AWS Support on the community forums or through AWS Premium Support. To opt in, visit the ECS page of your AWS console. Resource tagging is currently not available in the GovCloud (US-East) region.
You can now tag your Amazon Elastic Container Service (Amazon ECS) and AWS Fargate resources such as services, task definitions, tasks, clusters, and container instances . This will enable you to better allocate cost, improve visibility into your workloads, easily search and identify your containerized applications, implement programmatic infrastructure management actions, and define fine-grained resource-level permissions.
Many ECS customers are managing thousands of resources such as task definitions, services, tasks, and clusters, spread across different teams, products, business units, and environments. Without tagging, it was difficult to manage the entire infrastructure and the underlying cost in a systematic manner. Now, you can tag your ECS resources at creation or at runtime using the ECS APIs and Console. Customers using the AWS Fargate launch-type can now easily allocate the cost of their ECS Tasks using tags. For customers using the EC2 launch-type, ECS now provides detailed ECS Tasks usage data in the Cost & Usage Report, which customers can use to allocate the cost of the underlying EC2 instances.
To take advantage of tagging, you will need to opt-in to the new Amazon Resource Names (ARN) and resource identifiers (ID) format for tasks, container instances, and services. These new ARNs and IDs are necessary to introduce the new tagging functionality and all its underlying benefits.
Additional information about the new ARN and ID formats can be found in the FAQ and documentation. You can also read our post to learn more about moving to new ARN and ID. If you have questions, please reach out to your account team or contact AWS Support on the community forums or through AWS Premium Support. To opt in, visit the ECS page of your AWS console. Resource tagging is currently not available in the GovCloud (US-East) region.