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

I don't normally see `await` in pulumi examples. What you do see is `&lt;resource&gt;.apply()` that returns a `pulumi.Output&lt;T&gt;` that the pulumi SDK knows will _eventually_ be filled and everything that depends on the Output will wait for its fulfillment.

Basically, you need to build a long graph of dependent functions that will eventually be executed. Most of the pulumi SDK resources understand how to deal with a `pulumi.Output&lt;T&gt;`.

another option is to put anything you want to await in an async function and just call that function in `index.ts`

<https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-8.html#top-level-await|top-level awaits are also available in Typescript> if you have the right tsconfig, though i haven't tried this before with Pulumi

<https://pulumi-community.slack.com/archives/CRVK66N5U/p1614877794010800?thread_ts=1614875931.009700&amp;cid=CRVK66N5U> shows how to do this as well.

Most resources take pulumi.Input for their parameters, which is a union type that includes Promise. So you can pass a Promise directly in an argument.

If you need to pass a thing in a Promise, I think you can wrap the Promise in an Output (using the `pulumi.output` function) then Pulumi will lift properties out of the Output as you need them.

But.. doesn't `aws.iam.User.get()` return a _User_? Not a Promise...