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

Don't use `getInstance`, that looks up instances using the AWS SDK and returns the current state. You could try using `aws.ec2.Instance.get()`. It uses Pulumi's outputs to wait for values to be available. I haven't tried it in this use case though...

I thought you could not use get in a pulumi run

You can always use &lt;client&gt;.get. You cannot use &lt;output&gt;.get().

Alternatively: `aws.ec2.Instance.get()`: :+1: . `aws.ec2.Instance.get().id.get()`: :thumbsdown:

The tricky thing here is that the instances will not be available until you deploy something in Beanstalk. So I don’t really want to wait in the pulumi run

```    if (environment.instances[0].length &gt; 0) {
        instance = await aws.ec2.getInstance({
            instanceId: environment.instances[0]
        })
        exports["instance"] = instance.privateDns
    }```

`instances`  just ends up being empty. I guess this situation is a special case

That's probably the right thing to do. If you use `Instance.get()`, it goes into your stack as a read-only resource. And if the id changes, it might count as an update, and mess up your CI comments, etc.