AWS Cloudformation templates: using ansible

Cross Product Knowledge

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

The content on this page relates to platforms which are not supported by Atlassian. Consequently, Atlassian cannot guarantee providing any support for it. Please be aware that this material is provided for your information only and using it is done so at your own risk.

Why ansible

We use ansible internally to do some post-installation configuration on our AWS Cloudformation instances. While the use of configuration management tools like ansible is not supported by Atlassian, we wanted to make the injection point for ansible available as a reference, for customers to use or extend for other tools, eg Puppet or Chef.

Sample repo

There is a functional example repo provided at

This sample contains a very basic implementation which will create a r53 A record with all the IP's of the application nodes created by the stack. This lets you programmatically query the nodes in your stack like so :- 

user@host:~/$ nslookup

Non-authoritative answer:

How to enable it

When deploying any of the product Cloudformation templates from there are two relevant fields to leverage the ansible exit point.

  1. You should fork the atlassian-local-ansible-exmaple repo and modify it to suit your needs
  2. If your forked repo requires credentials to access, upload a ssh public key that can pull from your repo to AWS Systems Manager parameter store as a "secure string"
  3. in the two Git template fields, provide the repo and paramater name
  4. As your stack instantiates it will attempt to bootstrap the local-ansible repo you have referenced in the template

Last modified on Sep 4, 2018

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.