# ansible bootstrap/kickstart/export/offline/installer mode

**URL:** <https://forum.ansible.com/t/ansible-bootstrap-kickstart-export-offline-installer-mode/26710>\
**Category:** Ansible Developer\
**Tags:** windows, aws\
**Created:** [February 12, 2018, 7:21pm UTC](https://forum.ansible.com/t/ansible-bootstrap-kickstart-export-offline-installer-mode/26710 "2018-02-12T19:21:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Roman\_Belyakovsky](https://avatars.discourse-cdn.com/v4/letter/r/ecae2f/32.png) [@Roman\_Belyakovsky](https://forum.ansible.com/u/Roman_Belyakovsky)\
**Post date:** [February 12, 2018, 7:21pm UTC](https://forum.ansible.com/t/ansible-bootstrap-kickstart-export-offline-installer-mode/26710/1 "2018-02-12T19:21:49Z")

</div>

Ansible became a very convenient tool for different systems setup. However it still requires `ansible`to run playbooks and that’s sometimes a series limitation.

One of the examples is AWS ASG – you can install ansible on a local nix host and run playbook locally but that’s too complicated. And there’s no way to handle this on windows.

I suggest creating an `export` option that would produce a single python/powershell script that could be used without ansible. It’s clear some modules and approaches won’t work or will be limited in this mode (like delegate\_to) but that’s much better than nothing.

---

<div class="post-metadata">

**Author:** ![Matthew\_L\_Daniel](https://avatars.discourse-cdn.com/v4/letter/m/b487fb/32.png) [@Matthew\_L\_Daniel](https://forum.ansible.com/u/Matthew_L_Daniel)\
**Post date:** [March 25, 2018, 3:57am UTC](https://forum.ansible.com/t/ansible-bootstrap-kickstart-export-offline-installer-mode/26710/2 "2018-03-25T03:57:31Z")

</div>

As a counter-solution to that approach, the [kubespray project](https://github.com/kubernetes-incubator/kubespray/blob/v2.4.0/roles/bootstrap-os/tasks/bootstrap-coreos.yml) demonstrated that with just a little bit of scripting and the raw: module, one can relatively quickly provision ansible onto the target machines, then switch execution over to it as one would normally. We do that very trick using the user-data in EC2 launch situations, bootstrapping CoreOS on PyPy (although we use [portable-pypy](https://github.com/squeaky-pl/portable-pypy#portable-pypy-distribution-for-linux) because it whines less about the shared libraries when running). I would fully expect ASG would work fine, also.