<h3>What is Ansible’s approach to security?<aclass="headerlink"href="#what-is-ansible-s-approach-to-security"title="Permalink to this headline">¶</a></h3>
<p>Ansible aims to not develop custom daemon code but rely heavily on OpenSSH, which is extremely well
peer reviewed and the most widely used security subsystem in the industry. As a result, Ansible
has a lower attack surface than any configuration management tool featuring daemons that run
as root, and you do not have to worry about network security vulnerabilities in the tool itself.</p>
<p>If your central server is taken over (or even logged into by a malicious employee),
provided you were using SSH-agent and encrypted keys (and/or sudo with a password),
your keys are still locked and no one can take control of your nodes.</p>
<p>Compared with something like Chef/Puppet/other, compromised manifests would lead
to a loss of the whole network, with your network turning into an easily controllable
botnet. Further by not running daemon infrastructure, you have more
free RAM and compute resources, which should be relevant to users wanting to maximize their
computing investments.</p>
</div>
<divclass="section"id="how-does-ansible-scale">
<h3>How does Ansible scale?<aclass="headerlink"href="#how-does-ansible-scale"title="Permalink to this headline">¶</a></h3>
<p>Whether in single-execution mode or using ansible playbooks, ansible can
@ -335,7 +351,7 @@ tasks – whether for a QA sytem, build system, or anything you can think of
<pclass="pull-right"><ahref="#">Back to top</a></p>
@ -182,13 +182,17 @@ version of software if required.</p>
<p>Other deployment oriented frameworks similarly cover deployment well but lack a strongly defined resource model and devolve into glorified remote scripts. Ansible playbooks – having been designed with this problem in mind – are good at both deployment & idempotent configuration, meaning you don’t have to spread your infrastructure management out between different tools (Puppet+Capistrano, Chef+Fabric, etc), and performing ordered steps between different classes of machines is no problem, yet our modules affect system state only when required – while avoiding the problem of fragile scripting that assumes certain starting
or ending states.</p>
<p>Ansible is also unique in other ways. Extending ansible does not require programming in any particular language – you can write <aclass="reference internal"href="modules.html"><em>Ansible Modules</em></a> as idempotent scripts or programs that return simple JSON. Ansible is also pragmatic, so when you need to, it’s also trivially easy to just execute useful shell commands.</p>
<p>Why use Ansible versus something else? (Puppet, Chef, Capistrano, etc?) Ansible will have far
<p>Why use Ansible versus other configurationmanagement tools? (Puppet, Chef, etc?) Ansible will have far
less code, it will be (by extension) more correct, and it will be the
easiest thing to hack on and use you’ll ever see – regardless of your
favorite language of choice.</p>
<p>Systems management doesn’t have to be complicated. Ansible’s docs
will remain short & simple, and the source will be blindingly obvious.</p>
<p>We’ve learned well from “Infrastructure is Code”. Infrastructure should be easy and powerful to command, but it should not look like code, lest it acquire the disadvantages of a software project – bugs, complexity, and overhead. Infrastructure configurations should be simple, easy to develop, and easy to audit.</p>
favorite language of choice. Versus other deployment tools? (Capistrano, Fabric?). Ansible playbooks are easier
to use (not being code) and also allows intermixing of idempotent configuration management rules for a higher level
of control. Further, it was designed for deploying multi-node applications from the beginning.</p>
<p>Compared with most configuration managememnt tools, Ansible is also more secure. While most configuration management tools use a daemon, running as root with full access to the system, with it’s own in-house developed PKI infrastructure, Ansible just uses SSH (and supports sudo as neccesssary). There is no additional attack surface and OpenSSH is one of the most peer reviewed security components out there.
If a central server containing your playbooks are comprimised, your nodes are not – which is NOT the case
of these other tools, which can, more or less, turn into a botnet. Our security approach is to avoid writing custom
crypto code altogether, and rely on the most secure part of the Linux/Unix subsystem that your machines are already using.</p>
<p>Systems management doesn’t have to be complicated. Ansible’s docs will remain short & simple, and the source will be blindingly obvious. We’ve learned well from “Infrastructure is Code”. Infrastructure should be easy and powerful to command, but it should not look like code, lest it acquire the disadvantages of a software project – bugs, complexity, and overhead. Infrastructure configurations should be simple, easy to develop, and easy to audit.</p>
<divclass="section"id="architecture">
<h2>Architecture<aclass="headerlink"href="#architecture"title="Permalink to this headline">¶</a></h2>
<liclass="toctree-l3"><aclass="reference internal"href="faq.html#what-is-ansible-s-approach-to-security">What is Ansible’s approach to security?</a></li>
<liclass="toctree-l3"><aclass="reference internal"href="faq.html#how-does-ansible-scale">How does Ansible scale?</a></li>
<liclass="toctree-l3"><aclass="reference internal"href="faq.html#are-transports-other-than-ssh-supported">Are transports other than SSH supported?</a></li>
<liclass="toctree-l3"><aclass="reference internal"href="faq.html#what-are-some-ideal-uses-for-ansible">What are some ideal uses for Ansible?</a></li>
@ -376,7 +381,7 @@ Puppet Labs, and rPath. Reach Michael by email <a class="reference external" hr
<pclass="pull-right"><ahref="#">Back to top</a></p>
Michael DeHaan
13 years ago