//
Search across all documentation pages
8 pages in this section.
Where ECS and Fargate fit versus EKS: ECS is AWS's own container orchestrator, Fargate is its serverless compute mode, and together they run containers without a Kubernetes control plane to operate.
Hands-on ECS basics: create a cluster, register a Fargate task definition, run a one-off task with awsvpc networking, then list, describe, and stop tasks in both SDKs.
Register ECS task definitions via SDK: valid Fargate CPU/memory pairs, awsvpc networking, the awslogs driver, environment variables, and injecting secrets from Secrets Manager and SSM.
Expose ECS services via SDK: register tasks with an ALB target group (IP target type for Fargate), and enable internal service-to-service discovery with AWS Cloud Map serviceRegistries.
Open a shell inside a running Fargate task via SDK: enable ExecuteCommand on the task or service, grant the task role SSM messaging permissions, and run interactive or one-off commands with ExecuteCommand.
The ECS and Fargate SDK habits that keep deployments safe and bills low: right-size tasks, enable the deployment circuit breaker, set health-check grace periods, inject secrets safely, use Fargate Spot, and clean up.