AWS OpsWorks vs Chef vs Puppet Labs

Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

AWS OpsWorks
AWS OpsWorks

165
84
+ 1
42
Chef
Chef

973
645
+ 1
327
Puppet Labs
Puppet Labs

596
409
+ 1
218
No Stats
- No public GitHub repository available -

What is AWS OpsWorks?

Start from templates for common technologies like Ruby, Node.JS, PHP, and Java, or build your own using Chef recipes to install software packages and perform any task that you can script. AWS OpsWorks can scale your application using automatic load-based or time-based scaling and maintain the health of your application by detecting failed instances and replacing them. You have full control of deployments and automation of each component 

What is Chef?

Chef enables you to manage and scale cloud infrastructure with no downtime or interruptions. Freely move applications and configurations from one cloud to another. Chef is integrated with all major cloud providers including Amazon EC2, VMWare, IBM Smartcloud, Rackspace, OpenStack, Windows Azure, HP Cloud, Google Compute Engine, Joyent Cloud and others.

What is Puppet Labs?

Puppet is an automated administrative engine for your Linux, Unix, and Windows systems and performs administrative tasks (such as adding users, installing packages, and updating server configurations) based on a centralized specification.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose AWS OpsWorks?
Why do developers choose Chef?
Why do developers choose Puppet Labs?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
      Be the first to leave a con
      What companies use AWS OpsWorks?
      What companies use Chef?
      What companies use Puppet Labs?

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with AWS OpsWorks?
      What tools integrate with Chef?
      What tools integrate with Puppet Labs?

      Sign up to get full access to all the tool integrationsMake informed product decisions

      What are some alternatives to AWS OpsWorks, Chef, and Puppet Labs?
      AWS Elastic Beanstalk
      Once you upload your application, Elastic Beanstalk automatically handles the deployment details of capacity provisioning, load balancing, auto-scaling, and application health monitoring.
      AWS Config
      AWS Config is a fully managed service that provides you with an AWS resource inventory, configuration history, and configuration change notifications to enable security and governance. With AWS Config you can discover existing AWS resources, export a complete inventory of your AWS resources with all configuration details, and determine how a resource was configured at any point in time. These capabilities enable compliance auditing, security analysis, resource change tracking, and troubleshooting.
      AWS CloudFormation
      You can use AWS CloudFormation’s sample templates or create your own templates to describe the AWS resources, and any associated dependencies or runtime parameters, required to run your application. You don’t need to figure out the order in which AWS services need to be provisioned or the subtleties of how to make those dependencies work.
      AWS CodeDeploy
      AWS CodeDeploy is a service that automates code deployments to Amazon EC2 instances. AWS CodeDeploy makes it easier for you to rapidly release new features, helps you avoid downtime during deployment, and handles the complexity of updating your applications.
      Ansible
      Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use.
      See all alternatives
      Decisions about AWS OpsWorks, Chef, and Puppet Labs
      StackShare Editors
      StackShare Editors
      Salt
      Salt
      Puppet Labs
      Puppet Labs
      Ansible
      Ansible

      By 2014, the DevOps team at Lyft decided to port their infrastructure code from Puppet to Salt. At that point, the Puppet code based included around "10,000 lines of spaghetti-code,” which was unfamiliar and challenging to the relatively new members of the DevOps team.

      “The DevOps team felt that the Puppet infrastructure was too difficult to pick up quickly and would be impossible to introduce to [their] developers as the tool they’d use to manage their own services.”

      To determine a path forward, the team assessed both Ansible and Salt, exploring four key areas: simplicity/ease of use, maturity, performance, and community.

      They found that “Salt’s execution and state module support is more mature than Ansible’s, overall,” and that “Salt was faster than Ansible for state/playbook runs.” And while both have high levels of community support, Salt exceeded expectations in terms of friendless and responsiveness to opened issues.

      See more
      Marcel Kornegoor
      Marcel Kornegoor
      CTO at AT Computing · | 5 upvotes · 129.1K views
      atAT ComputingAT Computing
      Linux
      Linux
      Ubuntu
      Ubuntu
      CentOS
      CentOS
      Debian
      Debian