Build an application service that keeps serving as its servers change. Use the official AWS CLI in Terminal and AWS View to connect native resource state with actual HTTP responses.
Four guided labs build the skills in order:
- Route requests through an Application Load Balancer (ALB) to two servers.
- Detect an unhealthy target, observe traffic exclusion and restore service.
- Use a launch template and Auto Scaling group to replace a failed server.
- Execute scaling policies to move between two and three serving instances and test capacity bounds.
An independent troubleshooting challenge combines these skills: investigate a new server missing from traffic, restore application-aware health and return to two healthy servers. Complete the guided labs first.
Prerequisites: VPC subnets and access rules, EC2, SSH and User Data from the preceding AWS VPC and AWS EC2 and EBS courses. New load balancing and scaling concepts are explained near their first use.
Learning environment: Each unit starts in a fresh browser-based Linux environment with prepared dependencies and application fixtures. Follow the resource scope, verify functionality before cleanup and preserve the environment connection. The practical work uses ALB and controlled SimpleScaling execution; NLB is a comparison topic. CPU-based target tracking and physical availability-zone resilience are outside the practical scope.
These exercises can support AWS certification preparation for load balancing, health checks and compute availability. Use them alongside your chosen exam objectives; this course does not cover a complete exam syllabus.
