# New module for Managed VPC NAT Gateway

**URL:** <https://forum.ansible.com/t/new-module-for-managed-vpc-nat-gateway/20101>\
**Category:** Ansible Developer\
**Tags:** aws\
**Created:** [December 30, 2015, 12:13pm UTC](https://forum.ansible.com/t/new-module-for-managed-vpc-nat-gateway/20101 "2015-12-30T12:13:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jon2](https://avatars.discourse-cdn.com/v4/letter/j/e47774/32.png) [@jon2](https://forum.ansible.com/u/jon2)\
**Post date:** [December 30, 2015, 12:13pm UTC](https://forum.ansible.com/t/new-module-for-managed-vpc-nat-gateway/20101/1 "2015-12-30T12:13:16Z")

</div>

Hi,

AWS launched a Managed NAT Gateway service on 17th December ([https://aws.amazon.com/blogs/aws/new-managed-nat-network-address-translation-gateway-for-aws/](https://aws.amazon.com/blogs/aws/new-managed-nat-network-address-translation-gateway-for-aws/)) which enables you to NAT from private subnets to an elastic IP without having to spin up your own EC2 NAT instances.  
I’ve submitted a PR ([https://github.com/ansible/ansible-modules-extras/pull/1438](https://github.com/ansible/ansible-modules-extras/pull/1438)) to enable Ansible to manage these in an idempotent way.

Would be great to get some feedback.

Note: it requires boto3 and botocore 1.3.14 or above (checked for in module) as it’s a recent addition from the boto project.

Thanks,

Jon