AWS AmazonRDS documentation change
Summary
Updated RDS Proxy endpoint limitations and added details about automatic VPC endpoint creation and AWS PrivateLink usage
Security assessment
Added documentation about automatic VPC endpoint creation for secure communication and AWS PrivateLink usage. While this clarifies security features, there's no evidence of addressing a specific vulnerability.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/rds-proxy-endpoints.md b/AmazonRDS/latest/AuroraUserGuide/rds-proxy-endpoints.md index 6baa5773b..10665553f 100644 --- a//AmazonRDS/latest/AuroraUserGuide/rds-proxy-endpoints.md +++ b//AmazonRDS/latest/AuroraUserGuide/rds-proxy-endpoints.md @@ -69 +69 @@ RDS Proxy endpoints have the following limitations: - * Each proxy has a default endpoint that you can modify but not create or delete. + * The RDS proxy default endpoint cannot be modified. @@ -77,0 +78,4 @@ RDS Proxy endpoints have the following limitations: +When you create a proxy, RDS automatically creates a VPC endpoint for secure communication between applications and the database. The VPC endpoint is visible and can be accessed from the Amazon VPC Console. + +Adding a new proxy endpoint provisions an AWS PrivateLink interface endpoint. If you add one or more endpoints to your proxy, you incure additional charges. For more information, see [RDS Proxy Pricing](https://aws.amazon.com/rds/proxy/pricing/). +