AWS Route53 documentation change
Summary
Updated documentation for Route 53 traffic policies, including changes to JSON document handling, console transition notes, and detailed procedures for creating, viewing, and deleting traffic policies
Security assessment
The changes primarily focus on updating documentation for traffic policy management, including console transition notes and JSON handling. There is no evidence of security vulnerability fixes or new security features being documented.
Diff
diff --git a/Route53/latest/DeveloperGuide/traffic-policies.md index 2f0c1578b..df9bd1edd 100644 --- a/Route53/latest/DeveloperGuide/traffic-policies.md +++ b/Route53/latest/DeveloperGuide/traffic-policies.md @@ -5 +5 @@ -Creating a traffic policyValues that you specify when you create a traffic policyViewing a map that shows the effect of geoproximity settingsCreating additional versions of a traffic policyCreating a traffic policy by importing a JSON documentViewing traffic policy versions and the associated policy recordsDeleting traffic policy versions and traffic policies +Creating a traffic policyValues that you specify when you create a traffic policyViewing a map that shows the effect of geoproximity settingsCreating additional versions of a traffic policyCreating a traffic policy by using a JSON documentViewing traffic policy versions and the associated policy recordsDeleting traffic policy versions and traffic policies @@ -19 +19 @@ Creating a traffic policyValues that you specify when you create a traffic polic - * Creating a traffic policy by importing a JSON document + * Creating a traffic policy by using a JSON document @@ -31,0 +32,60 @@ To create a traffic policy, perform the following procedure. +###### Note + +We're updating the Traffic Flow console for Route 53. During the transition period, you can continue to use the old console. + +Choose the tab for the console you are using. + + * New console + + * Old console + + + + +New console + + +###### To create a traffic policy + + 1. Design your configuration. For information about how complex DNS routing configurations work, see [Configuring DNS failover](./dns-failover-configuring.html) in [Creating Amazon Route 53 health checks ](./dns-failover.html). + + 2. Based on the design for your configuration, create the health checks that you want to use for your endpoints. + + 3. 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/). + + 4. In the navigation pane, choose **Traffic policies**. + + 5. Choose **Create traffic policy**. + + 6. Enter a name and an optional description, and then choose **Next**. + + 7. On the editor, choose the DNS resource record type in the **Properties** pane. This type will be assigned to all resource records that you create for this traffic policy. + +Choose **Confirm**. For more information, see Values that you specify when you create a traffic policy. + + 8. In the editor page, choose **Connect to** and then choose one of **New routing rule** , **New endpoint** , **Existing routing rule** , or **Existing endpoint**. If you selected a **New routing rule** , in the **Properties** pane select the routing rule and choose **Confirm**. Then, in the **Properties** pane, enter the appropriate values. Repeat this process until your policy is done. For more information about the values for each connection type, see Values that you specify when you create a traffic policy. + +You can delete rules, endpoints, and branches of a traffic policy in the following ways: + + * To delete a rule or an endpoint, select the rule or the endpoint in the editor, and then choose **Delete** in **Properties** pane. + +###### Important + +If you delete a rule that has child rules and endpoints, Amazon Route 53 also deletes all of the children. + + * If you connect two rules to the same child rule or endpoint and you want to delete one of the connections, select the connection that you want to delete, and chose the **Delete** in the **Properties** pane for that connection. + + 9. Choose **Create policy**. + + 10. On the **Create policy records** page, use the new traffic policy to create one or more policy records in one hosted zone. For more information, see [Values that you specify when you create or update a policy record](./traffic-policy-records.html#traffic-policy-records-creating-values). You can also create policy records later, either in the same hosted zone or in additional hosted zones. + +If you don't want to create policy records now, choose **Cancel** , and the console displays the list of traffic policies and policy records that you have created by using the current AWS account. + + 11. If you specified settings for policy records in the preceding step, choose **Create policy records**. + + + + +Old console + + @@ -72,0 +133,4 @@ If you don't want to create policy records now, choose **Skip this step** , and +###### Note + +We're updating the Traffic Flow console for Route 53. During the transition period, you can continue to use the old console. The following list applies for both console, except where noted. + @@ -88,0 +153,2 @@ When you create a traffic policy, you specify the following values. + * Key (new console only) + @@ -115,0 +182,4 @@ If you want to route traffic to the following AWS resources, choose the applicab +###### Note + +CloudFront alias endpoints don't support evaluate health check. You can however, create a health check to monitor CloudFront endpoints. For more information, see [Creating and updating health checks](./health-checks-creating.html). + @@ -139,0 +210,4 @@ For more information, see [Active-passive failover](./dns-failover-types.html#dn +###### Note + +Evaluate target health is checked by default and it will evaluate the health of the target endpoint to which traffic is routed via an alias record. If you endpoint doesn't receive DNS traffic via an alias record, uncheck this and create a health check if you want to monitor the endpoint health. For more information, see [Creating and updating health checks](./health-checks-creating.html). + @@ -148,0 +223,4 @@ When you choose **Geolocation rule** , you also choose the country or the state +###### Note + +Evaluate target health is checked by default and it will evaluate the health of the target endpoint to which traffic is routed via an alias record. If you endpoint doesn't receive DNS traffic via an alias record, uncheck this and create a health check if you want to monitor the endpoint health. For more information, see [Creating and updating health checks](./health-checks-creating.html). + @@ -157,0 +236,4 @@ For more information, see [Latency-based routing](./routing-policy-latency.html) +###### Note + +Evaluate target health is checked by default and it will evaluate the health of the target endpoint to which traffic is routed via an alias record. If you endpoint doesn't receive DNS traffic via an alias record, uncheck this and create a health check if you want to monitor the endpoint health. For more information, see [Creating and updating health checks](./health-checks-creating.html). + @@ -226,0 +309,4 @@ For more information, see [Geoproximity routing](./routing-policy-geoproximity.h +###### Note + +Evaluate target health is checked by default and it will evaluate the health of the target endpoint to which traffic is routed via an alias record. If you endpoint doesn't receive DNS traffic via an alias record, uncheck this and create a health check if you want to monitor the endpoint health. For more information, see [Creating and updating health checks](./health-checks-creating.html). + @@ -233,0 +320,4 @@ For more information, see [Multivalue answer routing](./routing-policy-multivalu +###### Note + +Evaluate target health is checked by default and it will evaluate the health of the target endpoint to which traffic is routed via an alias record. If you endpoint doesn't receive DNS traffic via an alias record, uncheck this and create a health check if you want to monitor the endpoint health. For more information, see [Creating and updating health checks](./health-checks-creating.html). + @@ -242,0 +333,4 @@ For more information, see [Weighted routing](./routing-policy-weighted.html). +###### Note + +Evaluate target health is checked by default and it will evaluate the health of the target endpoint to which traffic is routed via an alias record. If you endpoint doesn't receive DNS traffic via an alias record, uncheck this and create a health check if you want to monitor the endpoint health. For more information, see [Creating and updating health checks](./health-checks-creating.html). + @@ -270,0 +365,4 @@ Choose this option if you want to route traffic to a CloudFront distribution. Th +###### Note + +CloudFront alias endpoints don't support evaluate health check. You can however, create a health check to monitor CloudFront endpoints. For more information, see [Creating and updating health checks](./health-checks-creating.html). + @@ -345,0 +444,4 @@ For more information about supported DNS types, see [Supported DNS record types] +### Key (new console only) + +Enter a friendly name for a routing rule or an endpoint for **Key**. This value displays as the name of a node in the editor. + @@ -349,0 +452,42 @@ A _geoproximity rule_ lets you specify the locations of your resources, both in +###### Note + +We're updating the Traffic Flow console for Route 53. During the transition period, you can continue to use the old console. + +Choose the tab for the console you are using. + + * New console + + * Old console + + + + +New console + + +You can display a map that shows the effect of your current geoproximity settings. For example, if you have resources in the US West (Oregon), Europe (Frankfurt), and Asia Pacific (Tokyo) Regions, and if you don't specify a bias, the map looks like this. + + + +The map for a geoproximity rule automatically displays in the **Properties** and updates as you add or delete regions. + +Note the following: + + * The map is accurate to within approximately 10 miles (16 kilometers). + + * The map automatically adjusts when you add, edit, or delete Regions, or when you change the bias setting for a Region. + + * The Region number and color in each rule definition correspond with numbers and colors on the map. + + * You can zoom in and zoom out to see more or less detail. Use the + and - buttons on the map, a touchpad, or the wheel on a mouse to change the zoom level. If you don't see the Region, or the Region number, you can enlarge the **Properties** pane and they will appear. + + * You can move the map around inside the map window to see specific areas. Use a touchpad, or click and drag the map with a mouse. You can also move the map window in a browser window. + + * If you have more than one geoproximity rule in a policy, you can view the map for only one rule at a time. + + + + +Old console + + @@ -380,0 +525,58 @@ To create a new traffic policy version, perform the following procedure. +###### Note + +We're updating the Traffic Flow console for Route 53. During the transition period, you can continue to use the old console. + +Choose the tab for the console you are using. + + * New console + + * Old console + + + + +New console + + +###### To create another version of a traffic policy + + 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 **Traffic policies**. + + 3. Choose the name of the traffic policy that you want to create a new version of. + + 4. In the **Traffic policy versions** table at the top of the page, select the check box for the traffic policy version that you want to use as a basis for the new traffic policy version. + + 5. Choose **Edit policy as new version**. + + 6. On the **Edit policy as a new version** dialog box, enter a description for the new traffic policy version. We recommend that you specify a description that distinguishes this version from other versions of the same traffic policy. When you create a new policy record, the value that you specify appears in the list of available versions for this traffic policy. + + 7. Choose **Next**. +