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?
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.