AWS Route53: Route53 traffic policy docs: editorial rewording of health-check guidance
Summary
Wording-only edits across the traffic policy page: 'Evaluate target health is checked by default and it will evaluate...' reworded to 'Evaluate target health is checked by default. It evaluates...', removal of 'if you want to' in the health check sentence, and a rephrased geoproximity/weighted-routing recommendation. No technical or security guidance changed.
Security assessment
The single changed sentence retains identical meaning to the original (health evaluation still described, users still directed to create a health check), only grammar/clarity differs. The geoproximity paragraph change is likewise a stylistic rewrite of 50/50 weighted routing advice. No new capability, permission, or vulnerability mitigation is documented, so there is no security impact.
Evidence
+Evaluate target health is checked by default. It evaluates the health of the target endpoint to which traffic is routed through an alias record. If your endpoint doesn't receive DNS traffic through an alias record, clear this option and create a health check to monitor the endpoint health. For more information, see [Creating and updating health checks](./health-checks-creating.html).
Diff
diff --git a/Route53/latest/DeveloperGuide/traffic-policies.md b/Route53/latest/DeveloperGuide/traffic-policies.md index 79bf50922..203d84aaa 100644 --- a//Route53/latest/DeveloperGuide/traffic-policies.md +++ b//Route53/latest/DeveloperGuide/traffic-policies.md @@ -214 +214 @@ For more information, see [Active-passive failover](./dns-failover-types.html#dn -Evaluate target health is checked by default and it will evaluate the health of the target endpoint to which traffic is routed through an alias record. If your endpoint doesn't receive DNS traffic through an alias record, clear this option 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). +Evaluate target health is checked by default. It evaluates the health of the target endpoint to which traffic is routed through an alias record. If your endpoint doesn't receive DNS traffic through an alias record, clear this option and create a health check to monitor the endpoint health. For more information, see [Creating and updating health checks](./health-checks-creating.html). @@ -227 +227 @@ When you choose **Geolocation rule** , you also choose the country or the state -Evaluate target health is checked by default and it will evaluate the health of the target endpoint to which traffic is routed through an alias record. If your endpoint doesn't receive DNS traffic through an alias record, clear this option 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). +Evaluate target health is checked by default. It evaluates the health of the target endpoint to which traffic is routed through an alias record. If your endpoint doesn't receive DNS traffic through an alias record, clear this option and create a health check to monitor the endpoint health. For more information, see [Creating and updating health checks](./health-checks-creating.html). @@ -240 +240 @@ For more information, see [Latency-based routing](./routing-policy-latency.html) -Evaluate target health is checked by default and it will evaluate the health of the target endpoint to which traffic is routed through an alias record. If your endpoint doesn't receive DNS traffic through an alias record, clear this option 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). +Evaluate target health is checked by default. It evaluates the health of the target endpoint to which traffic is routed through an alias record. If your endpoint doesn't receive DNS traffic through an alias record, clear this option and create a health check to monitor the endpoint health. For more information, see [Creating and updating health checks](./health-checks-creating.html). @@ -273 +273 @@ A single geoproximity routing policy cannot contain two or more locations that a -Additionally, some AWS Regions and Local Zones, such as US West (Oregon) and Portland, US, are situated too close to one another to be used within the same geoproximity routing policy. If you require traffic routing to more than one location within the same metropolitan area, instead define a geoproximity routing policy that results in a 50/50 weighted routing rule (WRR) for two different endpoints in the area, thereby distributing traffic evenly between those endpoints. +Additionally, some AWS Regions and Local Zones, such as US West (Oregon) and Portland, US, are situated too close to one another to be used within the same geoproximity routing policy. If you need to route traffic to more than one location within the same metropolitan area, define a geoproximity routing policy that creates a 50/50 weighted routing rule (WRR) for two endpoints in the area. This distributes traffic evenly between those endpoints. @@ -313 +313 @@ For more information, see [Geoproximity routing](./routing-policy-geoproximity.h -Evaluate target health is checked by default and it will evaluate the health of the target endpoint to which traffic is routed through an alias record. If your endpoint doesn't receive DNS traffic through an alias record, clear this option 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). +Evaluate target health is checked by default. It evaluates the health of the target endpoint to which traffic is routed through an alias record. If your endpoint doesn't receive DNS traffic through an alias record, clear this option and create a health check to monitor the endpoint health. For more information, see [Creating and updating health checks](./health-checks-creating.html). @@ -324 +324 @@ For more information, see [Multivalue answer routing](./routing-policy-multivalu -Evaluate target health is checked by default and it will evaluate the health of the target endpoint to which traffic is routed through an alias record. If your endpoint doesn't receive DNS traffic through an alias record, clear this option 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). +Evaluate target health is checked by default. It evaluates the health of the target endpoint to which traffic is routed through an alias record. If your endpoint doesn't receive DNS traffic through an alias record, clear this option and create a health check to monitor the endpoint health. For more information, see [Creating and updating health checks](./health-checks-creating.html). @@ -337 +337 @@ For more information, see [Weighted routing](./routing-policy-weighted.html). -Evaluate target health is checked by default and it will evaluate the health of the target endpoint to which traffic is routed through an alias record. If your endpoint doesn't receive DNS traffic through an alias record, clear this option 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). +Evaluate target health is checked by default. It evaluates the health of the target endpoint to which traffic is routed through an alias record. If your endpoint doesn't receive DNS traffic through an alias record, clear this option and create a health check to monitor the endpoint health. For more information, see [Creating and updating health checks](./health-checks-creating.html).