# Provisioning a NAT via ec2\_vpc

**URL:** <https://forum.ansible.com/t/provisioning-a-nat-via-ec2-vpc/17190>\
**Category:** Ansible Project\
**Created:** [January 5, 2015, 9:30pm UTC](https://forum.ansible.com/t/provisioning-a-nat-via-ec2-vpc/17190 "2015-01-05T21:30:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gary\_Malouf](https://avatars.discourse-cdn.com/v4/letter/g/4bbf92/32.png) [@Gary\_Malouf](https://forum.ansible.com/u/Gary_Malouf)\
**Post date:** [January 5, 2015, 9:30pm UTC](https://forum.ansible.com/t/provisioning-a-nat-via-ec2-vpc/17190/1 "2015-01-05T21:30:37Z")

</div>

Is setting up a NAT supported (but undocumented) or do we need to manually launch instances(s) via the normal ec2 module to act as a NAT for private sub-domains?

---

<div class="post-metadata">

**Author:** ![vaida.dan](https://avatars.discourse-cdn.com/v4/letter/v/5daacb/32.png) [@vaida.dan](https://forum.ansible.com/u/vaida.dan)\
**Post date:** [January 10, 2015, 7:01pm UTC](https://forum.ansible.com/t/provisioning-a-nat-via-ec2-vpc/17190/2 "2015-01-10T19:01:28Z")

</div>

\*subnets. Yes, that’s right. the ec2\_vpc module doesn’t do NAT related things. you’ll have to launch another EC2 instance for that.  
take a look here: [https://github.com/dfederlein/ansible-aws/blob/master/vpc/ec2\_vpc.yml](https://github.com/dfederlein/ansible-aws/blob/master/vpc/ec2_vpc.yml)  
it requires having the aws cli tools set up on your local host.