TrustRadius
Good for simple stacks and getting going with AWS + ChefWe 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.,6,OpsWorks has allowed some of our more simple application stacks to be implemented quickly and effectively. Whilst it is difficult to put actual numbers on it, it meant we could hit the ground running before tackling the more complex world of Cloudformation/Terraform to manage parts of our infrastructure.,Terraform and Cloudformation
Unspecified
AWS OpsWorks
4 Ratings
Score 7.8 out of 101
TRScore

AWS OpsWorks Reviews

AWS OpsWorks
4 Ratings
Score 7.8 out of 101
Show Filters 
Hide Filters 
Filter 4 vetted AWS OpsWorks reviews and ratings
Clear all filters
Overall Rating
Reviewer's Company Size
Last Updated
By Topic
Industry
Department
Experience
Job Type
Role
Reviews (1-1 of 1)
  Vendors can't alter or remove reviews. Here's why.
Andrew Raines profile photo
March 22, 2018

AWS OpsWorks Review: "Good for simple stacks and getting going with AWS + Chef"

Score 6 out of 10
Vetted Review
Verified User
Review Source
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.
Read Andrew Raines's full review

AWS OpsWorks Scorecard Summary

About AWS OpsWorks

AWS OpsWorks is a configuration management service that provides managed instances of Chef and Puppet.

AWS OpsWorks Technical Details

Operating Systems: Unspecified
Mobile Application:No