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

Closest I've gotten is typecasting an output as an input...

`const networking = new pulumi.StackReference(`other_stack`)`
`const vpcId: Input&lt;string&gt; = networking.requireOutputValue("vpcId") as Input&lt;string&gt;`
`const vpc = awsx.ec2.Vpc.fromExistingIds(`cluster-vpc`, {vpcId: vpcId})`

Have you tried just using `requireOuput` ? 

We do this in a similar pattern and don't have any issues with it 

<https://github.com/jaxxstorm/pulumi-examples/blob/6207179e2c4a6edbf60628edcc8a886c360f72ab/typescript/aws/eks-platform/vpc/index.ts#L12|https://github.com/jaxxstorm/pulumi-examples/blob/6207179e2c4a6edbf60628edcc8a886c360f72ab/typescript/aws/eks-platform/vpc/index.ts#L12>

<https://github.com/jaxxstorm/pulumi-examples/blob/6207179e2c4a6edbf60628edcc8a886c360f72ab/typescript/aws/eks-platform/eks/index.ts#L9|https://github.com/jaxxstorm/pulumi-examples/blob/6207179e2c4a6edbf60628edcc8a886c360f72ab/typescript/aws/eks-platform/eks/index.ts#L9>

Thanks for the tips. Just using `requireOutput` now is working for me though I swear I tried that previously. I think part of the problems I'm running into are related to Crosswalk vs Classic AWS. ECS Crosswalk for instance won't take just a vpcId for the vpc like some of the classic options and I couldn't get it to work by hydrating the vpc from non-crosswalk examples I saw either.