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

I think don't <http://awsx.lb|awsx.lb> has an equivalent to Vpc's _fromExistingIds_. You probably want to stick with the aws package's classes for this case.

In general, if you're comfortable with the way Pulumi works, there isn't a great reason to use the awsx packages. In my experience, it's pretty easy to create equivalent ComponentResources with additional domain-specific logic that suit your environment better, and you can expose the exact properties you need for logging, inter-op, etc.

They're great places to start, but you sacrifice just enough configurability to make it awkward to use once you get into interesting use cases

seconding the pain you get yourself into using awsx over aws package more than not.