ECS: Declaration vs Execution

Launch type declares compatibility; capacity providers actually run the tasks

ECS: Declaration vs Execution Launch type declares compatibility; capacity providers actually run the tasks Capacity providers - mix in a cluster, not in one strategy Task Definition · requiresCompatibilities = declaration · Architecture component Task Definition requiresCompatibilities = declaration ECS Service / Task · what you deploy · Architecture component ECS Service / Task what you deploy Capacity Provider Strategy · one kind per strategy · Architecture component Capacity Provider Strategy one kind per strategy FARGATE / FARGATE_SPOT · auto-created, AWS-owned infra · Capacity providers - mix in a cluster, not in one strategy FARGATE / FARGATE_SPOT auto-created, AWS-owned infra ECS Managed Instances · your account, AWS patches, GPU OK · Capacity providers - mix in a cluster, not in one strategy ECS Managed Instances your account, AWS patches, GPU OK Auto Scaling Group · self-managed EC2 · Capacity providers - mix in a cluster, not in one strategy Auto Scaling Group self-managed EC2 Spot Fleet · capacity provider only - no launch type · Capacity providers - mix in a cluster, not in one strategy Spot Fleet capacity provider only - no launch type compatibility only actual execution serverless managed EC2 self-managed spot pools Legend Backend Cloud External

Architecture diagram • Built with Archify • Create yours ↗ • Hover to trace • R route • Click to focus • +/− zoom • M radar • T theme • E export