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

No, but aside: there is no need to use `apply` in these circumstances. Pulumi makes properties of outputs available in these cases.
```    vpcConfig: {
      subnetIds: lambdaVpcConfig.lambdaVpcPrivateSubnetIds,
      securityGroupIds: lambdaVpcConfig.lambdaSecurityGroupIds
    },```

Also note that your code has securityGroupIds set as an array of one object, which is an array of security group ID outputs. I'm guessing you wanted it to be an array of security group ID outputs, not an array of arrays of security group IDs?

I didn't know pulumi could access `output` properties without `apply`. Let me give it a try.
On another note, the `lambdaSecurityGroupIds` is actually just one id, I misspelled it and was too lazy to change it :disappointed: I guess i`ll do that now :smile: Gonna edit the example just in case someone else has a take on the problem

I managed to get it to run in the vpc. I don't know how, because I didn't really change the code. I just ran the pulumi up 3 times and the 3rd time it worked. Could it be some permissions related issue? :thinking_face:

No, but AWS doesn't always do everything immediately. Maybe this was already in progress in AWS, and simply took that long?