Internet-facing load balancer lacks proven health-aware DNS routing

What it checks

Load balancer: no relevant Route53 record proves health-aware routing with an alternate-routing policy.

Where it applies

Terraform: aws_lb, aws_alb

CloudFormation: AWS::ElasticLoadBalancingV2::LoadBalancer

How to fix it

1. Verify each relevant record target, health_check_id or evaluate_target_health, and routing policy. Configure a compatible alternate endpoint when DNS failover is required; test all-unhealthy behavior.

Frameworks

• AWS Well-Architected REL.7

These mappings are advisory, not an attestation of compliance.

Vendor documentation

All rules