You were redirected from a different version of the documentation. Click here to go back.

Deploy a Standalone MongoDB Instance


You can deploy a standalone MongoDB instance managed by Ops Manager. Use standalone instances for testing and development. Do not use these deployments, which lack replication and high availability, for production systems. For all production deployments use replica sets. See Deploy a Replica Set for production deployments.


You must provision a server to which to deploy. For testing purposes, you can use your localhost.



Click Deployment.


Click the Add button and select New Standalone.


Configure the standalone MongoDB instance.

Enter information as required and click Apply.

The Auth Schema Version field determines the schema for storing user data. MongoDB 3.0 uses a different schema for user data than previous versions. For compatibility information, see the MongoDB Release Notes.

For managed deployments running MongoDB 3.0 or later, you can add the engine option in Advanced Options to set which storage engine to use. For information on storage engines, see Storage in the MongoDB manual.

New in version 3.4: You can set the engine option to inMemory to use an in-memory storage engine in your deployment. For more information, see In-Memory Storage Engine in the MongoDB manual.

For descriptions of Advanced Options, see Advanced Options for MongoDB Deployments.


Click Review & Deploy to review your changes.


Review and approve your changes.

Ops Manager displays your proposed changes.

  1. If you are satisfied, click Confirm & Deploy.
  2. Otherwise, click Cancel and you can make additional changes.