AWS OpsWorks vs Vagrant

• The interface is quite intuitive and allows you to discover and easily find what you want to do and what other features are within OpsWorks.
• Chef integration is pretty seamless and there are a good set of options and operating systems to choose from
• It makes things like auto scaling set up, either via load or time, more straight forward and intuitive than what you'd typically see via the EC2 console

Read full review

• Vagrant is decentralized so anyone can make a container package to get a project started. you aren't limited to wordpress, or even one style of wordpress install (you can make a sage.io wordpress environment).
• Vagrant easily lets you set ports and URLs for local development.
• I have yet to have a problem with Vagrant, as opposed to MAMP and DesktopServer, which both gave me SQL or other issues.

Read full review

• Getting up and running with OpsWorks is a very technical and potentially time-consuming process. You need to know the ins and outs of Chef/Puppet if you really want to get into it and there isn't a convenient way to test out the environment locally so debugging can be time-consuming.
• To take advantage of some of the newer AWS instance types you need to be running on a VPC, which again is a pain if you don't have a DevOps team.
• The error logs and monitoring metrics in OpsWorks are pretty basic and haven't changed much over the years.

Read full review

• Because Vagrant is a low-level tool with many ways to configure it, there is a steep learning curve. You don't just have to learn (or install) Vagrant, but also Virtualbox, Ansible and possibly some Vagrant plugins to keep boxes up to date.
• Support on Windows doesn't seem great. I'm a Mac guy, so it's been very difficult getting things to work as expected when a developer wants to work on Windows.
• Perhaps I didn't configure it correctly, but the default shared folders are not the best for performance. There are also frequently weird issues regarding file permissions.

Read full review

• OpsWorks has allowed some of our more simple application stacks to be implemented quickly and effectively. Whilst it is difficult to put actual numbers on it, it meant we could hit the ground running before tackling the more complex world of Cloudformation/Terraform to manage parts of our infrastructure.

Read full review

• Vagrant is free - It requires a bit of extra technical knowledge in terms of setup, but since it costs nothing it's an excellent resource
• It can be time consuming to learn, but once you get a good handle on it you're in good shape.

Read full review