Error when creating VPC without any private subnets and has NAT gateways about terraform-aws-vpc HOT 5 OPEN

From my understanding you have to define private subnets in the egress vpc cf here ...

from terraform-aws-vpc.

@laserpedro not quite....the egress VPC can live in another account and has just public subnets with NAT gateways living in them. You can then use a Transit Gateway to link those subnets with private subnets in separate VPCs that live in separate accounts. By creating a VPC with just public subnets for the egress VPC, you can keep the IP space small (which is desirable because this will be an internet-facing VPC after all).

from terraform-aws-vpc.

What about using non routable IPs for the private subnets in your egress VPC ?

from terraform-aws-vpc.

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

from terraform-aws-vpc.

I really think this is a valid use case and it's something I already witnessed on a past project. Also, AWS documents this pattern on some architectures, like here. I also made some local changes to the module so that the reproduction code (shared by @aiell0) works as expected. Can I open a PR for this? :)

from terraform-aws-vpc.