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

How do I refresh my AWS credentials? I was under the impression that that is exactly was `aws-vault` is doing, generating new temporary credentials for AWS. Do you mean something else?

`aws sts get-caller-identity` indicate my credentials are working just fine. If you mean something else, then you should explain what you mean.

again you can ask chatgpt. I'm not going to solve this for you.

It works with classic AWS credentials.

Pulumi, not getting Pulumi working with `aws-vault` v7.2.0 on Mac Sonoma 14.1.1. See above error.

Not the first time things not working with AWS temporary session credentials from `aws-vault`, can you guys please test with this? Modern infosec practices even Amazon's own recommendations prohibit AWS classic credentials.

It's not strictly that it isn't working with `aws-vault`, there's something much more fragile with how it's acquiring AWS credentials. It's very easy to break. Some debugging on your part is in order.

Is the Go pulumi package more reliable than the Node packages?

This is clearly erroneous. Rather than stop and throw here, determining the actual error is a good start:
```dial tcp: lookup sts.us-east-1.amazonaws.com on 192.168.0.1:53: no such host```

<@U05A56Q40SV> I was having a <https://pulumi-community.slack.com/archives/C84L4E3N1/p1700105337370559|weird issue very simliar to this> yesterday, but it's now resolved. Maybe it works for you now? At first I thought it was my internet connection but now I'm not so sure. Perhaps intermittent pulumi outage or some weird internet routing issue.

Like you said, it's not the first time I've had cases where Pulumi didn't work but raw aws cli works

`i/o timeout` -- different error, but yes, if AWS CLI works then exactly what does Pulumi (or Terraform) require that acts differently then the AWS CLI.

We just opened an issue on this, can you all chime in on what you’ve been seeing to help us track down what’s going on? <https://github.com/pulumi/pulumi-aws/issues/3023>

I have no solution to this problem. This is a show-stopper.

Occurs now with just classic AWS CLI credentials. Problem is persistent enough that it's no longer possible to use pulumi, and not persistent just enough to know that it's not a configuration error. For example, `preview` worked one time out of a dozen attempts, `up` and yet to work again.

My only reliable fix is to run `pulumi` in a docker image.

<@U05A56Q40SV> If you haven’t already, can you weigh in on the issue linked above and/or upvote it?