What users are saying about
10 Ratings
4 Ratings
10 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8 out of 100
4 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 6.1 out of 100

Likelihood to Recommend

AWS OpsWorks

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.
Diego Gamez | TrustRadius Reviewer

Spinnaker

Spinnaker suits well for applications which are stateless and can adapt to an immutable architecture of deployment. But for applications which are stateful and cannot afford to spin up new servers for every deployment doesn't go well with Spinnaker. It can handle only deployments which are VM based and cannot support deployments to serverless architecture like AWS Lambda etc.
Anonymous | TrustRadius Reviewer

Pros

AWS OpsWorks

  • 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
Andrew Raines | TrustRadius Reviewer

Spinnaker

  • Spinnaker is very strong in its ability to baking of AMI(with ROSCO) and code deployments for Linux based ec2/AMI. Below are some more points:
  • Out of the box deployment strategies.
  • Open Source and active development.
  • Multi cloud deployments ( also can integrate with kubernetes)
  • Automated triggers.
  • Manual Judgements.
  • In-house bakery service, which helps in immutable deployments.
  • Easy pipeline setups using the UI , no need to write complex CFNs for code deployments.
  • "One click resize" of the underlying ec2s.
  • Exactly "one click rollback".
  • Pipelines can be scripted (SPEL)
  • Excellent search feature to search LBs , clusters etc from the UI.
  • Both high level and low level view of clusters, which has fine-grained options to control cloud infra from Spinnaker UI itself.
  • SSO and RBAC supported.
  • Wide range of deployment strategies like Blue-Green , Highlanders etc.
Debajit Kataki | TrustRadius Reviewer

Cons

AWS OpsWorks

  • 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.
Anonymous | TrustRadius Reviewer

Spinnaker

  • Spinnaker on its own has 10 underlying micro services. Managing Spinnaker needs a focussed platform approach
  • No support to deploy the artifacts without re-creating the servers. Only pure immutable deployment are allowed.
  • No authorization at pipelines level
Anonymous | TrustRadius Reviewer

Support Rating

AWS OpsWorks

AWS OpsWorks 6.0
Based on 1 answer
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.
Anonymous | TrustRadius Reviewer

Spinnaker

No score
No answers yet
No answers on this topic

Alternatives Considered

AWS OpsWorks

OpsWorks is an orchestration tool, basically you use it to specify the state you want your network to be in by specifying the state you want each resource (server instances, applications, storage) in which you want that resource to be. And specify the state in which you want each resource.The evaluated competitors have other benefits that in our case did not provide as many benefits as OpsWorks.
Diego Gamez | TrustRadius Reviewer

Spinnaker

We get a centralised view of all pipelines in single place. This helps for a large enterprise. Maven is very popular, so generating RPM from existing POM.xml is cool!
Debajit Kataki | TrustRadius Reviewer

Return on Investment

AWS OpsWorks

  • 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.
Andrew Raines | TrustRadius Reviewer

Spinnaker

  • As we are using it on a large scale, hosting and maintaining it is affordable.
  • For few of the BU where there are fewer applications in Cloud. Hosting it and maintaining is an overhead and not very cost effective.
Anonymous | TrustRadius Reviewer

Pricing Details

AWS OpsWorks

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Spinnaker

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Add comparison