AWS OpsWorks is a configuration management service that provides managed instances of Chef and Puppet.
N/A
Ansible
Score 8.9 out of 10
N/A
The Red Hat Ansible Automation Platform (acquired by Red Hat in 2015) is a foundation for building and operating automation across an organization. The platform includes tools needed to implement enterprise-wide automation, and can automate resource provisioning, and IT environments and configuration of systems and devices. It can be used in a CI/CD process to provision the target environment and to then deploy the application on it.
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.
The thing I mentioned earlier where we're constantly dealing with federal regulations or new agents that they want us to install and deploy and just getting those out in a consistent manner in a canned installation via Playbook is ideal
Makes it easy to create and share automation in one central hub.
Ansible content collections give me the ability to reuse code, making it rapid to carry out complex IT processes.
Event-driven automation allows me to reduce manual tasks: it is rapid to know which action to take and respond automatically by receiving events from external apps automatically.
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.
Workflows should have more flexible paths than just success or failure.
The upgrade process can be challenging with differences in security and environment.
There is an opportunity to add CICD functionality into the tool.
For development, it would be nice to have the option of editing a repo directly from AAP to allow quick tests/reruns. Then, allow it to push the updates back or create a new branch/PR in GitHub.
The RBAC is good but could use improvements. One example would be an option that allows admins to assume the access of another user to validate it works as expected.
Great in almost every way compared to any other configuration management software. The only thing I wish for is python3 support. Other than that, YAML is much improved compared to the Ruby of Chef. The agentless nature is incredibly convenient for managing systems quickly, and if a member of your term has no terminal experience whatsoever they can still use the UI.
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.
There is a lot of good documentation that Ansible and Red Hat provide which should help get someone started with making Ansible useful. But once you get to more complicated scenarios, you will benefit from learning from others. I have not used Red Hat support for work with Ansible, but many of the online resources are helpful.
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.
AAP doesn't truly stack up against any of the products mentioned except for Aria Automation. But, it is extensible and open and has a lower cost to entry.
