Amazon Route 53 Profiles

With Route 53 Profiles, you can apply and manage DNS-related Route 53 configurations across many VPCs and in different Amazon Web Services accounts. Profiles make managing the DNS settings for many VPCs as easy as managing them for a single VPC and when you update a Profile, its settings are propagated to all the VPCs associated to the Profile. You can also share a Profile with Amazon Web Services accounts in the same Regions by using Amazon RAM. The currently Route 53 supported resources you can associate to a Profile are:

Some of the VPC configurations are directly managed on the Profile. The configurations are:

For example, you can enable the DNS Firewall failure mode configuration for all the VPCs the Profile is associated to, but keep the VPC's existing DNSSEC validation configuration.

You can also use Amazon CloudFormation to set up consistent DNS settings for newly provisioned VPCs.

You can associate one Profile per VPC and the number of resources you can associate per Profile varies. For more information, see Quotas on Route 53 Profiles .

How Route 53 Profile settings are prioritized

You can have the local DNS settings and associations set for Profiles for migration, or other testing purposes. When a DNS query matches both the Resolver rule for a private hosted zone that is directly associated with the VPC and a Resolver rule for a private hosted zone that is associated to the Profile, the local DNS settings take precedence. When DNS query is made for a conflicting domain name, the most specific one wins. The following table includes examples of the evaluation order:

Route 53 Profiles Region availability

Route 53 Profiles are available in most commercial Amazon Web Services Regions. The following table provides a list of the current availability.