AWS AWSCloudFormation: Route53 RecordSetGroup AliasTarget: clarify private hosted zone routing policies
Summary
Replaces the note that geolocation/latency alias records in a private hosted zone are 'allowed but not supported' with a pointer to the supported routing policies documentation.
Security assessment
Pure documentation clarification of supported routing policies for alias records; no security feature, fix, or vulnerability reference.
Evidence
+ * You can create alias records in a private hosted zone with any routing policy that private hosted zones support. For the list of supported routing policies, see [Supported routing policies for records in a private hosted zone](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zone-private-considerations.html#hosted-zone-private-considerations-routing-policies).
Diff
diff --git a/AWSCloudFormation/latest/TemplateReference/aws-properties-route53-recordsetgroup-aliastarget.md b/AWSCloudFormation/latest/TemplateReference/aws-properties-route53-recordsetgroup-aliastarget.md index 7eeed2c..6273ad4 100644 --- a//AWSCloudFormation/latest/TemplateReference/aws-properties-route53-recordsetgroup-aliastarget.md +++ b//AWSCloudFormation/latest/TemplateReference/aws-properties-route53-recordsetgroup-aliastarget.md @@ -15 +15 @@ When creating records for a private hosted zone, note the following: - * Creating geolocation alias and latency alias records in a private hosted zone is allowed but not supported. + * You can create alias records in a private hosted zone with any routing policy that private hosted zones support. For the list of supported routing policies, see [Supported routing policies for records in a private hosted zone](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zone-private-considerations.html#hosted-zone-private-considerations-routing-policies).