MongoDB Atlas
MongoDB Atlas spend, by project and cluster.
Cloud Intelligence™ imports your MongoDB Atlas cost and usage by organization, project, cluster, region and SKU, with your Atlas resource tags as labels. Right next to the rest of your cloud spend.
Service account · 6 months of history · Tracked hourly
MongoDB Atlas · October
what we import
Atlas data, in the dimensions you already use.
Every line item maps to standard Cloud Analytics dimensions for organization, project, cluster, region, service and SKU, and every Atlas resource tag comes through as a mongodb/ label.
5f1a2b3c4d5e6f7a8b9c0d1e64ab12cd34ef56ab78cd90efcheckout-prod64ab12cd34ef56ab78cd90ef:orders-prodN. VirginiaClustersATLAS_AWS_INSTANCE_M80_LOW_CPUserver hourswhat you can do with it
From the Atlas invoice to a decision
Cost by project and cluster
Slice by organization, project, cluster, SKU or any Atlas tag.
Spend by region
See where Atlas spend lands, by region, cluster and project.
Clusters vs data transfer
Instance hours and transfer cost side by side, by SKU.
MongoDB Intelligence
A preset dashboard, plus Atlas next to your other providers.
Budgets and alerts
Guardrails on Atlas spend, plus alerts when we spot cost anomalies.
Allocations
Put Atlas spend on teams by project or resource tag.
live in hours
Connect MongoDB Atlas in three steps
Create a service account.
In Atlas Access Manager, with billing viewer, read only and member permissions.
Connect in the catalog.
Paste the client ID and secret, and add our IPs to the access list.
Reports in hours.
Up to 6 months of history imported. We email you when it's ready.
Read-only billing access. Disconnect any time.
Start freeFrequently asked
questions
How do we connect MongoDB Atlas?
Open the MongoDB card in the integrations catalog and follow the wizard: create a service account in your Atlas organization, paste its client ID and secret, add our outbound IP addresses to its API access list, and test the connection. Repeat for each Atlas organization.
What permissions does the service account need?
Organization Billing Viewer, Organization Read Only and Organization Member. Creating it requires the Organization Owner permission in MongoDB, and we recommend a 365-day secret, which you can refresh later in the wizard.
Why do we add IP addresses to the access list?
All our requests to the Atlas API come from a fixed set of outbound IP addresses. Adding each one to the service account's API access list lets the connection through.
How much history do we get, and how fresh is it?
We import the last 6 months of billing and usage data on connect, which takes a few hours. Data is then tracked and reported hourly.
Which dimensions and labels are available?
Organization, project, cluster, region, service, SKU and unit map to standard Cloud Analytics dimensions, so Atlas sits in the same reports as your other providers. Every Atlas resource tag is pulled in automatically as a mongodb/ label for reports and allocations.
Which MongoDB products are supported?
MongoDB Atlas only. Cloud Manager, Ops Manager and self-hosted MongoDB deployments are not supported yet.
Connect MongoDB Atlas. Know what every cluster costs.
Free to start. Read-only. Reports in hours.