AWS AmazonRDS documentation change
Summary
Removed 'or an Aurora custom endpoint' from the restriction about what cannot be used to generate IAM authentication tokens, now only mentions custom Route 53 DNS records.
Security assessment
This change updates documentation about IAM database authentication restrictions. It clarifies that Aurora custom endpoints can now be used to generate authentication tokens, which is a feature update rather than a security fix. No evidence of a security vulnerability being addressed.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/UsingWithRDS.IAMDBAuth.Connecting.Python.md b/AmazonRDS/latest/AuroraUserGuide/UsingWithRDS.IAMDBAuth.Connecting.Python.md index 4efcdb016..4222a35cb 100644 --- a//AmazonRDS/latest/AuroraUserGuide/UsingWithRDS.IAMDBAuth.Connecting.Python.md +++ b//AmazonRDS/latest/AuroraUserGuide/UsingWithRDS.IAMDBAuth.Connecting.Python.md @@ -53 +53 @@ For `ssl_ca`, specify an SSL certificate. To download an SSL certificate, see [U -You cannot use a custom Route 53 DNS record or an Aurora custom endpoint instead of the DB cluster endpoint to generate the authentication token. +You cannot use a custom Route 53 DNS record instead of the DB cluster endpoint to generate the authentication token.