This message was deleted.

sparse-intern-71089

06/11/2021, 2:27 PM

This message was deleted.

bored-oyster-3147

06/11/2021, 2:48 PM

The 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

bored-oyster-3147

06/11/2021, 2:50 PM

actually even better: 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

millions-furniture-75402

06/11/2021, 2:55 PM

Thanks, I’ll look into these!

millions-furniture-75402

06/11/2021, 2:56 PM

I am creating my VPC with

awsx.ec2.Vpc.fromExistingIds

, so hopefully this won’t pose a problem

bored-oyster-3147

06/11/2021, 2:58 PM

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

millions-furniture-75402

06/11/2021, 2:59 PM

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.

🙌 1

little-cartoon-10569

06/13/2021, 9:03 PM

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

Open in Slack

Previous Next

Pulumi Community

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.