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’ve just published my first package of Pulumi code ported over from some of the Terraform examples I’ve published in the past. This one is a VPC component. There is some overlap with `pulumi-aws-infra`, but this has a few differences:

- private/public address space is assigned in an assymetric fashion (as per “Practical VPC Design”), and subnets are automatically sized based on the available address space and number of AZs
- a `PerAZ` option can be used for subnet distribution across all AZs in a region. No slack space is left since a second CIDR block can now be added.
- VPC endpoints for S3 and DynamoDB can optionally be created
- Flow logging can optionally be enabled
- Tags can be applied to every resource
- A private hosted zone can optionally be created and assigned via a DHCP Options Set

It’s available here: <https://www.npmjs.com/package/@operator-error/pulumi-aws-vpc> (the org name is taken from our blog, <https://operator-error.com>), and on GitHub at: <https://github.com/jen20/pulumi-aws-vpc>. Any feedback is much appreciated!