Working with 64-bit ARM workloads on Amazon ECS - Amazon Elastic Container Service
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China.

Working with 64-bit ARM workloads on Amazon ECS

Amazon ECS supports using 64-bit ARM applications. You can run your applications on the platform powered by Amazon Graviton2 processors,which is suitable for a wide variety of workloads, including application servers, micro-services, high-performance computing, CPU-based machine learning inference, video encoding, electronic design automation, gaming, open-source databases, and in-memory caches.


Before you begin deploying task definitions which use the 64-bit ARM architecture, be aware of the following considerations:

  • The applications can use the Fargate or EC2 launch types.

  • The applications can only use the Linux operating system.

  • For the Fargate type, the applications must use Fargate platform version 1.4.0 or later .

  • The applications can use Fluent Bit or CloudWatch for monitoring.

  • For the Fargate launch type, the following Regions do not support 64-bit ARM workloads:

    • US East (N. Virginia) , the use1-az3 Availability Zone

    • China (Beijing)

    • China (Ningxia)

    • Africa (Cape Town)

    • Middle East (Bahrain)

    • Amazon GovCloud (US-East)

    • Amazon GovCloud (US-West)

    • In Asia Pacific (Osaka), the apne3-az2 and apne3-az3 Availability Zones

  • For the Amazon EC2 launch type, see the following to verify that your Region supports the instance type you want to use:

    You can also use the Amazon EC2 describe-instance-type-offerings command with a filter to view the instance offering for your Region.

    aws ec2 describe-instance-type-offerings --filters Name=instance-type,Values=instance-type --region region

    The following example checks for the M6 instance type availability in the us-east-1 Region.

    aws ec2 describe-instance-type-offerings --filters Name=instance-type,Values=M6 --region us-east-1

    For more information, see describe-instance-type-offerings in the Amazon EC2 Command Line Reference.

Specifying the ARM architecture in your task definition

To take advantage of the ARM architecture, specify ARM64 for the cpuArchitecture task definition parameter.

The following shows the JSON format for the ARM architecture in a task definition:

{ "runtimePlatform": { "operatingSystemFamily": "LINUX", "cpuArchitecture": "ARM64" }, ... }

The following example is a task definition for the ARM architecture that displays "hello world".

{ "family": "arm64-testapp", "networkMode": "awsvpc", "containerDefinitions": [ { "name": "arm-container", "image": "arm64v8/busybox", "cpu": 100, "memory": 100, "essential": true, "command": [ "echo hello world" ], "entryPoint": [ "sh", "-c" ] } ], "requiresCompatibilities": [ "FARGATE" ], "cpu": "256", "memory": "512", "runtimePlatform": { "operatingSystemFamily": "LINUX", "cpuArchitecture": "ARM64" }, "executionRoleArn": "arn:aws:iam::123456789012:role/ecsTaskExecutionRole" }

Interfaces for Configuring ARM

You can configure the ARM CPU architecture for Amazon ECS task definitions using any of the following interfaces:

  • New Amazon ECS console

  • Amazon Command Line Interface (Amazon CLI)

  • Amazon SDKs

  • Amazon Copilot