AWS Route53 documentation change
Summary
Consolidated multiple documentation sections into a single file, adding detailed procedures for managing Route53 Resolver rules including creation, reverse lookup configuration, VPC associations, cross-account sharing, and deletion.
Security assessment
The changes add documentation about security-related features including cross-account rule sharing permissions (PutResolverRulePolicy requirement), restrictions on modifying shared rules, and access control considerations. However, there is no evidence of addressing a specific security vulnerability or incident.
Diff
diff --git a/Route53/latest/DeveloperGuide/resolver-rules-managing.md b/Route53/latest/DeveloperGuide/resolver-rules-managing.md index 7ad65d838..0a5152b98 100644 --- a//Route53/latest/DeveloperGuide/resolver-rules-managing.md +++ b//Route53/latest/DeveloperGuide/resolver-rules-managing.md @@ -4,0 +5,2 @@ +Viewing and editing forwarding rulesCreating forwarding rulesAdding rules for reverse lookupAssociating forwarding rules with a VPCDisassociating forwarding rules from a VPCSharing Resolver rules with other AWS accounts and using shared rulesDeleting forwarding rulesForwarding rules for reverse DNS queries in Resolver + @@ -11 +13,287 @@ If you want Resolver to forward queries for specified domain names to your netwo - * [Viewing and editing forwarding rules](./resolver-rules-managing-viewing.html) + * Viewing and editing forwarding rules + + * Creating forwarding rules + + * Adding rules for reverse lookup + + * Associating forwarding rules with a VPC + + * Disassociating forwarding rules from a VPC + + * Sharing Resolver rules with other AWS accounts and using shared rules + + * Deleting forwarding rules + + * Forwarding rules for reverse DNS queries in Resolver + + + + +## Viewing and editing forwarding rules + +To view and edit settings for a forwarding rule, perform the following procedure. + +###### To view and edit settings for a forwarding rule + + 1. Sign in to the AWS Management Console and open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/). + + 2. In the navigation pane, choose **Rules**. + + 3. On the navigation bar, choose the Region where you created the rule. + + 4. Choose the option for the rule that you want to view settings for or want to edit. + + 5. Choose **View details** or **Edit**. + +For information about the values for forwarding rules, see [Values that you specify when you create or edit rules](./resolver-forwarding-outbound-queries-rule-values.html). + + 6. If you chose **Edit** , enter the applicable values, and then choose **Save**. + + + + +## Creating forwarding rules + +To create one or more forwarding rules, perform the following procedure. + +###### To create forwarding rules and associate the rules with one or more VPCs + + 1. Sign in to the AWS Management Console and open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/). + + 2. In the navigation pane, choose **Rules**. + + 3. On the navigation bar, choose the Region where you want to create the rule. + + 4. Choose **Create rule**. + + 5. Enter the applicable values. For more information, see [Values that you specify when you create or edit rules](./resolver-forwarding-outbound-queries-rule-values.html). + + 6. Choose **Save**. + + 7. To add another rule, repeat steps 4 through 6. + + + + +## Adding rules for reverse lookup + +If you need to control reverse lookups in your VPC, you can add rules to your outbound resolver endpoint. + +###### To create the reverse lookup rule + + 1. Follow the steps in the previous procedure, up to step 5. + + 2. When you specify your rule, enter the PTR record for the IP address or addresses that you want a reverse lookup forwarding rule for. + +For example, if you need to forward lookups for addresses in the 10.0.0.0/23 range, enter two rules: + + * 0.0.10.in-addr.arpa + + * 1.0.10.in-addr.arpa + +Any IP address in those subnets will be referenced as a subdomain of those PTR records—for example, 10.0.1.161 will have a reverse lookup address of 161.1.0.10.in-addr.arpa, which is a subdomain of 1.0.10.in-addra.arpa. + + 3. Specify the server to forward these lookups to. + + 4. Add these rules to your outbound resolver endpoint. + + + + +Note that turning on `enableDNSHostNames` for your VPC automatically adds PTR records. See [What is Amazon Route 53 Resolver?](./resolver.html). The previous procedure is required only if you want to explicitly specify a resolver for given IP ranges—for example, when forwarding queries to an Active Directory server. + +## Associating forwarding rules with a VPC + +After you create a forwarding rule, you must associate the rule with one or more VPCs. The rules will only work after they are associated with a VPC. When you associate a rule with a VPC, Resolver starts to forward DNS queries for the domain name that's specified in the rule to the DNS resolvers that you specified in the rule. The queries pass through the outbound endpoint that you specified when you created the rule. + +###### To associate a forwarding rule with one or more VPCs + + 1. Sign in to the AWS Management Console and open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/). + + 2. In the navigation pane, choose **Rules**. + + 3. On the navigation bar, choose the Region where you created the rule. + + 4. Choose the name of the rule that you want to associate with one or more VPCs. + + 5. Choose **Associate VPC**. + + 6. Under **VPCs that use this rule** , choose the VPCs that you want to associate the rule with. + + 7. Choose **Add**. + + + + +## Disassociating forwarding rules from a VPC + +You disassociate a forwarding rule from a VPC in the following circumstances: + + * For DNS queries that originate in this VPC, you want Resolver to stop forwarding queries for the domain name specified in the rule to your network. + + * You want to delete the forwarding rule. If a rule is currently associated with one or more VPCs, you must disassociate the rule from all VPCs before you can delete it. + + + + +If you want to disassociate a forwarding rule from one or more VPCs, perform the following procedure. + +###### To disassociate a forwarding rule from a VPC + + 1. Sign in to the AWS Management Console and open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/). + + 2. In the navigation pane, choose **Rules**. + + 3. On the navigation bar, choose the Region where you created the rule. + + 4. Choose the name of the rule that you want to disassociate from one or more VPCs. + + 5. Choose the option for the VPC that you want to disassociate the rule from. + + 6. Choose **Disassociate**. + + 7. Type **disassociate** to confirm. + + 8. Choose **Submit**. + + + + +## Sharing Resolver rules with other AWS accounts and using shared rules + +You can share the Resolver rules that you created using one AWS account with other AWS accounts. To share rules, the Route 53 Resolver console integrates with AWS Resource Access Manager. For more information about Resource Access Manager, see the [Resource Access Manager User Guide](https://docs.aws.amazon.com/ram/latest/userguide/what-is.html). + +Note the following: + +**Associating shared rules with VPCs** + + +If another AWS account has shared one or more rules with your account, you can associate the rules with your VPCs the same way that you associate rules that you created with your VPCs. For more information, see Associating forwarding rules with a VPC. + +**Deleting or unsharing a rule** + + +If you share a rule with other accounts and then either delete the rule or stop sharing it, and if the rule was associated with one or more VPCs, Route 53 Resolver starts to process DNS queries for those VPCs based on the remaining rules. The behavior is the same as if you disassociate the rule from the VPC. + +If a rule is shared to an Organizational Unit (OU) and an account in the OU is moved to a different OU, all associations with the shared rule to any VPC in the account will be deleted. However, if the Resolver rule was already shared with destination OU, then the VPC association will stay intact and will not be dissociated. + +**Maximum number of rules and associations** + + +When an account creates a rule and shares it with one or more other accounts, the maximum number of rules per AWS Region applies to the account that created the rule. + +When an account that a rule is shared with associates the rule with one or more VPCs, the maximum number of associations between rules and VPCs per Region applies to the account that the rule is shared with. + +For current Resolver quotas, see [Quotas on Route 53 Resolver](./DNSLimitations.html#limits-api-entities-resolver). + +**Permissions** + + +To share a rule with another AWS account, you must have permission to use the [PutResolverRulePolicy](https://docs.aws.amazon.com/Route53/latest/APIReference/API_route53resolver_PutResolverRulePolicy.html) action. + +**Restrictions on the AWS account that a rule is shared with** + + +The account that a rule is shared with can't change or delete the rule. + +**Tagging** + + +Only the account that created a rule can add, delete, or see tags on the rule. +