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

are the env vars also present inside the container?

Yes - so it works fine if I comment out this part:

```const { accountId: awsAccountId } = await aws.getCallerIdentity({})```

I also have `PULUMI_ACCESS_TOKEN` set as env and that seems to work fine for logging into Pulumi - just aws credentials are having issues

Any known issues you’ve heard of that might be causing this?

```import * as pulumi from '@pulumi/pulumi'
import * as aws from '@pulumi/aws'
import * as awsx from '@pulumi/awsx'
import * as k8s from '@pulumi/kubernetes'```

```    "dependencies": {
        "@pulumi/aws": "^5.10.0",
        "@pulumi/awsx": "^0.40.0",
        "@pulumi/kubernetes": "^3.20.2",
        "@pulumi/pulumi": "^3.37.2",
    }```

We’re also facing this issue, but in our case it’s only happening after upgrading pulumi-aws from &gt;=4.0,&lt;5.0 to &gt;=5.0. We’re also using environment variables for aws creds.

would any of you by any chance be using IAM roles?

<@U03AX30HJSK> we have added permissions by group

Switching to using the ~/.aws/credentials file (instead of env vars) fixes the problem. This is with the exact same creds.