A Terraform module for creating and managing AWS Route53 hosted zones, DNS records, and DNSSEC configurations.
terraform-aws-route53 is a Terraform module that automates the creation and management of AWS Route53 DNS resources. It provides a declarative way to define hosted zones, DNS records with advanced routing policies, DNSSEC configurations, and cross-account VPC associations. The module solves the problem of manually configuring complex DNS setups through the AWS console or writing repetitive Terraform code.
DevOps engineers, SREs, and cloud infrastructure teams managing DNS on AWS who want to implement infrastructure-as-code practices for their Route53 configurations.
Developers choose this module because it's part of the trusted terraform-aws-modules ecosystem, reduces boilerplate Terraform code, supports advanced Route53 features like DNSSEC and complex routing policies, and follows AWS best practices. It's maintained by experienced contributors and widely used in production environments.
Terraform module to create AWS Route53 resources 🇺🇦
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports all AWS Route53 routing types—geolocation, weighted, failover, latency, and more—as shown in the detailed example code with multiple policy configurations.
Simplifies DNSSEC enablement by automatically creating and managing KMS keys for signing, reducing manual security setup steps.
Facilitates private hosted zone associations across AWS accounts using vpc_association_authorizations, essential for multi-account cloud architectures.
Includes sub-modules for delegation sets and resolver resources, plus extensive input variables for customization while following Terraform best practices.
Changing the ignore_vpc parameter requires manual Terraform state moves, which can be error-prone and lead to disruptive zone recreation if not handled carefully.
The module's feature-rich design adds unnecessary complexity for simple DNS needs, making it harder to onboard teams with limited Terraform or Route53 experience.
Tightly coupled with AWS Route53, so it's not suitable for multi-cloud DNS management or migrating to other DNS providers without significant rework.