Interface EC2TaskDefinitionArgs

interface EC2TaskDefinitionArgs {
    container?: Container;
    containers?: Record<string, Container>;
    executionRole?: any;
    family?: any;
    logGroup?: any;
    networkMode?: any;
    placementConstraints?: any;
    proxyConfiguration?: any;
    tags?: any;
    taskRole?: any;
    volumes?: any;
    vpc?: classic.ec2.Vpc;
}

Properties

container?: Container

Single container to make a TaskDefinition from. Useful for simple cases where there aren't multiple containers, especially when creating a TaskDefinition to call [run] on.

Either [container] or [containers] must be provided.

containers?: Record<string, Container>

All the containers to make a TaskDefinition from. Useful when creating a Service that will contain many containers within.

Either [container] or [containers] must be provided.

executionRole?: any

The 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 role will be created.

family?: any

An optional family name for the Task Definition. If not specified, then a suitable default will be created.

logGroup?: any

Log 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.

networkMode?: any

The Docker networking mode to use for the containers in the task. The valid values are none, bridge, awsvpc, and host.

placementConstraints?: any

A set of placement constraints rules that are taken into consideration during task placement. Maximum number of placement_constraints is 10.

proxyConfiguration?: any

The proxy configuration details for the App Mesh proxy.

tags?: any

Key-value mapping of resource tags

taskRole?: any

IAM 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 role will be created.

volumes?: any

A set of volume blocks that containers in your task may use.

The 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