MongoDB Backup Setup

Overview

We run daily MongoDB backups for key databases and store the backup artifacts in S3.

Backup Flow

1. EventBridge Scheduler triggers the backup Lambda on schedule.
2. Lambda runs the backup workflow for configured MongoDB databases.
3. Backups are uploaded to S3.

AWS Resources

• Lambda function: mongo-backup-signups
• Scheduler: EventBridge Schedulers- one for each DB to be backed up (connected to the Lambda above)
• S3 bucket: mongodb-backups-auto-1

Databases Covered

• storydesk
• auth
• langing page signups

Renderboard (studio)

The S3 backup scheduler for renderboard (mongodb-renderboard-backup) is disabled. Renderboard runs on a paid Atlas cluster, which has Atlas Cloud Backup built in, so the S3 backup isn't needed. It would also time out anyway, since the DB is too large to back up within the 15 min Lambda limit.

Analytics Logs Cleanup

• Lambda function: mongo-studio-cleanup
• Scheduler: analytics-logs-cleanup — runs weekly (Monday 09:00 IST)

Strips bulky fields from renderboard.analyticsLogs docs older than 30 days, keeping only data.model, data.cost and data.usage. The docs are backed up to the renderboard-analytics-logs-archive S3 bucket before stripping.