AWS OpsWorks is a configuration management service that provides managed instances of Chef and Puppet.
N/A
AWS Systems Manager
Score 7.2 out of 10
N/A
AWS Systems Manager allows users to centralize operational data from multiple AWS services and automate tasks across your AWS resources. With it, users can create logical groups of resources such as applications, different layers of an application stack, or production versus development environments. Systems Manager allows users to select a resource group and view its recent API activity, resource configuration changes, related notifications, operational alerts, software inventory, and patch…
$0.20
Per Million Calls
Pricing
AWS OpsWorks
AWS Systems Manager
Editions & Modules
No answers on this topic
AppConfig
$0.20
Per Million Calls
OpsCenter
$2.97
Per 1,000 Items
Offerings
Pricing Offerings
AWS OpsWorks
AWS Systems Manager
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
AWS OpsWorks
AWS Systems Manager
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.
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.
When you have a process running in aws that needs to copy files to group of instances as part of the process Installing software on a group of machines Adding Cloudwatch agent to instance.
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.