What is the difference between the task role and the execution role?

The execution role is used by the ECS agent to pull container images, push logs, and retrieve secrets during task startup. The task role is assumed by your application code running inside the container to call AWS services like S3, DynamoDB, or SQS.

Which CPU and memory combinations are valid for Fargate?

Fargate supports specific CPU/memory combinations. For example, 0.25 vCPU supports 0.5-2 GB memory, 0.5 vCPU supports 1-4 GB, 1 vCPU supports 2-8 GB, 2 vCPU supports 4-16 GB, and 4 vCPU supports 8-30 GB. The tool enforces these valid combinations.

Can I use this for EC2 launch type tasks?

Yes. The builder supports both Fargate and EC2 launch types. EC2 launch type tasks have additional options like network mode selection (bridge, host, awsvpc) and placement constraints that are not available with Fargate.

AWS ECS Task Definition Builder

ComputeAWS

Generate ECS task definition JSON with containers, resources, and volumes.

ECS Configuration

Generate ECS task definition JSON with containers, resources, and volumes.

Required Fields

familynetworkModerequiresCompatibilitiesrequiresCompatibilities[0]cpu

Generated Output

Output will appear here...

About This Tool

The ECS Task Definition Builder provides a guided form for constructing Amazon ECS task definitions. Task definitions are the blueprint for running containers on ECS and include settings for container images, CPU and memory allocation, port mappings, environment variables, logging, IAM roles, and more. This tool generates valid JSON task definitions that work with both Fargate and EC2 launch types, helping you avoid common mistakes in this complex configuration.

When to Use This Tool

•Build a Fargate task definition with proper CPU and memory combinations, container port mappings, and CloudWatch Logs configuration.
•Configure multi-container task definitions with sidecar patterns like log routers, service mesh proxies, or monitoring agents.
•Generate task definitions with proper IAM task roles and execution roles for pulling images from ECR and accessing AWS services.
•Create task definitions with health check configurations, restart policies, and secrets references from Secrets Manager or SSM Parameter Store.

Frequently Asked Questions

What is the difference between the task role and the execution role?: The execution role is used by the ECS agent to pull container images, push logs, and retrieve secrets during task startup. The task role is assumed by your application code running inside the container to call AWS services like S3, DynamoDB, or SQS.
Which CPU and memory combinations are valid for Fargate?: Fargate supports specific CPU/memory combinations. For example, 0.25 vCPU supports 0.5-2 GB memory, 0.5 vCPU supports 1-4 GB, 1 vCPU supports 2-8 GB, 2 vCPU supports 4-16 GB, and 4 vCPU supports 8-30 GB. The tool enforces these valid combinations.
Can I use this for EC2 launch type tasks?: Yes. The builder supports both Fargate and EC2 launch types. EC2 launch type tasks have additional options like network mode selection (bridge, host, awsvpc) and placement constraints that are not available with Fargate.

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.

AWS ECS Task Definition Builder

ComputeAWS

Generate ECS task definition JSON with containers, resources, and volumes.

ECS Configuration

Generate ECS task definition JSON with containers, resources, and volumes.

Required Fields

familynetworkModerequiresCompatibilitiesrequiresCompatibilities[0]cpu

Generated Output

Output will appear here...

About This Tool

When to Use This Tool

•Build a Fargate task definition with proper CPU and memory combinations, container port mappings, and CloudWatch Logs configuration.
•Configure multi-container task definitions with sidecar patterns like log routers, service mesh proxies, or monitoring agents.
•Generate task definitions with proper IAM task roles and execution roles for pulling images from ECR and accessing AWS services.
•Create task definitions with health check configurations, restart policies, and secrets references from Secrets Manager or SSM Parameter Store.

Frequently Asked Questions

What is the difference between the task role and the execution role?: The execution role is used by the ECS agent to pull container images, push logs, and retrieve secrets during task startup. The task role is assumed by your application code running inside the container to call AWS services like S3, DynamoDB, or SQS.
Which CPU and memory combinations are valid for Fargate?: Fargate supports specific CPU/memory combinations. For example, 0.25 vCPU supports 0.5-2 GB memory, 0.5 vCPU supports 1-4 GB, 1 vCPU supports 2-8 GB, 2 vCPU supports 4-16 GB, and 4 vCPU supports 8-30 GB. The tool enforces these valid combinations.
Can I use this for EC2 launch type tasks?: Yes. The builder supports both Fargate and EC2 launch types. EC2 launch type tasks have additional options like network mode selection (bridge, host, awsvpc) and placement constraints that are not available with Fargate.