Ansible vs AWS OpsWorks vs Chef

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

Ansible

12.7K
10K
+ 1
1.3K
AWS OpsWorks

205
185
+ 1
51
Chef

1.1K
926
+ 1
343
Advice on Ansible, AWS OpsWorks, and Chef
Needs advice
on
Puppet Labs
Chef
and
Ansible

I'm just getting started using Vagrant to help automate setting up local VMs to set up a Kubernetes cluster (development and experimentation only). (Yes, I do know about minikube)

I'm looking for a tool to help install software packages, setup users, etc..., on these VMs. I'm also fairly new to Ansible, Chef, and Puppet. What's a good one to start with to learn? I might decide to try all 3 at some point for my own curiosity.

The most important factors for me are simplicity, ease of use, shortest learning curve.

See more
Replies (2)
Recommends
Ansible

I have been working with Puppet and Ansible. The reason why I prefer ansible is the distribution of it. Ansible is more lightweight and therefore more popular. This leads to situations, where you can get fully packaged applications for ansible (e.g. confluent) supported by the vendor, but only incomplete packages for Puppet.

The only advantage I would see with Puppet if someone wants to use Foreman. This is still better supported with Puppet.

See more
Gabriel Pa
Recommends
Kubernetes
at

If you are just starting out, might as well learn Kubernetes There's a lot of tools that come with Kube that make it easier to use and most importantly: you become cloud-agnostic. We use Ansible because it's a lot simpler than Chef or Puppet and if you use Docker Compose for your deployments you can re-use them with Kubernetes later when you migrate

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Ansible
Pros of AWS OpsWorks
Pros of Chef
  • 274
    Agentless
  • 204
    Great configuration
  • 191
    Simple
  • 172
    Powerful
  • 149
    Easy to learn
  • 66
    Flexible
  • 54
    Doesn't get in the way of getting s--- done
  • 33
    Makes sense
  • 29
    Super efficient and flexible
  • 27
    Powerful
  • 11
    Dynamic Inventory
  • 8
    Backed by Red Hat
  • 7
    Works with AWS
  • 6
    Cloud Oriented
  • 6
    Easy to maintain
  • 4
    Because SSH
  • 4
    Multi language
  • 4
    Easy
  • 4
    Simple
  • 4
    Procedural or declarative, or both
  • 4
    Simple and powerful
  • 3
    Vagrant provisioner
  • 3
    Consistency
  • 2
    Debugging is simple
  • 2
    Well-documented
  • 2
    Merge hash to get final configuration similar to hiera
  • 2
    Fast as hell
  • 2
    Masterless
  • 1
    Work on windows, but difficult to manage
  • 32
    Devops
  • 19
    Cloud management
  • 108
    Dynamic and idempotent server configuration
  • 76
    Reusable components
  • 47
    Integration testing with Vagrant
  • 43
    Repeatable
  • 30
    Mock testing with Chefspec
  • 14
    Ruby
  • 8
    Can package cookbooks to guarantee repeatability
  • 7
    Works with AWS
  • 3
    Matured product with good community support
  • 3
    Has marketplace where you get readymade cookbooks
  • 2
    Less declarative more procedural
  • 2
    Open source configuration mgmt made easy(ish)

Sign up to add or upvote prosMake informed product decisions

Cons of Ansible
Cons of AWS OpsWorks
Cons of Chef
  • 5
    Hard to install
  • 4
    Dangerous
  • 3
    Bloated
  • 3
    Backward compatibility
  • 2
    Doesn't Run on Windows
  • 2
    No immutable infrastructure
    Be the first to leave a con
      Be the first to leave a con

      Sign up to add or upvote consMake informed product decisions

      - No public GitHub repository available -

      What is 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.

      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.

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

      What companies use Ansible?
      What companies use AWS OpsWorks?
      What companies use Chef?

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

      What tools integrate with Ansible?
      What tools integrate with AWS OpsWorks?
      What tools integrate with Chef?

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

      Blog Posts

      +14
      11
      1956
      +22
      17
      13181
      +30
      25
      14674
      +33
      20
      1597
      +23
      12
      6316
      What are some alternatives to Ansible, AWS OpsWorks, and Chef?
      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.
      Salt
      Salt is a new approach to infrastructure management. Easy enough to get running in minutes, scalable enough to manage tens of thousands of servers, and fast enough to communicate with them in seconds. Salt delivers a dynamic communication bus for infrastructures that can be used for orchestration, remote execution, configuration management and much more.
      Terraform
      With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.
      Jenkins
      In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
      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.
      See all alternatives
      How developers use Ansible, AWS OpsWorks, and Chef
      Cloudcraft uses
      Ansible

      Ansible is the deployment tool for people who don't like deployment tools. It's close to scripting, doesn't pollute your servers with agents or centralized servers, and just makes immediate sense. The entire stack at Cloudcraft.co is orchestrated by Ansible. What does that mean? Beyond the obvious of installing packages and configuring services, Ansible coordinates all the machines into a working deployment: It adds API servers to the loadbancer pool, opens ports on the DB server for the backend servers to connect, gracefully upgrades services in a rolling fashion for zero-downtime deployments etc. And it's so easy to use, it's easier to use than doing things by hand, meaning it's a deployment tool you'll actually use every time!

      Scrayos UG (haftungsbeschränkt) uses
      Ansible

      We use Ansible to synchronize the few configuration-options we've taken on our CoreOS-Machines. This makes deployment even easier and the fact that it's Agentless made the decision even easier.

      Bob P uses
      Ansible

      Ansible is used in both the development and production deployment process. A playbook couple with a Vagrantfile, easy deploys a local virtual machine that will mirror the setup in production.

      sapslaj uses
      Ansible

      I use Ansible to manage the configuration between all of the different pieces of equipment, and because it's agentless I can even manage things like networking devices all from one repo.

      BĂąi Thanh uses
      Ansible
      • Configuration management:
        • deploy/install all web/app environments
        • simple with Galaxy and playbooks.
      • No need any pre-installed agent on remote servers.
      Goyoboard uses
      Chef

      Out custom recipes makes it simple for developers bootstrap process (using vagrant) and that same recipe is also the one that is used to prep instances

      Zinc uses
      Chef

      We use Chef for our configuration management and our service discovery.

      EverTrue uses
      Chef

      Configuration management for any services not provided by AWS.

      Hund uses
      Chef

      Distributed application deployments and server configuration.

      James Salas uses
      Chef

      Configuration and deployment of application

      thanawatsenawat uses
      AWS OpsWorks

      Automate deploy application without SMTP.

      Hund uses
      AWS OpsWorks

      Chef server deployments.