AWS Security ChangesHomeSearch

AWS Route53: Route 53 Profiles: multiple VPC associations with priority ordering

Service: Route53 · 2026-11-10 · Documentation medium

File: Route53/latest/DeveloperGuide/profiles.md · Type: network

Summary

Documents that up to two Profiles can be associated to a VPC, each with a priority (100-9900), and explains how VPC Resolver evaluates Resolver rules, private hosted zones, DNS Firewall rule groups, query logging configurations, and DNSSEC validation settings across prioritized Profile associations.

Security assessment

The added text specifies the evaluation order for DNS Firewall rule groups, DNSSEC validation configuration, and query logging across multiple Profile associations, which determines which security controls actually apply to a VPC's DNS queries. It is feature/behavior documentation rather than a fix for a specific vulnerability, but it has direct security-control implications (a lower-priority Profile's firewall rules are not evaluated).

Evidence

+  * **Resolver DNS Firewall rule groups** – DNS Firewall evaluates the rule groups that are associated directly to the VPC together with the rule groups in the highest priority Profile association that has a rule that matches the query. The rule group priority determines the evaluation order, and a rule group that is associated directly to the VPC takes precedence over a Profile rule group that has the same rule group priority. DNS Firewall doesn't evaluate rule groups in the remaining Profiles for that query.

Diff

diff --git a/Route53/latest/DeveloperGuide/profiles.md b/Route53/latest/DeveloperGuide/profiles.md
index 6873e68..d7f225a 100644
--- a//Route53/latest/DeveloperGuide/profiles.md
+++ b//Route53/latest/DeveloperGuide/profiles.md
@@ -45 +45 @@ You can also use CloudFormation to set up consistent DNS settings for newly prov
-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](./DNSLimitations.html#limits-api-entities-route53-profiles).
+You can associate up to two Profiles to a VPC. Each association between a Profile and a VPC has a _priority_ , a value from 100 to 9900. A lower value means a higher priority. VPC Resolver evaluates the Profiles that are associated to a VPC in priority order. For more information, see How Route 53 Profile settings are prioritized. The number of resources you can associate per Profile varies. For more information, see [Quotas on Route 53 Profiles](./DNSLimitations.html#limits-api-entities-route53-profiles).
@@ -56,0 +57,25 @@ marketing.example.com |  None |  marketing.example.com |  Local VPC
+When more than one Profile is associated to a VPC, each association has a _priority_ , a value from 100 to 9900. A lower value means a higher priority. VPC Resolver evaluates the Profiles in priority order, starting with the association that has the lowest priority value:
+
+  * **Resolver rules and private hosted zones** – For each DNS query, VPC Resolver uses the first Profile, in priority order, that has a Resolver rule or a private hosted zone that matches the domain name in the query. VPC Resolver doesn't evaluate the remaining Profiles for that query, even if one of them has a more specific match. VPC Resolver then compares the settings in that Profile with the local VPC settings: the most specific domain name wins, and the local VPC settings take precedence when both are equally specific.
+
+  * **Resolver DNS Firewall rule groups** – DNS Firewall evaluates the rule groups that are associated directly to the VPC together with the rule groups in the highest priority Profile association that has a rule that matches the query. The rule group priority determines the evaluation order, and a rule group that is associated directly to the VPC takes precedence over a Profile rule group that has the same rule group priority. DNS Firewall doesn't evaluate rule groups in the remaining Profiles for that query.
+
+  * **VPC Resolver query logging configurations** – VPC Resolver logs queries to the query logging configurations in every Profile that is associated to the VPC, regardless of priority.
+
+  * **Profile configurations** – For reverse DNS lookup configuration for Resolver rules, DNS Firewall failure mode configuration, and DNSSEC validation configuration, the setting in the highest priority Profile that sets the configuration applies. VPC Resolver skips Profiles that use the VPC's own setting. If no associated Profile sets the configuration, the VPC's own setting applies.
+
+
+
+
+For example, Profile A is associated to a VPC with priority 100, Profile B is associated to the same VPC with priority 200, and the VPC has a local Resolver rule for `corp.example.com`. The following table shows which rule VPC Resolver uses for queries from this VPC.
+
+DNS query | Profile A rule (priority 100) | Profile B rule (priority 200) | VPC rule | Evaluated rule  
+---|---|---|---|---  
+test.example.com |  example.com |  test.example.com |  None |  Profile A (example.com)  
+app.example.net |  None |  example.net |  None |  Profile B (example.net)  
+hr.corp.example.com |  example.com |  hr.corp.example.com |  corp.example.com |  Local VPC (corp.example.com)  
+  
+If a VPC has no other Profile associations, you can omit the priority when you associate a Profile, and the association gets priority 100. When the VPC already has a Profile association, you must specify a priority, and each Profile association for the VPC must have a unique priority. Associations that were created before you could associate multiple Profiles to a VPC have priority 100. You can change the priority later. For more information, see [Updating the priority of a Route 53 Profile association with a VPC](./profiles-vpc-update-priority.html).
+
+Every Profile association for a VPC that isn't deleted keeps its priority and counts toward the quota for Profiles per VPC. This includes associations whose status is `FAILED` or `DELETING`. When you disassociate a Profile from a VPC, the other Profile associations for the VPC keep their priorities, and VPC Resolver evaluates the remaining Profiles in priority order.
+