Aws Ecs V2

Amazon ECS is AWS's managed container orchestration — simpler than Kubernetes (EKS) with less operational overhead, while still covering the full container lifecycle. Services run long-lived containers with auto-restart and load balancer integration; Tasks run containers once to completion (like AWS Fargate, but ECS manages the lifecycle). For agents: RegisterTaskDefinition defines container config; RunTask starts a one-off task; CreateService deploys a persistent service; UpdateService triggers a rolling deploy with a new image. boto3 is the standard Python interface — all ECS operations are synchronous API calls with async execution. Confidence is docs-derived.

ECS API via boto3 (Python). ecs.register_task_definition(family, containerDefinitions=[{name, image, cpu, memory, portMappings, environment, logConfiguration}], requiresCompatibilities, networkMode, executionRoleArn). ecs.run_task(cluster, taskDefinition, launchType="FARGATE", networkConfiguration={awsvpcConfiguration:{subnets,securityGroups}}, overrides={containerOverrides:[{name,environment,command}]}). ecs.create_service(cluster, serviceName, taskDefinition, desiredCount, launchType, networkConfiguration, loadBalancers). ecs.update_service(cluster, service, taskDefinition, desiredCount) — triggers rolling deployment. ecs.describe_tasks(cluster, tasks=[taskArn]) — retrieves task status and exit codes. ecs.list_services(cluster) — lists all services. ecs.describe_services(cluster, services) — service health + deployment status.

IAM-based auth: SigV4 request signing via boto3. IAM roles: ecs:RunTask, ecs:RegisterTaskDefinition, ecs:CreateService, ecs:UpdateService, ecs:DescribeTasks, iam:PassRole. Task execution role (ecsTaskExecutionRole): allows ECS to pull ECR images, inject secrets from SSM/Secrets Manager, write CloudWatch logs. Task role: IAM role assumed by container code (access AWS services from container). Instance role: EC2-specific (not needed for Fargate launch type). VPC: ECS tasks need subnets with connectivity (public IP or NAT for internet access).

Async model: RunTask/CreateService return immediately; task/service transitions asynchronously. Monitor via describe_tasks() or ECS events on EventBridge. Task exit codes: containerDefinitions[*].exitCode in describe_tasks response. Service deployment: ecs.update_service waits for new tasks to pass health checks before terminating old tasks (rolling). Stopped task reasons: stoppedReason field — diagnose launch failures. CloudWatch Logs: configure awslogs log driver in task definition for container stdout. ECS uptime tied to AWS infrastructure (99.99% SLA). Service circuit breaker: automatic rollback if new deployment fails health checks.

docs.aws.amazon.com/AmazonECS covers task definition reference, service management, networking setup, and IAM permissions. Getting started: AWS free tier, create ECS cluster (Fargate or EC2), register task definition, run first task via boto3 in under 15 minutes. boto3 ecs client: pip install boto3. AWS CLI: aws ecs run-task. CDK/Terraform for IaC (aws_ecs_service). Community via AWS re:Post and Stack Overflow (amazon-ecs tag). ECS is mature with extensive documentation and community resources.