AWS documentdb documentation change
Summary
Added guidance about avoiding cluster state changes during shard scaling operations
Security assessment
The change focuses on operational reliability during scaling. No security implications are mentioned.
Diff
diff --git a/documentdb/latest/devguide/elastic-best-practices.md b/documentdb/latest/devguide/elastic-best-practices.md index 317605b2b..103ef2677 100644 --- a//documentdb/latest/devguide/elastic-best-practices.md +++ b//documentdb/latest/devguide/elastic-best-practices.md @@ -74,0 +75,2 @@ The following list describes guidelines for scaling your elastic clusters. + * Changing the number of shards can take time because data has to be safely moved from one shard to another. To minimize risk of errors, we recommend not stopping or making any other changes to the cluster state while the change is in progress. +