For our organization, having AWS OpsWorks made it easier for our devops area to automate an infinity of manual processes - each time we …
We currently use AWS OpsWorks in hosting our application core. It forms the foundation of our product, which is used by the entire company;…
We currently use Opsworks to help orchestrate parts of our infrastructure and manage instances via Chef recipes. It is used for the …
Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of AWS OpsWorks, and make your voice heard!
Entry-level set up fee?
- No setup fee
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
Would you like us to let the vendor know that you want pricing?
AWS OpsWorks is a configuration management service that provides managed instances of Chef and Puppet.
Companies can't remove reviews or game the system. Here's why
- Automatic deployment of Chef servers within AWS.
- Detection of problems in our instances through a connection by ssh and Inspec Scan.
- Correction of problems with Chef-Run, in addition to that it achieves the validation and confirmation of the instance ready to operate.
- It can only be run in AWS environments and not outside of this cloud environment.
- In environments with a large number of nodes and instances it becomes complex.
- In older versions of Chef, interaction with OpsWorks is complicated
- OpsWorks provides a relatively simple interface for connecting with the ELB and bringing up/taking down EC2 instances.
- OpsWorks stacks and layers allow you to logically organize your infrastructure to match your system architecture.
- OpsWorks can assist in monitoring instance health and has a decent auto-scaling feature to recover from potential load-based outages.
- 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.
- 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
- There are no true deployment options, so you cannot specify rolling-deploys for example. It is possible to emulate some of these things, but it really is an exercise for the reader.
- Generally pushes you down the road of mutable infrastructure (as opposed to immutable infrastructure). It would be nice if there were better options around this.