AWS documentdb documentation change
Summary
Added warnings about burstable instances during upgrades and new pre-upgrade check failures for long collection names/index limits.
Security assessment
Changes focus on operational reliability during upgrades, not security vulnerabilities or features. No security terminology or context present.
Diff
diff --git a/documentdb/latest/devguide/docdb-mvu.md b/documentdb/latest/devguide/docdb-mvu.md index 3a271bd9b..254f87429 100644 --- a//documentdb/latest/devguide/docdb-mvu.md +++ b//documentdb/latest/devguide/docdb-mvu.md @@ -53,0 +54,2 @@ In-place MVU is not supported for global clusters or elastic clusters. To upgrad + * **Burstable instances** — If your cluster uses burstable instance types (for example, `db.t3.medium` or `db.t4g.medium`), we strongly recommend scaling up the primary instance to at least `db.r5.large` or `db.r6g.large` before initiating the upgrade. Burstable instances may not have sufficient CPU and memory to complete the upgrade process, which can result in upgrade failures and extended cluster unavailability. You can scale back down after the upgrade completes. + @@ -276,0 +279,6 @@ Replace each `placeholder` with your cluster's information. + * **Pre-upgrade check failure.** Before the upgrade begins, Amazon DocumentDB runs pre-upgrade validation checks. The following are common causes of pre-check failures: + + * **The upgrade could not proceed because collection(s) have names with 58 or more characters** — Rename the affected collections to shorter names before retrying the upgrade. + + * **The upgrade could not proceed because the index count exceeds the limit for the instance type** — Upgrade to a larger instance type before retrying the upgrade. For index limits by instance type, see Prerequisites. +