aws-containers

To deploy a container to AWS Fargate, configure an ECS service using awsvpc networking mode, attach it to an Application Load Balancer, and set deployment safety knobs like health check grace periods and circuit breaker rollback to ensure safe traffic routing.

ECS Fargate image pull failures in private subnets usually stem from missing VPC endpoints for ECR, incorrect execution role permissions for ecr:GetAuthorizationToken, or restrictive security groups blocking Docker registry traffic.

Configure blue green deployments for ECS services by enabling the deployment circuit breaker with rollback, setting proper health check configurations, and using ALB target group swapping to shift traffic only after new tasks pass health checks.

Exit code 137 on ECS Fargate indicates an Out of Memory (OOM) error where the container exceeded its allocated memory limit; fix it by increasing the task memory reservation or optimizing the container's memory usage.

Manage ECR lifecycle policies for multi-arch images by targeting untagged manifests carefully, as lifecycle rules can accidentally delete manifest list references; apply tag-based rules to preserve multi-arch build artifacts.