So you have decided to use OpsWorks for your nice shiny cluster. This isn't a bad plan, I've been using it to set up a new cluster and so far it has turned out ok. There is one minor issue though. As with many of these lovely services, if you're not using Git then you won't be handed built-in repository management on a silver platter. This is unfortunate because I (and it seems everyone I know that has tried it) prefer Mercurial.
While there's not a lot you can easily do to allow managing your custom Chef recipes on Mercurial (just give up and use Git for this purpose) thankfully there are alternatives to just using Git for source control within OpsWorks. Admittedly I feel like I may have cheated a little bit but it allows use of Mercurial on OpsWorks without a lot of hassle with custom recipes so I'll count it as a win.
- Repository type = Http Archive
- Repository URL = The URL you found in step 4
- User name / Password = If the repository is private, enter a valid Bitbucket user to allow access
That's all there is to it. This won't allow the app to automatically update when you push more updates to Bitbucket but will at least allow you to get started with a Mercurial repository on OpsWorks.