AWS Security ChangesHomeSearch

AWS AmazonRDS documentation change

Service: AmazonRDS · 2026-07-01 · Documentation low

File: AmazonRDS/latest/AuroraUserGuide/UsingWithRDS.IAMDBAuth.md

Summary

Removed connection rate limit recommendation (200 connections/second) and associated throttling explanation for IAM DB authentication.

Security assessment

Deletion of a specific connection rate limit suggests operational changes but lacks evidence of addressing a security flaw. Mitigation advice (connection pooling) remains unchanged.

Diff

diff --git a/AmazonRDS/latest/AuroraUserGuide/UsingWithRDS.IAMDBAuth.md b/AmazonRDS/latest/AuroraUserGuide/UsingWithRDS.IAMDBAuth.md
index 8d75ddd85..650c22665 100644
--- a//AmazonRDS/latest/AuroraUserGuide/UsingWithRDS.IAMDBAuth.md
+++ b//AmazonRDS/latest/AuroraUserGuide/UsingWithRDS.IAMDBAuth.md
@@ -26 +26 @@ IAM database authentication provides the following benefits:
-In general, consider using IAM database authentication when your applications create fewer than 200 connections per second, and you don't want to manage usernames and passwords directly in your application code.
+In general, consider using IAM database authentication when you don't want to manage usernames and passwords directly in your application code.
@@ -103,6 +102,0 @@ We recommend the following when using IAM database authentication:
-  * Use IAM database authentication when your application requires fewer than 200 new IAM database authentication connections per second.
-
-The database engines that work with Amazon Aurora don't impose any limits on authentication attempts per second. However, when you use IAM database authentication, your application must generate an authentication token. Your application then uses that token to connect to the DB cluster. If you exceed the limit of maximum new connections per second, then the extra overhead of IAM database authentication can cause connection throttling. 
-
-Consider using connection pooling in your applications to mitigate constant connection creation. This can reduce the overhead from IAM DB authentication and allow your applications to reuse existing connections. Alternatively, consider using RDS Proxy for these use cases. RDS Proxy has additional costs. See [RDS Proxy pricing](https://aws.amazon.com/rds/proxy/pricing/).
-