Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Pull request Compare This branch is 266 commits ahead of jerrod:master.
Fetching latest commit...
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.

ey-cloud-recipes/mongodb v2.0.2

A chef recipe for enabling mongodb v2.0.2 on Engine Yard AppCloud. This recipe downloads the latest version binary from 10gen and sets up a 3 node MongoDB Replica Set.

It makes a few assumptions:

  • You will be running MongoDB on a utility instance(s).
  • You will be using Replica sets.

MMS support

The recipe will also install Mongo Monitoring Service (MMS) on a solo or db_master. You will need to provide your api & secret keys. See for more information.

Using it

  • add the following to main/recipes/default.rb,

require_recipe "mongodb"

  • Upload recipes to your environment

ey recipes upload -e <environment>

  • Add an utility instance with the following naming scheme(s)

    • For an replica set,
      • mongodb_repl#{setname}_1
      • mongodb_repl#{setname}_2
      • mongodb_repl#{setname}_3
      • ...
  • Drops /data/#{}/shared/config/mongo.yml with all the information needed to connect to MongoDB.


Replica sets should normally be in a size of 3 or greater. This recipe does not and will not support 32-bit instances.
Please ensure you use 64-bit instances when you create the Utility slices.


  • The usage of #{} is an indicator of the application name set on the Applications Section on the Dashboard.


Things (currently) lacking from this recipe:

  • Ability to set up scheduled backups of your MongoDB database
  • Ability to set up a sharded installation
  • Arbiter support

Known Bugs

Previous versions of this recipe used the legacy-static binary. This is no longer needed. Please fetch latest changes as this recipe is being frequently maintained.


If you find bugs, please open a Zendesk ticket or submit a pull request.


Thanks to Edward Muller and Dan Peterson for the original awesome recipe to begin with.

Something went wrong with that request. Please try again.