AWS aurora-dsql documentation change
Summary
Increased default connection limits and rate thresholds
Security assessment
Adjusts resource quotas without evidence of addressing a security vulnerability or enhancing security features.
Diff
diff --git a/aurora-dsql/latest/userguide/working-with-connections.md b/aurora-dsql/latest/userguide/working-with-connections.md index aecb031f2..9d5c30897 100644 --- a//aurora-dsql/latest/userguide/working-with-connections.md +++ b//aurora-dsql/latest/userguide/working-with-connections.md @@ -17 +17 @@ To make sure that a user with revoked Postgres credentials can't connect to a cl -By default, you can create up to [ 1000 connections per cluster ](https://docs.aws.amazon.com/aurora-dsql/latest/userguide/CHAP_quotas.html#SECTION_cluster-quotas)at 10 connections per second with a burst of 100. For example, if one connection is one token in a token bucket, you begin with 100 available tokens in the bucket. If you create 100 tokens, you have zero remaining tokens and have to wait for a second before you can create more connections. The refill rate is 10 tokens per second. To increase these limits, contact AWS support. +By default, you can create up to [ 10000 connections per cluster ](https://docs.aws.amazon.com/aurora-dsql/latest/userguide/CHAP_quotas.html#SECTION_cluster-quotas)at 100 connections per second with a burst of 1000. For example, if one connection is one token in a token bucket, you begin with 1000 available tokens in the bucket. If you create 1000 tokens, you have zero remaining tokens and have to wait for a second before you can create more connections. The refill rate is 100 tokens per second. To increase these limits, contact AWS support.