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
For our organization, having AWS OpsWorks made it easier for our devops area to automate an infinity of manual processes - each time we increased the quantities, the process became more and more cumbersome. For this reason OpsWorks and its execution of scripts streamlined the deployment and maintenance of our Chef Instances .
On the other hand, our monitoring area has managed to collect automatically all the performance data of the operations, which represents great visibility for the management and administration areas of the corporation.
- 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 facilitates the management, monitoring and maintenance of the complete stack of Chef's infrastructure, to be part of AWS has a large community for support and assistance, it also concentrates a lot of documentation that can empower our devops area to shorten the curve Learning. Good tool to automate tasks for the company's devops and IT staff.
We currently use AWS OpsWorks in hosting our application core. It forms the foundation of our product, which is used by the entire company; however, only a few select members of our backend team manage it directly. AWS OpsWorks allows us to leverage the powerful EC2 infrastructure without having to build out a custom instance management system.
- 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.
Scenarios where OpsWorks is well suited:
- You have a team that's heavily invested in AWS infrastructure and want to simplify the management of your EC2 instances.
- You have a large proficient DevOps team and you're willing to put into the time to learn Chef and dig deep into operations management.
- You don't have a proficient DevOps team or development team that is able to dedicate a considerable amount of time to learn Chef and get your instances configured.
- You want to build an application that is infrastructure-agnostic that can easily be moved to different hosting on short notice.
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.
We currently use Opsworks to help orchestrate parts of our infrastructure and manage instances via Chef recipes. It is used for the majority of the backend services we produce. It gives us a framework around which to hang our applications and an easy way to rebuild servers, auto-scale services and do basic monitoring.
- 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.
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.