MongoDB Atlas

You are a MongoDB Atlas administrator. The user wants to set up a production MongoDB Atlas cluster with automated backups and monitoring enabled.

What to check first

• Verify you have a MongoDB Atlas account (create one at mongodb.com/cloud/atlas if needed)
• Confirm your IP address is whitelisted in MongoDB Atlas Network Access settings
• Check that you have access to generate API keys in your organization settings

Steps

1. Log into MongoDB Atlas and click "Create a Deployment" — choose "Build a Cluster"
2. Select your cloud provider (AWS, Google Cloud, or Azure) and region closest to your users
3. Choose cluster tier: M0 (free, 512 MB) for testing or M2/M5+ for production workloads
4. Set your cluster name (e.g., "production-cluster") and click "Create Deployment"
5. Wait 3–5 minutes for cluster initialization, then add a Database User via the "Database Access" tab with a strong password
6. Navigate to "Backup & Restore" in the left sidebar and enable "Continuous Cloud Backups" (set 7-day retention minimum for production)
7. Go to "Monitoring" tab and enable "Atlas Performance Advisor" and "Real-Time Performance Panel" to track query performance
8. Add IP whitelist entries under "Network Access" — use 0.0.0.0/0 only for development, restrict to specific IPs in production
9. Get your connection string from "Connect" button and test it with mongosh or your driver

Code

// Node.js example: Connect to MongoDB Atlas and verify monitoring setup
const { MongoClient } = require('mongodb');

const uri = 'mongodb+srv://username:password@production-cluster.mongodb.net/mydb?retryWrites=true&w=majority';

async function setupAndMonitor() {
  const client = new MongoClient(uri, {
    serverSelectionTimeoutMS: 5000,
    socketTimeoutMS: 5000,
  });

  try {
    // Connect to cluster
    await client.connect();
    console.log('✓ Connected to MongoDB Atlas cluster');

    const adminDb = client.db('admin');
    
    // Check server status
    const serverStatus = await adminDb.command({ serverStatus: 1 });
    console.log(`✓ Cluster uptime: ${Math.round(serverStatus.uptime / 3600)} hours`);

    // Create a test collection with monitoring
    const db = client.db('mydb');
    const collection = db.collection('test_collection');
    
    // Insert test document
    const result = await collection.insertOne({
      timestamp: new Date(),
      message: 'Atlas monitoring test',
      status: 'active'
    });
    console.log(`✓ Inserted document: ${result.insertedId}`);

    // Verify backup settings via serverStatus
    const replStatus = await adminDb.command({ replSetGetStatus:

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change