AWS Security ChangesHomeSearch

AWS Route53: Document priority setting when associating a Profile to a VPC

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

File: Route53/latest/DeveloperGuide/profile-associate-vpcs.md

Summary

Adds an optional priority step in the console workflow, updates the CLI associate-profile instructions and example output, and explains the --priority parameter (100-9900, lower is higher, must be unique per VPC).

Security assessment

The change documents evaluation-order priority for Route 53 Profile associations and corrects CLI examples; it is functional configuration guidance with no authentication, encryption, or exposure implications.

Evidence

+To set the order in which VPC Resolver evaluates the Profiles associated to the VPC, add the `--priority` parameter with a value from 100 to 9900. A lower value means a higher priority. If the VPC has no other Profile associations, you can omit `--priority`, and the association gets priority 100. If the VPC already has a Profile association, `--priority` is required and must be different from the priority of every other Profile association for the VPC.

Diff

diff --git a/Route53/latest/DeveloperGuide/profile-associate-vpcs.md b/Route53/latest/DeveloperGuide/profile-associate-vpcs.md
index 6096fa1..6d4e694 100644
--- a//Route53/latest/DeveloperGuide/profile-associate-vpcs.md
+++ b//Route53/latest/DeveloperGuide/profile-associate-vpcs.md
@@ -31 +31 @@ Console
-  5. Choose **Associate**
+  5. (Optional) In the **Review profile prioritization** table, set the **Priority** for the new association, and change the priority of the Profiles that are already associated to the VPC if needed. To change a priority, choose the **Edit priority** (pencil) icon in the **Priority** column, enter a value from 100 to 9900, and then choose **Submit edit**. A lower value means a higher priority, and each Profile associated to a VPC must have a unique priority. For more information, see [How Route 53 Profile settings are prioritized](./profiles.html#profiles-priority).
@@ -33 +33,3 @@ Console
-  6. The association progress is displayed in the **Status** column on the **VPCs** page.
+  6. Choose **Associate**
+
+  7. The association progress is displayed in the **Status** column on the **VPCs** page.
@@ -41 +43 @@ CLI
-You can list the Profiles by running a AWS CLI command like the following and using your own values for `name`, `profile-id`, and `resource-id`:
+To associate a Profile to a VPC, use the [associate-profile](https://docs.aws.amazon.com/cli/latest/reference/route53profiles/associate-profile.html) AWS CLI command. For example, the following command associates Profile `rp-4987774726example` to VPC `vpc-0af3b96b3example`. Use your own values for `name`, `profile-id`, and `resource-id`.
@@ -49,5 +51,5 @@ The following is an example output after you run the command:
-        "ProfileResourceAssociation": {
-            "CreationTime": 1710851216.613,
-            "Id": "rpr-001913120a7example",
-            "ModificationTime": 1710851216.613,
-            "Name": "test-resource-association",
+        "ProfileAssociation": {
+            "CreationTime": 1709338817.148,
+            "Id": "rpassoc-489ce212fexample",
+            "ModificationTime": 1709338817.148,
+            "Name": "test-association",
@@ -56,5 +58,4 @@ The following is an example output after you run the command:
-            "ResourceArn": "arn:aws:route53resolver:us-east-1:123456789012:firewall-rule-group/rslvr-frg-cfe7f72example",
-            "ResourceProperties": "{\"priority\":102}",
-            "ResourceType": "FIREWALL_RULE_GROUP",
-            "Status": "UPDATING",
-            "StatusMessage": "Updating the Profile to DNS Firewall rule group association"
+            "ResourceId": "vpc-0af3b96b3example",
+            "Priority": 100,
+            "Status": "CREATING",
+            "StatusMessage": "Creating Profile Association"
@@ -63,0 +65,2 @@ The following is an example output after you run the command:
+To set the order in which VPC Resolver evaluates the Profiles associated to the VPC, add the `--priority` parameter with a value from 100 to 9900. A lower value means a higher priority. If the VPC has no other Profile associations, you can omit `--priority`, and the association gets priority 100. If the VPC already has a Profile association, `--priority` is required and must be different from the priority of every other Profile association for the VPC.
+