AWS Route 53 Zone Association

aws_route53_zone_association (Terraform)

The Zone Association in Route 53 can be configured in Terraform with the resource name aws_route53_zone_association. The following sections describe 2 examples of how to use the resource and its parameters.

Example Usage from GitHub

dhlee011/AWS_Terraform

resource "aws_route53_zone_association" "seoul_attch" {
  zone_id = aws_route53_zone.seoul_zone.zone_id
  vpc_id  = aws_vpc.seoul.id
}

Polina-DevOps/Terraform-Mutable

resource "aws_route53_zone_association" "zone-associate" {
  zone_id       = var.INTERNAL_DNS_ZONE_ID
  vpc_id        = aws_vpc.main.id

Parameters

• id optional computed - string
• owning_account optional computed - string
• vpc_id required - string
• vpc_region optional computed - string
• zone_id required - string

Explanation in Terraform Registry

Manages a Route53 Hosted Zone VPC association. VPC associations can only be made on private zones. See the aws_route53_vpc_association_authorization resource for setting up cross-account associations.

NOTE: Unless explicit association ordering is required (e.g., a separate cross-account association authorization), usage of this resource is not recommended. Use the vpc configuration blocks available within the aws_route53_zone resource instead. NOTE: Terraform provides both this standalone Zone VPC Association resource and exclusive VPC associations defined in-line in the aws_route53_zone resource via vpc configuration blocks. At this time, you cannot use those in-line VPC associations in conjunction with this resource and the same zone ID otherwise it will cause a perpetual difference in plan output. You can optionally use the generic Terraform resource lifecycle configuration block with ignore_changes in the aws_route53_zone resource to manage additional associations via this resource.