On this page
This feature is not available for
M0 free clusters,
M5 clusters. To learn more about which features are unavailable,
see Atlas M0 (Free Cluster), M2, and M5 Limitations.
Atlas lets you export your Cloud Backup snapshots to an AWS S3 bucket.
You can manually export individual snapshots or set up an export policy for automatic export of your snapshots. For automatic exports, you must specify a frequency in your export policy. The frequency can be monthly. To configure daily or weekly export frequency, submit a support request. Atlas automatically exports any backup snapshot with the frequency type that matches the export frequency. The exported result is a full backup of that snapshot.
Consider the following:
- A backup policy that sets a weekly and monthly snapshot schedule
- An export policy that sets a monthly export frequency
Suppose, at the end of the month, the weekly and monthly snapshots
happen on the same day. There would be
4 snapshots of which
3 would be weekly snapshots and the fourth snapshot, although
treated as a weekly snapshot by Atlas, would also be the monthly
snapshot because it happened on the same day. Atlas will export
the monthly snapshot only because the export frequency matches the
snapshot frequency for that snapshot. To export the weekly snapshots
as well, update the export policy to export weekly snapshots also.
If the export frequency is set to weekly, Atlas would export all
Atlas exports snapshots for collections one at a time. As the export progresses, you may see partial results in your S3 bucket. Atlas queues any new job if Atlas is currently exporting 5 or more replica sets. For sharded clusters, Atlas always exports the snapshots of all the shards simultaneously, regardless of the number of shards.
$.125 per GB of data exported to the AWS S3
bucket. Atlas compresses the data before exporting. To estimate the
amount of data being exported, add up the
of each database in your cluster. This total should correspond to the
uncompressed size of your export, which would be the maximum cost
Atlas uploads an empty file to
- Add a new AWS S3 export bucket
- Start an export
After Atlas finishes exporting, Atlas uploads a metadata file
.complete and a metadata file named
If an export job fails:
- Atlas doesn't automatically try to export again.
- Atlas doesn't remove any partial data in your S3 bucket.
Atlas uploads the contents of your database to S3 in
format with documents in extended JSON format within. The path
to the files on S3 is:
Name of your Atlas organization.
Name of your Atlas project.
Name of your Atlas cluster.
Date when snapshot was taken.
Timestamp when the export job was created.
Name of the database in the Atlas cluster.
Name of the Atlas collection.
Name of the replica set.
Count that is incremented as chunks are uploaded. Starts at
The following limitations apply:
- You can only export to AWS S3 buckets.
- You can't export fallback snapshots.
- You can have only one active export per snapshot.
To export your Cloud Backup snapshots to an AWS S3 bucket, you will need the following:
M10or higher Atlas cluster with Cloud Backup enabled.
- AWS IAM role
STS:AssumeRolethat grants Atlas access to your AWS resources. To learn more about configuring AWS access for Atlas, see Set Up Unified AWS Access.
- AWS IAM role policy
that grants Atlas write access or the
S3:GetBucketLocationpermissions to your AWS resources. To learn more about configuring write access to AWS resources, see Set Up Unified AWS Access.
Use the following APIs to: