Skip to content
Nubent

/Glossary · AWS

What is Amazon ECS?

Amazon ECS (Elastic Container Service) is the fully managed AWS container orchestrator. It runs and scales containers on AWS Fargate, with no servers to manage, or on EC2 instances, with no control plane to maintain.

How Amazon ECS works

You write a task definition with the container image, CPU, memory, environment variables and permissions. An ECS service keeps the desired number of tasks running, registers them with an Application Load Balancer and replaces them if they fail. Auto scaling adjusts the task count based on CloudWatch metrics.

With Fargate, AWS manages capacity and you pay per second for vCPU and memory. With EC2, you control instance types, GPUs or local storage, using capacity providers to scale the cluster. ECS Service Connect simplifies service-to-service communication, and deployments can be rolling or blue/green with automatic rollback.

When Amazon ECS makes sense

ECS fits when you want to run containers in production with as little operational overhead as possible and your team does not need Kubernetes-specific tooling. It is a very solid choice for APIs, web applications, queue workers and scheduled jobs, especially paired with Fargate.

If your organization already has Kubernetes experience, needs multi-cloud portability or depends on specific operators, Amazon EKS may be a better fit. Many companies run most services on ECS and save EKS for the cases that truly justify it.

Best practices and common mistakes

Give each service its own task role with least privilege, store secrets in Secrets Manager or Parameter Store, turn on Container Insights and define realistic health checks. Use Fargate Spot for interruption-tolerant workloads and Graviton for better price-performance.

Common mistakes: overprovisioning CPU and memory just in case and overpaying, sharing one IAM role across every service, using the latest tag on images, and not configuring the deployment circuit breaker, which leaves services stuck in a restart loop with no rollback.

/FAQ

Questions about Amazon ECS

Another question? Write to hello@nubent.com and an engineer will answer.

Does ECS have an additional cost?

There is no charge for the ECS orchestrator itself. You pay for the resources your tasks use: vCPU and memory on Fargate, or the cluster's EC2 instances, plus load balancers, storage and data transfer. Compute Savings Plans apply to both Fargate and EC2.

Should I run ECS on Fargate or EC2?

Fargate removes server management and is a great fit for most workloads. EC2 makes sense when you need GPUs, specific instance types, a lot of local storage, or high container density where the per-instance cost ends up lower than Fargate.

Can I migrate from ECS to EKS later?

Yes. The container images are the same, so the migration means translating task definitions and services into Kubernetes manifests, plus adjusting networking, permissions and pipelines. With solid infrastructure as code, it is a well-scoped project.

Next step

What should we build next on AWS?

30 minutes with an engineer. Concrete next steps, whether or not you work with us.