The number of targets differs between Availability Zones.
Distribute requests from the load balancer without letting placement differences create a large skew.
Which feature should be considered?
Consider cross-zone load balancing so a load balancer can distribute requests across targets in multiple Availability Zones.
Detailed explanation
Cross-zone load balancing distributes traffic across targets in multiple Availability Zones.
Cross-zone load balancing distributes traffic across targets in multiple Availability Zones.
IAM roles authorize actions and do not perform HTTP load balancing.
IAM roles authorize actions and do not perform HTTP load balancing.
Sending traffic to unhealthy targets reduces availability and does not correct placement skew safely.
Sending traffic to unhealthy targets reduces availability and does not correct placement skew safely.
S3 bucket policies do not control load-balancer target distribution.
S3 bucket policies do not control load-balancer target distribution.
Check official documentation
Compare the following points with the official documentation.
Elastic Load Balancing cross-zone load balancingの公式説明を確認する。
What to confirm
AZ配置とターゲット分散の関係を説明できる。
Key points
- Cross-zone load balancing
- Target
- Availability Zone
Notes
- Environment: AWS公式ELBドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Placement and distribution
Different target counts by zone can skew traffic unless distribution spans the relevant zones.
Health is separate
Health checks remove unusable targets but do not by themselves equalize placement differences.