Every resilient AWS workload rests on this layer — EC2, Auto Scaling Groups, load balancers, and Lambda are the compute primitives engineering teams at fintechs and e-commerce platforms rely on to handle traffic spikes without manual intervention. Getting auto-scaling configuration wrong is one of the most common causes of both production cost spikes and availability incidents.
What This Pillar Covers
- EC2 and instance types — On-Demand, Reserved, and Spot instances; right-sizing for real workloads
- Auto Scaling Groups — dynamic and predictive scaling policies, lifecycle hooks, health checks
- Elastic Load Balancing — ALB, NLB, and CLB; target groups and health-check tuning
- AWS Lambda — serverless compute, triggers, concurrency limits, and cold-start mitigation
- ECS and Fargate — task definitions, service scheduling, and capacity providers
Who This Is For
Cloud engineers and DevOps engineers designing AWS architectures that need to scale predictably, self-heal from instance failure, and stay within a fixed compute budget.