AWSAmazon Route 53Networking

aws_route53_zone_association cost estimation

A zone association is free. It attaches a VPC to a private hosted zone so the VPC can resolve its records. Cost comes from the hosted zone and its query volume, not the association.

An aws_route53_zone_association attaches an additional VPC to a Route 53 private hosted zone, letting resources in that VPC resolve the zone's private DNS records. It is used when a private hosted zone must serve more than one VPC, or VPCs in different accounts. The association itself is free, and you can associate many VPCs with a zone without a per-association charge.

The cost is on the private hosted zone, not the association. A private hosted zone carries the standard $0.50/month hosted zone fee, and queries against it are billed at about $0.40 per million per month, the same as public zones. Attaching more VPCs does not add a fixed fee; it can raise query volume because more resources now resolve against the zone, but that is usage-based, not a charge for the association.

There is nothing to optimize on the association itself. The cost management happens at the zone level: consolidating private DNS into fewer zones to avoid paying the $0.50/month fee repeatedly, and being aware that broadly shared private zones can accumulate query volume. c3x prices the hosted zone and its query volume and treats VPC associations as free.

Terraform example

A minimal but realistic configuration that C3X can estimate.

resource "aws_route53_zone_association" "secondary" {
  zone_id = aws_route53_zone.internal.zone_id
  vpc_id  = aws_vpc.secondary.id
}

Pricing dimensions

What you actually pay for when you provision aws_route53_zone_association.

DimensionUnitWhat's being charged
Zone associationfreeAttaching a VPC to a private hosted zone has no charge.
$0
Private hosted zoneper zone-monthThe zone the VPC is associated with carries the standard hosted zone fee.
~$0.50/month per zone
DNS queriesper millionQueries from associated VPCs against the zone are billed per million.
~$0.40 per million

Optimization tips

Common ways to reduce aws_route53_zone_association cost without changing the workload.

Consolidate private DNS into fewer zones

~$0.50/month per zone avoided

Each private hosted zone carries a $0.50/month fee. Associating multiple VPCs with one shared zone is cheaper than maintaining a separate zone per VPC.

Associate only the VPCs that need resolution

The association is free, but broadly attaching VPCs raises query volume against the zone. Attach only VPCs that actually resolve the private records.

Reuse one zone across accounts

Cross-account association lets several accounts share one private hosted zone, avoiding duplicate zones and their per-zone fees.

FAQ

Does a Route 53 zone association cost money?

No. Associating a VPC with a private hosted zone is free. You pay the $0.50/month hosted zone fee and per-million query charges on the zone itself, not for the association.

Does attaching more VPCs to a private zone raise the fee?

There is no per-association fee. Attaching more VPCs can increase query volume against the zone, which is billed per million, but the association adds no fixed cost.

Is a private hosted zone billed differently from a public one?

No. Both carry the same $0.50/month zone fee and about $0.40 per million query charge. The association resource that connects a VPC to a private zone is free.

Related resources

Estimate this resource in your own Terraform

Free, open source, no API key. C3X parses your Terraform and shows line-item cost for every resource, including aws_route53_zone_association.