AWS vpc documentation change
Summary
Modified private DNS enablement criteria to specify ARN-type resource configurations for Amazon RDS databases
Security assessment
Change clarifies configuration requirements but doesn't address security vulnerabilities or introduce new security features. It's a documentation refinement rather than security-related.
Diff
diff --git a/vpc/latest/privatelink/privatelink-access-service-networks.md index baf757753..9cf65c0a3 100644 --- a/vpc/latest/privatelink/privatelink-access-service-networks.md +++ b/vpc/latest/privatelink/privatelink-access-service-networks.md @@ -68 +68 @@ If you're using the AWS Management Console, you can find the DNS name under the -When your service network has resource configurations that use ARNs, you can enable [private DNS](./privatelink-access-aws-services.html#interface-endpoint-private-dns). With private DNS, you can continue to make requests to the resource using the DNS name provisioned for the resource by the AWS service, while leveraging private connectivity through the service-network VPC endpoint. For more information, see [DNS resolution](./privatelink-access-resources.html#resource-endpoint-dns-resolution). +You can only enable [private DNS](./privatelink-access-aws-services.html#interface-endpoint-private-dns) when your service network has an ARN-type resource configuration to an Amazon RDS database service. With private DNS, you can continue to make requests to the resource using the DNS name provisioned for the resource by the AWS service, while leveraging private connectivity through the service-network VPC endpoint. For more information, see [DNS resolution](./privatelink-access-resources.html#resource-endpoint-dns-resolution).