# ec2\_vpc versus ec2\_vpc\_net et al

**URL:** <https://forum.ansible.com/t/ec2-vpc-versus-ec2-vpc-net-et-al/20464>\
**Category:** Ansible Project\
**Created:** [February 5, 2016, 2:56pm UTC](https://forum.ansible.com/t/ec2-vpc-versus-ec2-vpc-net-et-al/20464 "2016-02-05T14:56:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jeff\_Hardy](https://avatars.discourse-cdn.com/v4/letter/j/ecae2f/32.png) [@Jeff\_Hardy](https://forum.ansible.com/u/Jeff_Hardy)\
**Post date:** [February 5, 2016, 2:56pm UTC](https://forum.ansible.com/t/ec2-vpc-versus-ec2-vpc-net-et-al/20464/1 "2016-02-05T14:56:43Z")

</div>

I have been working up some playbooks and roles using the various vpc modules. With ec2\_vpc, it is possible to lay out vpc, subnets, and routes pretty much all-in-one, while doing the same with the newer (as of 2.0) ec2\_vpc\_net module requires chaining things such as vpc\_id to the ec2\_vpc\_subnet, igw, and route modules. I can see that separating the functionality allows for more flexibility. Will the original ec2\_vpc continue to be developed, or should all effort go into working with the latter modules?

---

<div class="post-metadata">

**Author:** ![viper233](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/viper233/32/2060_2.png) [@viper233](https://forum.ansible.com/u/viper233)\
**Post date:** [February 5, 2016, 6:14pm UTC](https://forum.ansible.com/t/ec2-vpc-versus-ec2-vpc-net-et-al/20464/2 "2016-02-05T18:14:23Z")

</div>

I think moving forward the ec2\_vpc\_net and other broken out modules are what will be the future of AWS resource provisioning. The older module coupled things too tightly together and didn’t integrate as well, weren’t as logical if those resources already existed or were already created via other means.

I’m no authority on these modules though and would appreciate others comments.