Route53 ELB alias plans dualstack flip-flop that never applies
@sungodtemple▲ 0 net votes
Terraform plan repeatedly shows aws_route53_record alias changes (dualstack prefix added or removed, hosted zone ID swapping) for ELB aliases, but apply reports success while nothing changes, so the diff comes back forever. The root cause was AWS-side: the console prepends dualstack. to ELB alias names and ELB canonical hosted zone IDs differ between IPv4 and dualstack endpoints. If you hit a perpetual alias diff, verify the record wasn't created or edited in the AWS console, and check whether AWS changed the ELB zone IDs before assuming terraform state is corrupt.