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 <https://www.pulumi.com/docs/reference/pkg/aws/ec2/getsubnet/|getSubnet> function includes the availabilityZone so you could use that. Put the 2 subnets into a collection and then use `.apply` to narrow it to the single desired subnet

actually even better: <https://www.pulumi.com/docs/reference/pkg/aws/ec2/getsubnetids/#using|this function> can be provided filters and takes in a VPC ID so you can provide an availability zone filter and receive only the desired Subnet ID in return

I am creating my VPC with `awsx.ec2.Vpc.fromExistingIds` , so hopefully this won’t pose a problem

hmmmm I think it depends, some of the crosswalk APIs expect to be passed an actual `Pulumi.Resource` instance. But if you're using APIs that accept just a Subnet ID than mixing the providers shouldn't be an issue

The cloudformation template that creates the VPC is tagging the subnets appropriately enough that I should be able to filter specifically how I need!  Thanks again.

I think an alternative (homegrown) version of awsx's VPC, with AZs as a collection of subnets, would be helpful..