AWS AmazonRDS documentation change
Summary
Removed explicit throttling limit (200 connections/second) from IAM DB authentication error explanation.
Security assessment
The change removes a specific rate limit number but retains the throttling error behavior and mitigation advice. No security vulnerability is indicated; this appears to be a documentation refinement.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/UsingWithRDS.IAMDBAuth.Troubleshooting.md b/AmazonRDS/latest/AuroraUserGuide/UsingWithRDS.IAMDBAuth.Troubleshooting.md index 123430dad..faa4eb23b 100644 --- a//AmazonRDS/latest/AuroraUserGuide/UsingWithRDS.IAMDBAuth.Troubleshooting.md +++ b//AmazonRDS/latest/AuroraUserGuide/UsingWithRDS.IAMDBAuth.Troubleshooting.md @@ -80 +80 @@ Error | Metric(s) | Cause | Solution -`[ERROR] Failed to authorize the connection request for user `db_user` due to IAM DB authentication throttling. (Status Code: 429, Error Code: ThrottlingException)` | `IamDbAuthConnectionFailure` `IamDbAuthConnectionFailureThrottling` | You are making too many connection requests to your DB in a short amount of time. IAM DB authentication throttling limit is 200 connections per second. | Reduce the rate of establishing new connections with IAM authentication. Consider implementing connection pooling using RDS Proxy in order to reuse established connections in your application. +`[ERROR] Failed to authorize the connection request for user `db_user` due to IAM DB authentication throttling. (Status Code: 429, Error Code: ThrottlingException)` | `IamDbAuthConnectionFailure` `IamDbAuthConnectionFailureThrottling` | You are making too many connection requests to your DB in a short amount of time. | Reduce the rate of establishing new connections with IAM authentication. Consider implementing connection pooling using RDS Proxy in order to reuse established connections in your application.