This message was deleted.

We don’t have a type definition in the AWS provider (although the names are the same as in the official AWS docs: https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ContainerDefinition.html) If types were really important, you could create your task definitions using the AWS Native provider which do have strongly typed container definitions. Providers can be used together as generally the outputs are ARNs or IDs

thanks for info 🙂

You probably could but we can’t ensure that this type is going to stay consistent with what’s in the AWS provider. The AWS native one is probably more reliable

well in the non-native it's just a string, so was thinking something like:

const conatinerDefs: TaskDefinitionContainerDefinition[] = [...];
new aws.ecs.TaskDefinition("myTaskDef, {
  containerDefinitions: JSON.stringify(containerDefs)
  ...

That should work yes

This works well so far. FWIW: the decalration for me looks like this:

const containerDefinitions: aws_native.types.input.ecs.TaskDefinitionContainerDefinitionArgs[] = [...]