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

The `awsx.ec2.Vpc` component can take care of creating all the various configurations of VPCs   - that might be worth checking out. 

Also found this guy: <https://github.com/pulumi/pulumi-awsx/blob/master/nodejs/awsx/network.ts>

Which would be better to use? Or better supported?

The `Vpc` component actually subsumes the older `Network`. The latter is noted at deprecated at <https://github.com/pulumi/pulumi-awsx/blob/master/README.md>. 

Is there an example somewhere of a VPC with multiple pub/priv subnets over multiple AZs using the `awsx.ec2.Vpc` module?

Nevermind! The Vpc module is pretty intuitive.  Very nice abstraction level you folks have going there :slightly_smiling_face:

Just on initial entry into the module i was confused as to why it was put under `ec2` other than that, awesome stuff.

Yes - this namespacing is due to the (largely historical) association of the underlying networking resources in AWS into the ec2 namespace. But agreed that as you move to higher level abstractions this becomes less obvious. Something to consider for future updates to namespace structure here. 