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

hey folks, a colleague us running `pulumi up` for the first time. They've logged in the CLI, set a stack (an existing one I've deployed to before) and they also put our machine user IAM deployer keys in `~/.aws/credentials`.

they're getting <https://github.com/pulumi/pulumi/issues/6333|this>, though
```Previewing update (dev)

View Live: <https://app.pulumi.com/xxxxxxxx/infra/dev/previews/xxxxxxxx>

     Type                 Name                                    Plan     Info
     pulumi:pulumi:Stack  infra-dev                                        1 message
     └─ aws:s3:Bucket     backend-beanstalk-deployment-resources           1 error
 
Diagnostics:
  aws:s3:Bucket (backend-beanstalk-deployment-resources):
    error: 1 error occurred:
    	* error configuring Terraform AWS Provider: AWS account ID not previously found and failed retrieving via all available methods. See <https://www.terraform.io/docs/providers/aws/index.html#skip_requesting_account_id> for workaround and implications. Errors: 2 errors occurred:
    	* error calling sts:GetCallerIdentity: InvalidClientTokenId: The security token included in the request is invalid.
    	status code: 403, request id: d0d5ebc9-9f8b-469c-a658-45ef57228ec7
    	* failed getting account information via iam:ListRoles: InvalidClientTokenId: The security token included in the request is invalid.
    	status code: 403, request id: fc2e220e-14aa-4a4d-a37d-5232732b0335
 
  pulumi:pulumi:Stack (infra-dev):
    E0511 15:30:13.239102816  414553 <http://fork_posix.cc:70]|fork_posix.cc:70]>           Fork support is only compatible with the epoll1 and poll polling strategies```

trying this:
&gt;  ok, delete ~/.aws and just run `aws configure` again
&gt; and paste those values manually when prompted


found the issue:  he had some other AWS env vars set. Unsetting those resolved the issue.

I normally use exported environment variables with `direnv` or in combination with `awsume` or a very good solution is to use `aws-vault`

<@U036KV0KSDS> ask them to check for the presence if any environment variables 

<@UCWG26BH7> yup, thanks - that was the issue :slightly_smiling_face: