Skip to main content

MongoDB Atlas Billing

Use MongoDB Atlas Billing to ingest Atlas invoice and usage cost data into Cloudaware Cost Management.

info
  • Audience: Cloudaware administrators, FinOps, finance teams
  • Outcome: MongoDB Atlas billing data is discovered and ingested into Cloudaware

This guide covers:

  • Atlas organization billing access.
  • Required Atlas organization roles.
  • Programmatic access requirements.
  • MongoDB Atlas Billing discovery in Cloudaware.
  • Verification and troubleshooting steps.

Prerequisites​

  • MongoDB Atlas integration configured in Cloudaware (see MongoDB Atlas).
  • MongoDB Atlas organization with billing enabled.
  • Atlas organization ID for each organization that Cloudaware should ingest.
  • Atlas programmatic access configured for the organization.
  • API key used by Cloudaware with the Organization Billing Viewer role for read-only billing access.
tip

MongoDB recommends service accounts for Atlas Admin API access. Cloudaware currently supports authentication using API keys, which MongoDB considers a legacy authentication method.

How It Works​

  • MongoDB Atlas generates billing data at the organization level.
  • Cloudaware uses Atlas Admin API to discover invoices and retrieve billing reports.
  • After the required read access is granted, Cloudaware discovers the billing source and imports cost data automatically.

Configure Atlas Billing Access​

  1. Sign in to the MongoDB Atlas console with Organization Owner permissions.
  2. Select the Atlas organization that contains the billing data.
  3. Open Access Manager for the organization.
  4. Create or select the API key used by Cloudaware.
  5. Assign the Organization Billing Viewer role.
  6. Save the public key and private key.
  7. Copy the Atlas organization ID.
note

Atlas displays an API private key only when the key is created. Save it securely before leaving the page.

MongoDB Atlas Billing Discovery in Cloudaware​

Cloudaware automatically discovers MongoDB Atlas billing integrations once the prerequisites are met.

To review discovered billing sources:

  1. In Cloudaware, go to Admin.
  2. Locate MongoDB Atlas Billing under Billing integrations.
  3. Click CONFIGURED to see discovered billing sources.
  4. Review the list of MongoDB Atlas billing integrations and check the Status column:
    • Green status indicates successful configuration and data access.
    • Red status indicates a problem; verify Atlas roles, keys, and organization ID.

Verification​

After initial setup:

  • In Cloudaware Admin -> MongoDB Atlas Billing, verify that the integration status is green.
  • In Cost Management dashboards, verify that Atlas spend appears for the expected billing periods.
  • Compare total Atlas costs in Cloudaware with the Atlas Billing and Invoices pages for the same organization and month.
  • If the organization uses cross-organization billing, confirm that linked organization invoices appear as expected.

Troubleshooting​

MongoDB Atlas Billing Data Not Accessible​

  • In MongoDB Atlas:
    • Open Access Manager for the organization.
    • Confirm that the API key used by Cloudaware has Organization Billing Viewer access.
    • Confirm that the organization ID in Cloudaware matches the Atlas organization that owns the billing data.
    • Verify that invoices exist for the selected billing period.

Cloudaware MongoDB Atlas Billing Integration Red or Missing​

  • In Cloudaware, go to Admin:
    • Open the MongoDB Atlas section. Check that the Atlas integration is configured and has green status.
    • Open the MongoDB Atlas Billing section. Confirm that discovered billing integrations have green status.
  • If status remains red:
    • Recheck Atlas programmatic access credentials.
    • Confirm that the credentials have billing access at the organization level.

Security Notes​

  • Use Organization Billing Viewer for least-privilege read-only billing access.
  • Use a dedicated API key for Cloudaware instead of a personal user.
  • Store client secrets or API private keys only in approved credential stores.
  • Rotate Atlas keys regularly and update the Cloudaware integration after rotation.
  • Review Atlas organization access regularly.
On this page