A web application runs on several EC2 instances.
Incoming requests should be distributed to healthy targets.
Which AWS capability fits this purpose?
Elastic Load Balancing provides a common endpoint, distributes requests across targets, and can use health checks when routing.
Detailed explanation
Route 53 provides DNS functions and does not inspect HTTP request bodies.
Route 53 provides DNS functions and does not inspect HTTP request bodies.
CloudTrail records API activity and does not perform application request distribution.
CloudTrail records API activity and does not perform application request distribution.
Artifact supplies compliance documents and does not perform load balancing or health checks.
Artifact supplies compliance documents and does not perform load balancing or health checks.
A load balancer distributes client requests and can route only to healthy registered targets.
A load balancer distributes client requests and can route only to healthy registered targets.
Check official documentation
Compare the following points with the official documentation.
Elastic Load BalancingのApplication Load Balancer公式概要でtarget、health check、distributionを確認する。
What to confirm
ロードバランサーをトラフィック分散とターゲット正常性確認の機能として説明できる。
Key points
- Elastic Load Balancing
- Target
- Health check
Notes
- Environment: AWS公式Elastic Load Balancingドキュメントの確認
- Confirm current AWS service behavior and pricing conditions in the official documentation.
Foundation review
Traffic distribution
A load balancer hides target changes behind a stable client endpoint.
Health-aware routing
Failed targets can be removed from new request routing based on health checks.