What is this integration?
Manage MongoDB Atlas projects, clusters, and users with Monk.What Monk manages
- Project, Cluster, User
Obtaining Atlas Credentials
Before using MongoDB Atlas with Monk, you’ll need to create an Organization API Key in MongoDB Atlas.What You’ll Need
- Organization Name - Your MongoDB Atlas organization name or ID
- Service Account Client ID - Atlas API Public Key
- Service Account Client Secret - Atlas API Private Key
Step-by-Step
- Log into MongoDB Atlas at https://cloud.mongodb.com
- Click your organization name in the top left
- Go to Organization Settings (gear icon)
- Navigate to Access Manager → API Keys tab
- Click Create API Key
- Enter description: “Monk Deployment”
- Set Organization Permissions:
Organization Project CreatorProject Cluster ManagerProject User Admin
- Click Next
- Copy the Public Key (Client ID) - save this
- Copy the Private Key (Client Secret) - shown only once, save it now!
- Click Done
- Note your Organization Name from Organization Settings main page
Required Access Scope
Monk needs these specific permissions:- Organization Project Creator - To create Atlas projects for your deployments
- Project Cluster Manager - To provision and manage database clusters
- Project User Admin - To create database users for your applications
- Access existing projects or data outside what it creates
- Modify organization-level settings
- Access billing information
Security Best Practices
✅ Rotate keys periodically - Update API keys every 90 days ✅ Use project-specific keys when possible - If you only deploy to one project ✅ Monitor API key usage - Check Atlas Access Tracking logs ✅ Revoke unused keys - Remove old keys when no longer neededAuth
- Uses a Monk secret for API token (e.g., mongodb-atlas-token) and password secret for users
Getting Started
- Set secrets:
- Define resources (save as mongodb-atlas.yaml):
- Create/update:
Backup & Snapshot Actions (M10+ Clusters)
MongoDB Atlas provides comprehensive backup and restore capabilities for M10 and higher dedicated clusters.M0 free tier does not support backup API. M2 and M5 shared tiers also
lack backup support. For production deployments requiring backups, use M10+
dedicated clusters which include automated daily backups and point-in-time
restore capabilities.
| Action | Description |
|---|---|
get-backup-info | View backup configuration and status |
create-snapshot | Create an on-demand backup snapshot |
list-snapshots | List available snapshots |
describe-snapshot | Get detailed info about a specific snapshot |
delete-snapshot | Delete a backup snapshot |
restore | Restore from snapshot or point-in-time |
get-restore-status | Check restore job progress |
list-restore-jobs | View all restore jobs |

