> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt

# Additional Services

## Advanced Security

Atlas supports [Encryption at Rest using Customer Key Management](https://www.mongodb.com/docs/atlas/security-kms-encryption.md#std-label-security-kms-encryption) and [LDAP User Authentication and Authorization](https://www.mongodb.com/docs/atlas/security-ldaps.md#std-label-security-ldaps) in Atlas projects and clusters.

Excluding MongoDB Atlas Enterprise and MongoDB Atlas Platinum customers, Atlas charges a 15% uplift to the cost of each cluster with **LDAP User Authentication and Authorization** or **Encryption at Rest using Customer Key Management** enabled.

Configuring **LDAP User Authentication and Authorization** for a project enables the feature for all clusters in the project. Configuring **Encryption at Rest using Customer Key Management** for a project allows you to enable or disable the feature on a per-cluster basis.

**Note:**

In addition to the Atlas 15% uplift for clusters with LDAP User Authentication and Authorization or Encryption at Rest with customer KMS enabled, clusters using customer-managed keys incur costs from your cloud provider's key management service for API requests. Your cloud provider charges these costs based on your usage.

Atlas features such as [data validation](https://www.mongodb.com/docs/atlas/data-validation.md#std-label-data-validation) make additional KMS requests when operating on encrypted clusters. To learn more about KMS usage and costs, see [Data Validation KMS Usage.](https://www.mongodb.com/docs/atlas/security-kms-encryption.md#std-label-data-validation-kms-usage)

## Private Endpoints

MongoDB Atlas supports [private endpoints.](https://www.mongodb.com/docs/atlas/security-private-endpoint.md#std-label-private-endpoint-concepts)

You can configure private endpoints for many Atlas features, including:

- [dedicated clusters](https://www.mongodb.com/docs/atlas/create-database-deployment.md#std-label-dedicated-clusters)

- Online Archive

- Atlas Data Federation

- Atlas Stream Processing

dedicated clusters, Online Archive, and Data Federation use the billing model described in this section.

Atlas Stream Processing private endpoint billing charges depend on the private link connection created with the private endpoint. To learn more, see [Private Link.](https://www.mongodb.com/docs/atlas/billing/stream-processing-costs.md#std-label-asp-private-link-billing)

## Private Endpoint Billing

Atlas bills private endpoints based on:

- **Per-endpoint hourly charges** in each region where you deploy an Atlas private endpoint.

- **Usage-based charges** measured in Atlas [Private Endpoint Capacity Units.](https://www.mongodb.com/docs/atlas/billing/additional-services.md#std-label-privatelink-billing-cu)

These charges apply to dedicated clusters, Online Archive, and Data Federation.

Select your cloud provider to view private endpoint billing details.

MongoDB Atlas supports private endpoints on AWS (Amazon Web Services) using the [AWS PrivateLink](https://aws.amazon.com/privatelink/) feature.

For Atlas services that use AWS PrivateLink private endpoints (for example, [dedicated clusters](https://www.mongodb.com/docs/atlas/create-database-deployment.md#std-label-dedicated-clusters), Online Archive, and Data Federation), Atlas charges you based on your usage across the following dimensions:

- Atlas [Private Endpoint](https://www.mongodb.com/docs/atlas/billing/additional-services.md#std-label-privatelink-billing-endpoint): The sum of the hourly costs incurred to host private endpoints in all AWS (Amazon Web Services) regions.

- Atlas [Private Endpoint Capacity Units](https://www.mongodb.com/docs/atlas/billing/additional-services.md#std-label-privatelink-billing-cu): The sum of the hourly costs incurred to process traffic to private endpoints.

- Atlas [AWS Data Transfer (Same Region)](https://www.mongodb.com/docs/atlas/billing/additional-services.md#std-label-privatelink-billing-data-transfer): The cost of the intra-regional data transfer that serving your private endpoints requires.

In addition to the costs Atlas charges you, AWS (Amazon Web Services) charges you for each VPC (Virtual Private Cloud) interface endpoint you create. To ensure cluster availability in the event of a widespread network outage, create VPC (Virtual Private Cloud) interface endpoints in at least two availability zones per region. AWS (Amazon Web Services) also charges you for the data volume each VPC (Virtual Private Cloud) interface endpoint processes.

**See also:**

[AWS PrivateLink Pricing.](https://aws.amazon.com/privatelink/pricing/)

### Atlas Private Endpoint

Atlas charges hourly for each region to which you deploy a private endpoint. The [hourly cost](https://www.mongodb.com/docs/atlas/billing/additional-services.md#std-label-pl-region-rates) varies by region.

### Atlas Private Endpoint Capacity Units

Additionally, Atlas charges you per hour based on the traffic that your private endpoint processes. The [hourly cost](https://www.mongodb.com/docs/atlas/billing/additional-services.md#std-label-pl-region-rates) varies based on the amount of traffic and the region to which your private endpoint is deployed.

Atlas private endpoint capacity units measure the dimensions on which the Atlas private endpoint processes your traffic:

- **New connections or flows**: Number of newly established connections or flows per second.

- **Active connections or flows**: Peak concurrent connections or flows, sampled per minute.

- **Processed bytes**: The number of bytes processed by the private endpoint in Gigabytes (GB).

For TCP traffic, an Atlas private endpoint capacity unit contains:

- **New connections or flows**: 800 new TCP connections per second.

- **Active connections or flows**: 100,000 active TCP connections (sampled per minute).

- **Processed bytes**: 1 GB per hour.

For UDP traffic, an Atlas private endpoint capacity unit contains:

- **New connections or flows**: 400 new UDP flows per second.

- **Active connections or flows**: 50,000 active UDP flows (sampled per minute).

- **Processed bytes**: 1 GB per hour.

For TLS traffic, an Atlas private endpoint capacity unit contains:

- **New connections or flows**: 50 new TLS connections or flows per second.

- **Active connections or flows**: 3,000 active TLS connections or flows (sampled per minute).

- **Processed bytes**: 1 GB per hour.

Atlas charges you only for the dimension that has the highest usage during each hour across all traffic types.

The following example shows a breakdown of costs for one hour of TLS (Transport Layer Security) network traffic to a private endpoint in the `us-east-1` region:

| Dimension | Amount | Atlas Private Endpoint Capacity Units Consumed |
| --- | --- | --- |
| New connections or flows | 25 | .50 |
| Active connections or flows | 1500 | .50 |
| Processed bytes | 2.5 GB | 2.5 |

The **Processed bytes** dimension has the largest capacity unit consumption rate. For this hour, Atlas charges you the following for using Atlas private endpoint capacity units in the `us-east-1` region:

| Capacity Units | Region Rate per Capacity Unit | Fixed Cost | Total |
| --- | --- | --- | --- |
| 2.5 | $0.0120 | $0.045 | $0.075 `0.045 + (2.5 capacity units * 0.0120)` |

### Atlas AWS Data Transfer (Same Region)

Atlas routes private endpoint traffic through an AWS (Amazon Web Services) Network Load Balancer that uses cross-zone load balancing. If the load balancer and the target node run in different availability zones, the traffic between them incurs intra-regional data transfer costs. Atlas meters this traffic and bills it as `Atlas AWS Data Transfer (Same
        Region)`. This metering applies to usage on or after May 1, 2025.

These charges appear at the project level without a cluster name. Atlas provisions one load balancer for each VPC (Virtual Private Cloud) rather than for each cluster, so the load balancer carries no cluster identity. If your project contains multiple clusters, you can't attribute these charges to a specific cluster.

Each private endpoint charge covers a distinct cost. No charge duplicates another:

| Charge | Description |
| --- | --- |
| Atlas Private Endpoint | Hourly cost to run the load balancer. |
| Atlas Private Endpoint Capacity Units | Resources that the load balancer consumes to process your traffic. |
| Atlas AWS Data Transfer (Same Region) | Data that the load balancer transfers between availability zones in the same region. |

To learn more about how Atlas charges for data transfer, see [Data Transfer Costs.](https://www.mongodb.com/docs/atlas/billing/data-transfer-costs.md#std-label-data-transfer-costs)

### AWS PrivateLink Rates by Region

Atlas rates for using the AWS PrivateLink feature vary by region:

**Note:**

The rates listed below are in addition to what AWS (Amazon Web Services) charges you for each VPC (Virtual Private Cloud) interface endpoint you create. To learn more, see [AWS PrivateLink Pricing.](https://aws.amazon.com/privatelink/pricing/)

| AWS (Amazon Web Services) region | Hourly Cost per Private Endpoint | Cost per Atlas Private Endpoint Capacity Unit |
| --- | --- | --- |
| `us-east-1` N. Virginia | $0.0450 | $0.0120 |
| `us-east-2` Ohio | $0.0450 | $0.0120 |
| `us-west-1` N. California | $0.0504 | $0.0120 |
| `us-west-2` Oregon | $0.0450 | $0.0120 |
| `ca-central-1` Canada | $0.0495 | $0.0132 |
| `mx-central-1` Mexico City | $0.0473 | $0.0126 |
| `sa-east-1` Sao Paulo | $0.0680 | $0.0165 |
| `eu-north-1` Stockholm | $0.0479 | $0.0114 |
| `eu-west-1` Ireland | $0.0504 | $0.0120 |
| `eu-west-2` London | $0.0529 | $0.0120 |
| `eu-west-3` Paris | $0.0529 | $0.0126 |
| `eu-central-1` Frankfurt | $0.0540 | $0.0120 |
| `eu-central-2` Switzerland | $0.0594 | $0.0132 |
| `eu-south-1` Spain | $0.0504 | $0.0160 |
| `me-south-1` Bahrain | $0.0554 | $0.0132 |
| `me-central-1` UAE | $0.0564 | $0.0179 |
| `ap-northeast-1` Tokyo | $0.0486 | $0.0120 |
| `ap-northeast-2` Seoul | $0.0450 | $0.0120 |
| `ap-south-1` Mumbai | $0.0478 | $0.0120 |
| `ap-south-2` Hyperabad | $0.0478 | $0.0120 |
| `ap-southeast-1` Singapore | $0.0504 | $0.0120 |
| `ap-southeast-2` Sydney | $0.0504 | $0.0120 |
| `ap-southeast-3` Melbourne | $0.0504 | $0.0120 |
| `ap-east-1` Hong Kong | $0.0554 | $0.0132 |

### Remote Region

Atlas charges an additional hourly cost for each active remote region with cross-region private endpoint connectivity.

- **Hourly Cost per Active Remote Region:** $0.05 per hour for each active remote region.

A remote region is considered active when at least one interface endpoint from that region is connected to the private endpoint service. You are charged for each hour (or partial hour) that a remote region is active.

**Note:**

This charge applies in addition to the standard private endpoint and capacity unit charges. If you configure a remote region but do not connect any endpoints from that region, you are not charged for that region.

MongoDB Atlas supports private endpoints on Microsoft Azure using the [Azure Private Link](https://azure.microsoft.com/en-us/services/private-link/) feature.

For Atlas services that use Azure Private Link private endpoints (for example, [dedicated clusters](https://www.mongodb.com/docs/atlas/create-database-deployment.md#std-label-dedicated-clusters), Online Archive, and Data Federation), Atlas charges you based on your usage across the following dimension:

- Atlas Private Endpoint Capacity Units: Each unit equals 1 GB of data processed through the entire Azure Private Link. Both incoming and outgoing data incurs charges.

**See also:**

[Azure Private Link Pricing.](https://azure.microsoft.com/en-us/pricing/details/private-link/)

**Example:**

1 GB of data into MongoDB via Azure Private Link equals 1 Private Endpoint Capacity Unit consumed ($0.03).

### Azure Private Link Rates by Region

Atlas rates for using the Azure Private Link feature vary by region:

**Note:**

The rates listed below are in addition to what Microsoft Azure charges you for each private endpoint you create.

| Azure region | Cost per 1 GB Increment |
| --- | --- |
| `australiaeast` New South Wales | $0.0300 |
| `australiasoutheast` Victoria | $0.0300 |
| `brazilsouth` Sao Paulo | $0.0300 |
| `canadacentral` Toronto, ON | $0.0300 |
| `canadaeast` Quebec City, QC | $0.0300 |
| `centralindia` Pune | $0.0300 |
| `centralus` Iowa | $0.0300 |
| `eastasia` Hong Kong | $0.0300 |
| `eastus` Virginia | $0.0300 |
| `eastus2` Virginia | $0.0300 |
| `francecentral` Paris | $0.0300 |
| `germanynorth` Berlin | $0.0300 |
| `germanywestnorth` Frankfurt | $0.0300 |
| `japaneast` Tokyo | $0.0300 |
| `japanwest` Osaka | $0.0300 |
| `koreacentral` Seoul | $0.0300 |
| `koreasouth` Busun | $0.0300 |
| `northcentralus` Illinois | $0.0300 |
| `northeurope` Ireland | $0.0300 |
| `norwayeast` Oslo | $0.0300 |
| `qatarcentral` Qatar | $0.0300 |
| `southafricanorth` Johannesburg | $0.0300 |
| `southcentralus` Texas | $0.0300 |
| `southeastasia` Singapore | $0.0300 |
| `southindia` Chennai | $0.0300 |
| `switzerlandnorth` Zurich | $0.0300 |
| `switzerlandwest` Geneva | $0.0300 |
| `uaecentral` Abu Dhabi | $0.0300 |
| `uaenorth` Dubai | $0.0300 |
| `uksouth` London, England | $0.0300 |
| `ukwest` Cardiff, Wales | $0.0300 |
| `westcentralus` Wyoming | $0.0300 |
| `westeurope` Netherlands | $0.0300 |
| `westindia` Mumbai | $0.0300 |
| `westus` California | $0.0300 |
| `westus2` Washington | $0.0300 |

MongoDB Atlas supports private endpoints on Google Cloud using the [GCP Private Service Connect](https://cloud.google.com/vpc/docs/private-service-connect) feature.

For [dedicated clusters](https://www.mongodb.com/docs/atlas/create-database-deployment.md#std-label-dedicated-clusters), Atlas charges you based on your usage across the following dimensions:

### Atlas Private Endpoint

Atlas charges hourly for each project and region in which you deploy a private endpoint. The [hourly cost](https://www.mongodb.com/docs/atlas/billing/additional-services.md#std-label-psc-region-rates) varies by region.

**Note:**

Atlas charges a flat hourly rate for the region, regardless of the internal resources created to support the private endpoint service.

### Atlas Private Endpoint Capacity Units

Atlas also charges you based on your usage with Private Endpoint Capacity Units. Each unit equals 1 GB of data processed through Google Cloud private endpoints. Both incoming and outgoing data incur charges.

In addition to the costs Atlas charges you, Google Cloud charges you for each Private Service Connect endpoint (forwarding rule) created to access Atlas.

**See also:**

[GCP Private Service Connect Pricing](https://cloud.google.com/vpc/pricing#psc-forwarding-rules)

### Google Cloud Private Service Connect Rates by Region

Atlas rates for using GCP Private Service Connect vary by region:

**Note:**

The rates listed below are in addition to what Google Cloud charges you for each Private Service Connect endpoint you create.

For Google Cloud, this billing model applies to dedicated clusters. Data Federation does not support GCP private link.

| Customer Subnet Region | Hourly Cost per Private Endpoint | Cost per Atlas Private Endpoint Capacity Unit |
| --- | --- | --- |
| `us-east1` South Carolina | $0.0500 | $0.0200 |
| `us-east4` N. Virginia | $0.0560 | $0.0200 |
| `us-east5` Columbus | $0.0500 | $0.0400 |
| `us-west1` Oregon | $0.0500 | $0.0200 |
| `us-west2` Los Angeles | $0.0560 | $0.0200 |
| `us-west3` Salt Lake City | $0.0560 | $0.0200 |
| `us-west4` Las Vegas | $0.0560 | $0.0200 |
| `us-central1` Iowa | $0.0500 | $0.0200 |
| `us-south1` Dallas | $0.0590 | $0.0389 |
| `northamerica-northeast1` Montreal | $0.0560 | $0.0200 |
| `northamerica-northeast2` Toronto | $0.0560 | $0.0200 |
| `southamerica-east1` Sao Paulo | $0.0760 | $0.0200 |
| `southamerica-west1` Santiago | $0.0760 | $0.0200 |
| `europe-central2` Warsaw | $0.0600 | $0.0200 |
| `europe-north1` Finland | $0.0560 | $0.0200 |
| `europe-west1` Belgium | $0.0500 | $0.0200 |
| `europe-west2` London | $0.0600 | $0.0200 |
| `europe-west3` Frankfurt | $0.0600 | $0.0200 |
| `europe-west4` Netherlands | $0.0560 | $0.0200 |
| `europe-west6` Zurich | $0.0660 | $0.0200 |
| `europe-west8` Milan | $0.0585 | $0.0387 |
| `europe-west9` Paris | $0.0585 | $0.0387 |
| `europe-west12` Turin | $0.0600 | $0.0400 |
| `europe-southwest1` Madrid | $0.0600 | $0.0392 |
| `austrailia-southeast1` Sydney | $0.0680 | $0.0200 |
| `austrailia-southeast2` Melbourne | $0.0680 | $0.0200 |
| `asia-east1` Taiwan | $0.0500 | $0.0200 |
| `asia-east2` Hong Kong | $0.0700 | $0.0200 |
| `asia-northeast1` Tokyo | $0.0760 | $0.0200 |
| `asia-northeast2` Osaka | $0.0760 | $0.0200 |
| `asia-northeast3` Seoul | $0.0760 | $0.0200 |
| `asia-south1` Mumbai | $0.0600 | $0.0200 |
| `asia-south2` Delhi | $0.0600 | $0.0200 |
| `asia-southeast1` Singapore | $0.0560 | $0.0200 |
| `asia-southeast2` Jakarta | $0.0760 | $0.0200 |
| `me-west1` Tel Aviv | $0.0550 | $0.0376 |
| `me-central1` Doha | $0.0615 | $0.0397 |

**Example:**

1 GB of data into Atlas via GCP Private Service Connect equals 1 Private Endpoint Capacity Unit consumed ($0.02).

## Database Auditing

Atlas supports database auditing. To learn more, see [Set up Database Auditing.](https://www.mongodb.com/docs/atlas/database-auditing.md#std-label-set-up-database-auditing)

Excluding MongoDB Atlas Enterprise and MongoDB Atlas Platinum customers, Atlas charges a 10% uplift to the hourly cost of all dedicated clusters. The 10% uplift applies to projects using Database Auditing.

## Charts for Atlas

Charts on Atlas is billed based on the volume of data transferred from the Charts web server to web browser clients. Each Charts instance includes `1 GB` of data transfers per month at no charge. After you use the included `1 GB`, each additional GB of data transfers is billed at a fixed rate.

**See also:**

[Charts on Atlas Pricing.](https://www.mongodb.com/docs/charts/pricing/)

## Atlas Online Archive

You may incur data transfer and compute costs for each Online Archive on your Atlas cluster. If you have Online Archive configured on your cluster, your Atlas invoice includes these costs as a line item.

**See also:**

[Atlas pricing page](https://www.mongodb.com/cloud/atlas/pricing)

## Free Cluster Backups

**Important:**

Backups for Free clusters are available as a [private preview](https://www.mongodb.com/docs/preview-features/). The feature and corresponding documentation might change at any time during the preview.

Atlas offers a backup subscription for Free clusters (`M0`). When you enable backups for a Free cluster, Atlas takes daily snapshots of your cluster and retains the last four snapshots.

Atlas bills you $0.10 per day for each Free cluster with backups enabled, up to a maximum of $3.00 per month per cluster. You can cancel the subscription at any time.

If you pause your Free cluster, Atlas pauses backups and subscription billing until you resume the cluster.

To learn how to enable and manage Free cluster backups, see [Free Cluster Backups.](https://www.mongodb.com/docs/atlas/backup/cloud-backup/free-cluster-backup.md#std-label-free-cluster-backups)

## Support Plan

If you have a paid [support plan](https://www.mongodb.com/docs/atlas/support.md#std-label-atlas-support), your invoice lists the total monthly support cost in the Summary section. Support cost line items appear in the Details section.

Atlas distributes support charges proportionally across the cloud providers that host your usage. The Details section lists a separate support line item for each cloud provider you use. Support usage that isn't associated with a cloud provider appears under Other Atlas Usage. Atlas calculates your support minimum once per month for your entire organization, separately from these per-provider charges.