Hey guys I m a bit frustrated with the `dial tcp lookup` err

Question

Hey guys I m a bit frustrated with the `dial tcp lookup` error as it does not seem to be indicative of the actual problem All my pulumi projects stopped working today with this error Worked earlier in the day FWIW I did do a `brew upgrade` ``` configuring Terraform AWS Provider validating provider credentials retrieving caller identity from STS operation error STS GetCallerIdentity https response error StatusCode 0 RequestID request send failed Post dial tcp lookup on 192 168 0 1 53 no such host``` How do I debug this and understand the actually problem This works fine ```aws vault exec env aws sts get caller identity``` This fails but had been working fine to date for months no changes other than updating outdated brew packages ```aws vault exec env no session pulumi up stack stack ```

stale-answer-34162 · Answer

refresh your amazon credentials

rapid-belgium-4304 · Answer

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

stale-answer-34162 · Answer

ask chatgpt

rapid-belgium-4304 · Answer

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

stale-answer-34162 · Answer

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

rapid-belgium-4304 · Answer

Your trolling is unhelpful

rapid-belgium-4304 · Answer

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

rapid-belgium-4304 · Answer

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

rapid-belgium-4304 · Answer

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

rapid-belgium-4304 · Answer

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```

gifted-gigabyte-53859 · Answer

< rapid belgium 4304> I was having a 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

gifted-gigabyte-53859 · Answer

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

rapid-belgium-4304 · Answer

`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

salmon-account-74572 · Answer

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>

rapid-belgium-4304 · Answer

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

rapid-belgium-4304 · Answer

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

rapid-belgium-4304 · Answer

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

salmon-account-74572 · Answer

< rapid belgium 4304> If you haven t already can you weigh in on the issue linked above and or upvote it