Skip to content

Route53 DNS hosted zones

aws-service aws-service Route53 Considerations

  • Route53 private hosted zone will have associations with VPCs on different AWS organization accounts
  • Route53 should ideally be hosted in the Shared account, although sometimes Route53 is already deployed in a Legacy account where it can be imported and fully supported as code.
  • Route53 zero downtime migration (active-active hosted zones) is completely possible and achievable with Leverage terraform code

leverage-aws-dns

Figure: AWS Organization shared account Route53 DNS diagram. (Source: Cristian Southall, "Using CloudFormation Custom Resources to Configure Route53 Aliases", Abstractable.io Blog post, accessed November 18th 2020).