AWS secretsmanager documentation change
Summary
Minor wording change: replaced 'on the client side' with 'unexpected issues' in API failure explanation.
Security assessment
Cosmetic language adjustment without security implications. No references to vulnerabilities or security features.
Diff
diff --git a/secretsmanager/latest/userguide/reference_limits.md b/secretsmanager/latest/userguide/reference_limits.md index 325b0c7aa..5063a7e2e 100644 --- a//secretsmanager/latest/userguide/reference_limits.md +++ b//secretsmanager/latest/userguide/reference_limits.md @@ -42 +42 @@ Versions per secret | Each supported Region: 100 | No | The maximum number of ve -Your AWS client might see calls to Secrets Manager fail due to unexpected issues on the client side. Or calls might fail due to rate limiting from Secrets Manager. When you exceed an API request quota, Secrets Manager throttles the request. It rejects an otherwise valid request and returns a throttling error. For both kinds of failures, we recommend you retry the call after a brief waiting period. This is called a [backoff and retry strategy](https://docs.aws.amazon.com/general/latest/gr/api-retries.html). +Your AWS client might see calls to Secrets Manager fail due to unexpected issues. Or calls might fail due to rate limiting from Secrets Manager. When you exceed an API request quota, Secrets Manager throttles the request. It rejects an otherwise valid request and returns a throttling error. For both kinds of failures, we recommend you retry the call after a brief waiting period. This is called a [backoff and retry strategy](https://docs.aws.amazon.com/general/latest/gr/api-retries.html).