# jinja2 support for cloudformation module

**URL:** <https://forum.ansible.com/t/jinja2-support-for-cloudformation-module/17397>\
**Category:** Ansible Developer\
**Created:** [January 29, 2015, 1:46pm UTC](https://forum.ansible.com/t/jinja2-support-for-cloudformation-module/17397 "2015-01-29T13:46:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kuLa](https://avatars.discourse-cdn.com/v4/letter/k/b487fb/32.png) [@kuLa](https://forum.ansible.com/u/kuLa)\
**Post date:** [January 29, 2015, 1:46pm UTC](https://forum.ansible.com/t/jinja2-support-for-cloudformation-module/17397/1 "2015-01-29T13:46:48Z")

</div>

Hi all,

I’ve been doing deep integration for pure cloudformation stack with ansible and thought that it’ll be nice to have jinja support for it.

Am I the first one which see benefits in having ex for loops in security groups to create ingress rules for list of IPs?

If anybody would be interested here ([https://github.com/vorlock/ansible-modules-core](https://github.com/vorlock/ansible-modules-core)) is what I did.

I think it’ll be a nice addition to have j2 support to make this crapy cfn stacks more DRY

---

<div class="post-metadata">

**Author:** ![Evgeniy\_Litvinenko](https://avatars.discourse-cdn.com/v4/letter/e/838e76/32.png) [@Evgeniy\_Litvinenko](https://forum.ansible.com/u/Evgeniy_Litvinenko)\
**Post date:** [July 7, 2015, 12:47pm UTC](https://forum.ansible.com/t/jinja2-support-for-cloudformation-module/17397/2 "2015-07-07T12:47:09Z")

</div>

Hi,

Got into the similar situation and it would be great to have such feature with jinja support, I noticed that this pull request is closed, could it be reopened ?

---

<div class="post-metadata">

**Author:** ![Michael\_Weinrich](https://avatars.discourse-cdn.com/v4/letter/m/b19c9b/32.png) [@Michael\_Weinrich](https://forum.ansible.com/u/Michael_Weinrich)\
**Post date:** [July 7, 2015, 10:29pm UTC](https://forum.ansible.com/t/jinja2-support-for-cloudformation-module/17397/3 "2015-07-07T22:29:17Z")

</div>

Hi,

I went for a different approach and the PR ([https://github.com/ansible/ansible-modules-core/pull/1562](https://github.com/ansible/ansible-modules-core/pull/1562)) was already merged. Using it you can use the template lookup to achieve what was discussed here. HTH