Deploy containers on Amazon ECS with AWS Graviton processors
Introduction
Deploy containers using ECS on AWS Graviton processors
Deploy ECS containers on AWS Graviton processor using Terraform
Next Steps
Deploy containers on Amazon ECS with AWS Graviton processors
Who is this for?
This is an introductory topic for developers who want to use AWS Graviton processors with Amazon Elastic Container Service (ECS).
What will you learn?
Upon completion of this Learning Path, you will be able to:
- Create an Amazon ECS cluster with Fargate and AWS Graviton processors
- Create and run an Amazon ECS task
- Use Terraform to automate deployment of an ECS cluster
Prerequisites
Before starting, you will need the following:
- An AWS account
- A computer with Docker, AWS CLI, and Terraform installed
Summary
This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
You’ll deploy a containerized application on Amazon ECS with AWS Fargate and Graviton processors. You’ll create an ECS cluster and task, run it on Arm-based AWS Fargate infrastructure, and then automate the workflow with Terraform. The Terraform configuration creates an Amazon Elastic Container Registry (ECR) repository and deploys an NGINX task to ECS on Graviton.
Frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
No. Fargate is a serverless option for ECS, so you don’t manually provision or maintain EC2 instances.
The task should start on the Fargate cluster and show a running status in ECS. That confirms the container runs on AWS Graviton-backed infrastructure.
Create an Amazon ECR repository and use it as the source for images referenced by your ECS task. This lets ECS pull the image when the task starts.
It automates the same deployment steps by defining AWS resources such as an ECR repository and ECS components to run an NGINX task on Fargate with AWS Graviton processors.
Verify that the cluster and task definition target the Fargate launch type and that required AWS resources and permissions from earlier steps exist. Also check that the container image is available in the ECR repository you created.