AWS OpsWorks is a configuration management service that provides managed instances of Chef and Puppet.
N/A
Pricing
AWS OpsWorks
Editions & Modules
No answers on this topic
Offerings
Pricing Offerings
AWS OpsWorks
Free Trial
No
Free/Freemium Version
No
Premium Consulting/Integration Services
No
Entry-level Setup Fee
No setup fee
Additional Details
—
More Pricing Information
Community Pulse
AWS OpsWorks
Considered Both Products
AWS OpsWorks
Verified User
Employee
Chose AWS OpsWorks
Opsworks will become EOL soon and we have been using the recommended Systems Manager solution recently which offers a lot more flexibility in terms of orchestration technology (ie. higher Chef versions) and easier to integrate with even more AWS services.
We first got up and running with OpsWorks about 6~7 years ago, at a time when many of its competitors were far more limited. At the time it made sense as the logical tool to go with and getting up and running on the AWS infrastructure was beneficial for the scale we were …
OpsWorks isn't really a direct competitor to Terraform/Cloudformation, but it does allow you to do some of the more simple things on offer quite quickly and effectively. Opsworks was used for this reason, along with existing internal knowledge of Chef. Along with some of the …
Where you already have some Chef recipes to build your application boxes and are happy to run directly on VMs, OpsWorks really shines. It won't do anything too complex for you, so it only really works well for simple stacks (load balancers, application layers, database layers). If you want to do more complex infrastructure, Cloudformation or Terraform are probably worth looking at.
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.
Unless you pay for a pricey support package getting support on OpsWorks will be pretty slow. Documentation is also relatively limited and sometimes hard to follow when compared to competitors. Generally, we've been able to get the answers we need from OpsWorks support when we run into problems but don't expect rapid responses.
OpsWorks isn't really a direct competitor to Terraform/Cloudformation, but it does allow you to do some of the more simple things on offer quite quickly and effectively. Opsworks was used for this reason, along with existing internal knowledge of Chef. Along with some of the other services on offer from AWS, it is good to use as a stepping stone along the way when building your systems - or perhaps it would be entirely suitable for a fairly simple project.