Skip to main content
Choose how your app’s MongoDB runs and let Monk create it and connect it to your services. This guide covers MongoDB Atlas in detail, plus the other two options.

​
Before you start

  • Your app already uses MongoDB (a driver such as mongodb, mongoose or pymongo). Monk runs the database. Your code connects to it.
  • For Atlas: an Atlas organization API key. See MongoDB Atlas credentials for the permissions it needs. Monk asks for it through a form.
  • For DigitalOcean: DigitalOcean credentials.

​
Pick an option

Atlas tiers include a free shared tier (M0), dedicated clusters (M10 and up) and Flex. Check Atlas’s own pricing for each.

​
Ask Monk

Or be specific:

​
What you review

  1. Credentials. The Atlas API key form opens in the local dashboard. Enter the keys there, never in chat.
  2. The plan. For Atlas it shows the project, cluster tier, cloud and region, the database user Monk creates and the network access it adds for your cluster. Nothing is created until you approve.

​
What you get

  • A MongoDB database on the option you chose
  • A database user for your app and a connection string injected into the services that use it
  • For Atlas: a project in your organization, and network access for your cluster’s addresses

​
Backups

On Atlas dedicated tiers, the integration provides snapshot and restore actions. Ask Monk to run them and approve each one:
The free tier (M0) has no backup actions. See Back up and restore.

​
Switching options later

Monk creates the new database and updates connection settings after you approve the plan. It does not copy your data. Export from the old database and import into the new one (for example with mongodump and mongorestore) before you switch, then remove the old database.

​
Next