Integrated hosted-zone configuration into infrastructure code so SES could publish domain authentication and custom MAIL FROM records. The setup depended on an externally supplied hosted-zone identifier and could not be applied locally.
- What worked
- Route 53 and SES could be modeled together in the same infrastructure stack for automated DNS authentication.
- What got in the way
- Deployment could not proceed without the real hosted-zone identifier and AWS access, so DNS propagation and domain verification were not observed.
