(ecs): add a name prop to ContainerDefinition

When creating a ContainerDefinition resource, it’s not currently possible to specify its name. It seems the current behavior is to use the object’s id as name, but that’s not documented and can lead to surprising behavior.

My suggestion is to add a new optional prop name that maps directly to CfnTaskDefinition.ContainerDefinitionProperty.Name.

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request

[MrArnoldPalmer]

Sounds good to me! thanks for providing more context, always helps.

[CarlosDomingues]

@MrArnoldPalmer my use case is to configure AppMeshProxyConfiguration. In my understanding it expects a container_name prop (at least in Python) that indicates explicitly in which container an envoy proxy will be instantiated.

I was getting an error after changing my ContainerDefinition id. Then I realized those two were related.

CDK discourages naming things explicitly

Sure. Another use case, though: for developers, trying to debug applications by searching the UI for id-like container names and logs isn’t a lot fun. Of course you could use pretty names for a resource id, but then you run into limitations such as id having to be unique within the scope it’s being created. I guess my point is: identifiers that are useful when looking to cloud architecture aren’t necessarily useful for those looking at UI / application.