As the hosting operator, plan recovery for your customer’s documents before a PD AWS DocumentDB service needs it. The administrator needs a usable cluster recovery point, a working destination and a deliberate application cutover. The customer Snapshots page does not provide an in-place Restore control.

Establish the recovery point

Identify the original service, AWS region and cluster. Record the required point in time and ask the administrator to verify that a usable manual snapshot or automated recovery point exists. Normal module provisioning requests seven-day backup retention; confirm the actual retained backups before relying on that window for an existing service.

A missing customer-list item is not proof that no backup exists. Preserve the source cluster and the recovery points the application needs while the administrator checks the provider state. Read the manual-snapshot guide only as preparation for supported customer actions, not as a replacement for a tested recovery procedure.

Restore and prepare compute

AWS snapshot restoration creates a new DocumentDB cluster, rather than overwriting the existing one. An API restoration restores the cluster volume; compute instances must be added once the restored cluster is available. The administrator must verify both storage and compute readiness before testing an application connection.

The module’s customer controls do not expose Restore, point-in-time recovery or native snapshot export to S3. Keep the recovery point independently of any separate application-data export, and use the administrator’s appropriate AWS recovery workflow.

Coordinate tracking and cutover

A separately restored AWS cluster is not automatically attached to the original billing service. Record the original and destination clusters separately and establish how the recovered cluster will be managed before changing module settings or retiring the source. Another Create request is not a way to attach a separately restored cluster. Privately verify the destination’s network access, TLS, credentials and recovered documents. Then plan the application endpoint change and check the application’s result. Keep the original service and recovery-point references alongside the observed recovery result.

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