Cluster Snapshot Considerations - Amazon DocumentDB

Cluster Snapshot Considerations

Amazon DocumentDB creates daily automatic snapshots of your cluster during your cluster's backup window. Amazon DocumentDB saves the automatic snapshots of your cluster according to the backup retention period that you specify. If necessary, you can recover your cluster to any point in time during the backup retention period. Automatic snapshots don't occur while a copy operation is executing in the same Region for the same cluster.

In addition to automatic cluster snapshots, you can also manually create a cluster snapshot. You can copy both automatic and manual snapshots. For more information, see Creating a Manual Cluster Snapshot and Copying Amazon DocumentDB Cluster Snapshots.


Your cluster must be in the available state for an automatic snapshot to be taken.

You can't share an Amazon DocumentDB automated cluster snapshot. As a workaround, you can create a manual snapshot by copying the automated snapshot, and then share that copy. For more information about copying a snapshot, see Copying Amazon DocumentDB Cluster Snapshots. For more information about restoring a cluster from a snapshot, see Restoring from a Cluster Snapshot.

Backup Storage

Your Amazon DocumentDB backup storage for each AWS Region is composed of the backup storage needed for your backup retention period, which includes automatic and manual cluster snapshots in that Region. The default backup retention period is 1 day. For more information about backup storage pricing, see Amazon DocumentDB Pricing.

When you delete a cluster, all of its automatic snapshots are deleted and cannot be recovered. However, manual snapshots are not deleted when you delete a cluster. if you choose to have Amazon DocumentDB create a final snapshot (manual snapshot) before your cluster is deleted, you can use the final snapshot to recover your cluster.

For more information on snapshots and storage, see Understanding Backup Storage Usage.

Backup Window

Automatic snapshots occur daily during the preferred backup window. If the snapshot requires more time than allotted to the backup window, the backup process continues until it finishes, even though the backup window has ended. The backup window can't overlap with the weekly maintenance window for the cluster.

If you don't specify a preferred backup window when you create the cluster, Amazon DocumentDB assigns a default 30-minute backup window. This window is chosen at random from an 8-hour block of time associated with your cluster's Region. You can change your preferred backup window by modifying the cluster. For more information, see Modifying an Amazon DocumentDB cluster.

Region UTC Time Block
US East (Ohio) 03:00-11:00
US East (N. Virginia) 03:00-11:00
US West (Oregon) 06:00-14:00
South America (São Paulo) 04:00-12:00
Asia Pacific (Hong Kong) 14:00-22:00
Asia Pacific (Hyderabad) 06:30–14:30
Asia Pacific (Mumbai) 17:30-01:30
Asia Pacific (Seoul) 13:00-21:00
Asia Pacific (Singapore) 14:00-22:00
Asia Pacific (Sydney) 12:00-20:00
Asia Pacific (Tokyo) 13:00-21:00
Canada (Central) 03:00-11:00
Europe (Frankfurt) 23:00-07:00
Europe (Ireland) 22:00-06:00
Europe (London) 22:00-06:00
Europe (Milan) 23:00-07:00
Europe (Paris) 22:00-06:00
China (Beijing) 14:00-22:00
China (Ningxia) 14:00-22:00
AWS GovCloud (US-West) 06:00-14:00
AWS GovCloud (US-East) 17:00-01:00

Backup Retention Period

The backup retention period is the number of days an automatic backup is retained before being automatically deleted. Amazon DocumentDB supports a backup retention period of 1–35 days.

You can set the backup retention period when you create a cluster. If you don't explicitly set the backup retention period, the default backup retention period of 1 day is assigned to your cluster. After you create a cluster, you can modify the backup retention period by modifying the cluster using either the AWS Management Console or the AWS CLI. For more information, see Modifying an Amazon DocumentDB cluster.

Copy Cluster Snapshot Encryption

Cluster and snapshot encryption is based on a KMS encryption key. The KMS key ID is the Amazon Resource Name (ARN), KMS key identifier, or the KMS key alias for the KMS encryption key.

The following guidelines and limitations apply:

  • Encryption is inferred from the cluster when creating a snapshot. If the cluster is encrypted, the snapshot of that cluster is encrypted with the same KMS key. If the cluster is not encrypted, the snapshot is not encrypted.

  • If you copy an encrypted cluster snapshot from your Amazon Web Services account, you can specify a value for KmsKeyId to encrypt the copy with a new KMS encryption key. If you don't specify a value for KmsKeyId , then the copy of the cluster snapshot is encrypted with the same KMS key as the source cluster snapshot.

  • If you copy an encrypted cluster snapshot that is shared from another Amazon Web Services account, then you must specify a value for KmsKeyId.

  • To copy an encrypted cluster snapshot to another Amazon Web Services Region, set KmsKeyId to the KMS key ID that you want to use to encrypt the copy of the cluster snapshot in the destination Region. KMS encryption keys are specific to the Amazon Web Services Region that they are created in, and you can't use encryption keys from one Amazon Web Services Region in another Amazon Web Services Region.

  • If you copy an unencrypted cluster snapshot and specify a value for the KmsKeyId parameter, an error is returned.