GetInfraDesk
DocsDashboard →
Documentation
📖 Overview
Getting Started
🚀 Quick Start
🔐 AWS IAM Permissions
đŸ›Ąī¸ Security & Privacy
Decision Intelligence
✋ Decision Inbox
📄 Decision Briefs
⚡ How Approved Actions Work
â†Šī¸ Rollback Guide
Connected Signals
🔗 Signal Hub Overview
â˜ī¸ Cloudflare
🤖 OpenAI Spend
📊 Datadog
🍃 MongoDB Atlas
Support
🔧 Troubleshooting
❓ FAQ
đŸŽ¯ Pilot Program
Need help?
Email us at support@getinfradesk.com
🍃

MongoDB Atlas Data Spend — Read-only beta

Reviews cluster sizing, paused clusters, and data spend risk signals. InfraDesk never pauses, resizes, deletes, or modifies clusters.

Required access

â€ĸ MongoDB Atlas Programmatic API key
â€ĸ Organisation Read Only or Project Read Only role
â€ĸ Public key + Private key
Create API key in Atlas →
Important: Atlas API keys may be restricted by API Access List (IP allowlist). If validation fails, add InfraDesk server egress IP to the Atlas API Access List, or set 0.0.0.0/0 for testing.

Decision signals

â€ĸ Paused cluster — still incurring storage/backup costs
â€ĸ Dev/test cluster on production-tier instance
â€ĸ Old MongoDB version — 2+ major versions behind
â€ĸ Single-node cluster — no replication redundancy
â€ĸ Large disk on small instance — storage efficiency review

Authentication

InfraDesk uses HTTP Digest Auth with Programmatic API keys (public + private key pair). Architecture is ready for Service Accounts/OAuth2 migration when MongoDB deprecates legacy API keys.