Choose the compute and memory capacity for a customer’s PD AWS DocumentDB cluster. The instance plan is separate from document storage, which grows automatically as data is added. Choosing a larger instance does not add standby instances or turn the offering into a multi-replica cluster.

Compare the offered plans

The module’s curated choices include Burstable Medium, Burstable Medium (Graviton), Memory Large, Memory Large (Graviton), Memory X-Large (Graviton) and Memory 2X-Large (Graviton). The burstable choices use T3 or T4g; the memory choices use R5 or R6g. Review the actual instance-class value with the label rather than judging capacity from a tier name alone.

AWS documents DocumentDB instance classes. Match compute and memory to the application’s working set, connections and sustained demand. This module’s curated catalogue is not a list of every class AWS offers.

Save a compatible selection

1. Open the package’s Module settings.
2. Review Plan, Region and DocumentDB version together.
3. Confirm the account’s available capacity and orderable combination.
4. Save, then check the actual customer selection before provisioning.

Live provider lookups can fall back to curated choices when unavailable. A displayed plan therefore does not prove AWS will accept that precise combination in the chosen region and account.

Separate defaults from changes

Editing a default is different from resizing an existing customer database. Review recovery needs, provider readiness and application interruption before a supported change. If creation refused a plan, preserve the original service and check its recorded result before trying again.

See the PD AWS DocumentDB Blesta guide for related tasks, or explore PD AWS DocumentDB.