Navigation
  • Billing >
  • Cluster Configuration Costs

Cluster Configuration Costs

Cloud Service Provider and Region

Atlas supports deploying clusters onto Amazon Web Services, the Google Cloud Platform, and Microsoft Azure. The choice of cloud service provider and region or regions for the Atlas project affects the cost of running a Atlas cluster.

Multi-region cluster costs depend on the number of and location of additional regions selected. When creating a cluster, Atlas displays the cluster tier cost based on only the Preferred Region of the cluster. You can see the total cost of running the cluster in the Cluster Overview.

For more information on configuring your cloud provider and region, see Cloud Providers and Regions.

Cluster Tier

Atlas provides different cluster tiers. Each cluster tier has a default RAM capacity, storage capacity, and maximum storage speed. The cluster’s per-hour charge includes these default values. Atlas uses the selected cluster when deploying all the data-bearing [1] servers in your cluster.

Depending on the choice of cloud service provider, Atlas provides customization options for cluster storage capacity and the speed of that storage. If you add capacity or speed, you incur additional costs on top of the base cost. For multi-region clusters, the per-cluster cost, including any selected customizations, is relative to the Preferred Region. The Cluster Overview box shows your overall charges.

Storage Capacity

Atlas charges for storage capacity differently depending on whether you use the cluster default or specify a custom storage capacity. If you use the default, storage is included in the cluster’s per-hour cost. If you customize, Atlas charges for the entire amount of storage, not the difference from the default size.

For example, if the cluster default is 80 GB and if you increase storage to 100 GB, the change in cost is the charge for 100 GB. If you then increase storage to 120 GB, the change in cost is the charge for 20 GB.

Note

Increasing storage capacity can change the max IOPS available with each Custom Storage Speed.

Custom Storage Speed

Atlas measures storage speed as maximum IOPS. Each Atlas cluster tier offers a default storage speed that is included in the cluster’s per-hour cost. The choice of cloud service provider and cluster affects the available storage speed customization options, as well as the cost of selecting a custom storage speed.

AWS
For most cluster types, you can increase storage speed from Standard to Fast or Fastest, which affects costs. Selecting a custom speed changes both IOPS and the type of storage used. The storage type changes from a general-purpose SSD to a provisioned-IOPS SSD. For more information on storage types, see Amazon EBS Volume Types.
GCP
All clusters use SSD persistent disks with fixed maximum IOPS based on the cluster storage capacity. The maximum IOPS increases as storage capacity increases. The cost of the increased maximum IOPS is included in the cost of the increased storage capacity. For more information on the GCP persistent disks, see Persistent Disks.
Azure
All clusters use premium SSD disks with fixed maximum IOPS based on the storage capacity. The maximum IOPS increases as storage capacity increases. The cost of the increased maximum IOPS is included in the cost of the increased storage capacity. For more information on the Azure Premium disks, see High-performance Premium Storage and managed disks for VMs.

Backup

The Atlas Backup supports Continuous Backups and Cloud Provider Snapshots. Each backup method has its own cost calculations and considerations.

Atlas charges for each replica set in a cluster. For a replica set deployment, the backup costs are the cost to backup data for the replica set. For a sharded cluster deployment, Atlas sums the cost to backup the data for each shard replica set and the config server replica set.

Atlas charges for the network transfer costs of restoring a snapshot. See Data Transfer Costs for more information on how Atlas charges for network data.

Continuous Backups

The backup cost for continuous backups is per GB per month (US$2.50 / GB / month) as specified on the Atlas pricing page. The monthly rate is annualized and then divided by 365 to arrive at a Daily Backup Rate per GB. The first 1 GB of backup data is free.

Monthly backup costs are primarily based on the size per-gigabyte of the data to back up. This size is roughly equivalent to the uncompressed size of all documents and all indexes for all the databases backed up.

To retrieve the size in gigabyte of the documents and indexes for a given database, you can issue the db.stats() method and sum the dataSize and indexSize fields.

db.stats(1024*1024*1024).dataSize + db.stats(1024*1024*1024).indexSize

The rate is based on your having 28 snapshots at steady state:

  • The six-hour snapshots are kept for two days;
  • The daily snapshots for one week,
  • The weekly snapshots for one month,
  • The monthly for one year.

Adding that up, you get 8 + 5 + 3 + 12 = 28 snapshots. We adjust the backup rate daily based on the following formula:

backupRatePerMonth = $1.25 + snapshotAtSteadyState/28 * $1.25

Changing the snapshot frequency or retention period affects the base rate per GB. See Snapshot Schedule for more information.

Examples

  • For a three-member replica set with 30GB of data, Atlas charges US$72.50 each month (using the default backup rate).

    (30GB - 1GB) × US$2.50 = US$72.50

  • A sharded cluster with 3 shards contains 90GB of data, with each shard containing 30GB of data each. The config server replica set contains 5GB of data.

    For this sharded cluster, Atlas charges US$227.50 per month (using the default backup rate).

    ((30GB - 1GB) × US$2.50) × 3) + ((5GB - 1GB) × US$2.50) = US$227.50

Cloud Provider Snapshots

The backup cost for Cloud Provider Snapshots is the total size of all snapshots per GB per month. The rate per GB depends on the region of the cluster. For multi-region clusters, the snapshot storage location depends on the location of the replica set member targeted for snapshots. The rate per GB therefore depends on the region of the targeted replica set member at the time of the snapshot.

AWS Cloud Provider Snapshots supports incremental snapshots, where a new snapshot saves only the data that changed after your most recent snapshot. For example, a cluster with 10GB of data and 3 snapshots may require less than 30GB of total snapshot storage depending on how data changed between snapshots.

