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

You can do this with config at the moment. <@UB3BGTV63> might know other, better ways to do this, however if you configure the `externalVpcId` and related variables, the `cloud.Service` will join an existing VPC.

See <https://pulumi.io/quickstart/cloudfx/index.html#configuration>.

TL;DR, `pulumi config set cloud-aws:externalVpcId &lt;my-vpc-id&gt;`

I'd like to create the VPC in code though. 

Ah, got it. Let me take a look. IIRC there is a way to do this.

<@UB9JVTW07> Do you know the answer here? How do I create my own `awsinfra.Network`, and plug it into the AWS cloud package so that it uses it rather than creating a new one?

i can't see any way to do it currently :slightly_smiling_face:

Yes - currently you probably will need to stand up the network in a separate stack and use config vars mentioned above. We definitely want to support simpler composition of the cloud library with networks/clusters/etc - along the lines of how we now support “first class providers”.

Ah drats, that confirms my reading of the code too. Can we file an issue? I would love to see these things compose, as I'm sure <@UCZ0LS7NZ> would too :slightly_smiling_face:

It would be nice if that composition was done via an interface defined by `cloud` rather than direct use of the `awsinfra` one, in order that other network designs can meet it

Opened <https://github.com/pulumi/pulumi-cloud/issues/601>. 

<@UB8A66MPS> good point - that would fall out pretty naturally from a straightforward approach to what’s described in the issue above - but perhaps worth calling out explicitly in that issue as well. 