No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

You can pass in an empty array for the various subnets, then do it the normal way.

However: if you're not taking advantage of the subnets and NAT gateway, then consider not using awsx. It is only there to take away that sort of "undifferentiated heavy lifting": if your heavy lifting is differentiated, then it may be worth doing it yourself.

Yes, I think I will skip awsx and use regular aws resource instead to be able to better manage the configuration

If you've got the inclination at the same time, I've been told that running your own NAT gateway using a right-sized EC2 instance is a good way to save money. Once you move to aws.ec2, this becomes an option (if you have the dev time available).

Sounds like a good option, we have started a migration to shared VPCs and transition GW to reduce to only 2 NAT instances