Docs Menu

Export Cloud Backup Snapshot

On this page

  • How Atlas Exports Snapshots
  • Exported Data Format
  • Limitations
  • Pre-requisites
  • Export Management
Feature unavailable in Free and Shared-Tier Clusters

This feature is not available for M0 free clusters, M2, and 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. Atlas automatically exports any snapshot that matches this frequency.

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.

After Atlas finishes exporting, Atlas uploads a metadata file named .complete and a metadata file named metadata.json for each collection.

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 .json.gz 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 0.

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:

  1. M10 or higher Atlas cluster with Cloud Backup enabled.
  2. AWS IAM role with STS:AssumeRole that grants Atlas access to your AWS resources. To learn more about configuring AWS access for Atlas, see Set Up Unified AWS Access.
  3. AWS IAM role policy that grants Atlas write access or the S3:PutObject and S3:GetBucketLocation permissions 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:

Give Feedback
MongoDB logo
© 2021 MongoDB, Inc.


  • Careers
  • Legal Notices
  • Privacy Notices
  • Security Information
  • Trust Center
© 2021 MongoDB, Inc.