If the existing snapshot storage volume becomes invalid, Atlas creates a new snapshot storage volume in the same region as the cluster’s current primary and takes a full-copy snapshot. Atlas continues using that primary and its AWS region for snapshots and snapshot storage. This may result in a higher invoice for the few days required to re-establish incremental snapshots. The cost per GB for snapshot storage may also change depending on the region of the new snapshot target. For more information on how Atlas manages snapshot storage, see Cloud Provider Snapshots.

When restoring a cluster using a manual download via HTTPS, Atlas also charges per-hour that the download link remains active. Contact MongoDB Support for more information. From the Atlas project or cluster view, click Support in the left-hand navigation bar.

Note

Backup snapshots which are KMS encrypted are not downloadable.

The backup cost for cloud provider snapshots is the total size of all snapshots per GB per month. The rate per GB depends on the region of the cluster. For multi-region clusters, the rate per GB depends on the cluster’s preferred region.

Example

For a three member replica set deployed to the Azure useast2 region (Virginia, USA) with three snapshots of 10, 20, and 30GB respectively, Atlas charges US$20.40.

(10GB * US$0.34) + (20GB * US$0.34) + (30GB * US$0.34)

Note

The US$0.34 rate per GB is specific to the Azure useast2 region at the time of writing. Atlas displays the most current cost per GB for the cluster’s selected region during cluster configuration. See Tutorial: Create a New Cluster or Modify a Cluster for more information on cluster configuration.

When restoring a cluster using a manual download via HTTPS, Atlas also charges per-hour that the download link remains active. Contact MongoDB Support for more information. From the Atlas project or cluster view, click Support in the left-hand navigation bar.

Note

Backup snapshots which are encrypted using Customer Key Management are not downloadable.

The backup cost for Cloud Provider Snapshots is the total size of all snapshots per GB per month. The rate per GB depends on the region of the cluster. For multi-region clusters, the snapshot storage location depends on the location of the replica set member targeted for snapshots. The rate per GB therefore depends on the region of the targeted replica set member at the time of the snapshot.

GCP Cloud Provider Snapshots supports incremental snapshots, where a new snapshot saves only the data that changed after your most recent snapshot. For example, a cluster with 10GB of data and 3 snapshots may require less than 30GB of total snapshot storage depending on how data changed between snapshots.

If the existing snapshot storage volume becomes invalid, Atlas creates a new snapshot storage volume in the same region as the cluster’s current primary and takes a full-copy snapshot. Atlas continues using that primary and its GCP region for snapshots and snapshot storage. This may result in a higher invoice for the few days required to re-establish incremental snapshots. The cost per GB for snapshot storage may also change depending on the region of the new snapshot target. For more information on how Atlas manages snapshot storage, see Cloud Provider Snapshots.

When restoring a cluster using a manual download via HTTPS, Atlas also charges per-hour that the download link remains active. Contact MongoDB Support for more information. From the Atlas project or cluster view, click Support in the left-hand navigation bar.

Note

Backup snapshots which are KMS encrypted are not downloadable.

If you have questions on Cloud Provider Snapshot backup sizing and pricing, please contact Atlas support by clicking Support from the left-hand navigation of the Atlas UI.

Point in Time Restores (AWS only)

AWS-hosted cluster owners may opt to enable Point in Time restores from cloud provider snapshots. PIT backups are billed based on the disk space occupied by the cluster’s oplog combined with the CPS backup size. Total cost is calculated based on tiered pricing, which varies by AWS region. The following example pricing table applies to the US East region:

Size on disk Cost per GB
0-5 GB free
5-100 GB $1.00
100-500 GB $0.50
>500 GB $0.25

Example

A cluster has a combined total snapshot and oplog size of 115 GB. The first 5 GB are free. The remaining 110 GB are billed at:

(95 * $1.00) + (15 * $0.50) = $102.50

PIT backups may be configured to cover a window of time specified by the user. Longer backup windows result in larger oplogs and higher backup costs.

Lowering the Monthly Rate

Continuous Backups
Lowering snapshot frequency or lowering snapshot retention lowers the cost per gigabyte. Increasing the snapshot frequency or the snapshot retention increases the cost per gigabyte. To modify the snapshot frequency or retention for a cluster, see Snapshot Schedule.
Cloud Provider Snapshots
The cost of backups is dependent on the region of the replica set member targeted for snapshots. Modifying the region configuration for your cluster may reduce the cost per gigabyte for snapshot storage. You can change regions by scaling the cluster.

BI Connector for Atlas

Excluding MongoDB Atlas Enterprise and MongoDB Atlas Platinum customers, if BI Connector for Atlas is enabled for your cluster:

  • The billing rate for the BI Connector for Atlas is described in the Cluster UI as a daily uplift on the cost of the associated cluster. You can view the rate when deploying your cluster or by modifying your cluster.
  • BI Connector for Atlas has a sustained-usage pricing. That is, the daily rate is charged only up to a maximum for the month.

Number of Servers

Atlas charges the cluster cost and data storage cost for each data-bearing server [1] in your cluster. For a replica set, the number of data-bearing servers equals the replication factor. For a sharded cluster, the number of data-bearing servers equals the replication factor multiplied by the number of shards.

If you enable sharding, Atlas also runs three config servers in addition to your data-bearing servers. Your selections for cluster tier and data storage do not affect the costs of the config servers. Config servers are charged at a separate rate. Their cost is reflected in the cost of the cluster.

[1](1, 2) For replica sets, the data-bearing servers are the servers hosting the replica set nodes. For sharded clusters, the data-bearing servers are the servers hosting the shards. For sharded clusters, Atlas also deploys servers for the config servers; these are charged at a rate separate from the cluster costs.