The hability of the ECS Agent tag the instance that it's running in with the ECS Cluster ARN and ECS Container Instance ID.
Description
On a cluster with 3000+ instances split on 30+ clusters to identify where a Task was placed, mainly on AWS Batch side.
1 Container instance can only be placed in 1 cluster only and will have only 1 valid ID it's nonsense to not have such feature so you could relate the resources Backwards to the cluster.
The API for checking the container instance requires the cluster so If you do have the container ID and +30 cluster you need todo a try and error to find out the cluster that it belongs too.
I don't know why such feature as ENABLE and DISABLE being DISABLE as default never was implemented.
rupertbg
commented
1 year ago
Summary
The hability of the ECS Agent tag the instance that it's running in with the ECS Cluster ARN and ECS Container Instance ID.
Description
On a cluster with 3000+ instances split on 30+ clusters to identify where a Task was placed, mainly on AWS Batch side.
1 Container instance can only be placed in 1 cluster only and will have only 1 valid ID it's nonsense to not have such feature so you could relate the resources Backwards to the cluster.
The API for checking the container instance requires the cluster so If you do have the container ID and +30 cluster you need todo a try and error to find out the cluster that it belongs too.
I don't know why such feature as ENABLE and DISABLE being DISABLE as default never was implemented.