Optional
cpuThe number of cpu units used by the task. If not provided, a default will be computed based on the cumulative needs specified by [containerDefinitions]
Optional
executionThe execution role that the Amazon ECS container agent and the Docker daemon can assume.
If undefined
, a default will be created for the task. If null
, no task will be created.
Optional
familyAn optional family name for the Task Definition. If not specified, then a suitable default will be created.
Optional
inferenceConfiguration block(s) with Inference Accelerators settings. Detailed below.
Optional
ipcThe IPC resource namespace to be used for the containers in the task The valid values are host
, task
, and none
.
Optional
logLog group for logging information related to the service. If undefined
a default instance
with a one-day retention policy will be created. If null
, no log group will be created.
Optional
memoryThe amount (in MiB) of memory used by the task. If not provided, a default will be computed based on the cumulative needs specified by [containerDefinitions]
Optional
networkThe Docker networking mode to use for the containers in the task. The valid values are
none
, bridge
, awsvpc
, and host
.
Optional
pidThe process namespace to use for the containers in the task. The valid values are host
and task
.
Optional
placementA set of placement constraints rules that are taken into consideration during task placement.
Maximum number of placement_constraints
is 10
.
Optional
proxyThe proxy configuration details for the App Mesh proxy.
A set of launch types required by the task. The valid values are EC2
and FARGATE
.
Optional
tagsKey-value mapping of resource tags
Optional
taskIAM role that allows your Amazon ECS container task to make calls to other AWS services. If
undefined
, a default will be created for the task. If null
, no task will be created.
Optional
volumesA set of volume blocks that containers in your task may use.
Optional
vpcThe vpc that the service for this task will run in. Does not normally need to be explicitly provided as it will be inferred from the cluster the service is associated with.
Generated using TypeDoc
All the containers to make a ClusterTaskDefinition from. Useful when creating a ClusterService that will contain many containers within.
Either [container] or [containers] must be provided.