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

This is telling you your DNS lookups are failing. It’s a local error. Are you running from an ec2 instance?

Okay, we’ll you’re querying an ipv6 dns server and it’s failing. It’s likely not a Pulumi specific problem 

is there something I could do it to debug it?

Do a dns lookup for the sts address in the error 

```Server:		fe80::96ea:eaff:fe2b:ec16%11
Address:	fe80::96ea:eaff:fe2b:ec16%11#53

Non-authoritative answer:
Name:	<http://sts.us-east-2.amazonaws.com|sts.us-east-2.amazonaws.com>
Address: 52.95.18.19```

does it mean something? (I'm lost here :melting_face: )

well, it seems nothing is blocking the DNS lookup

it’s honestly hard to say, there’s a lot of potential issues, but I will say it’s a local configuration issue. You need to:

• make sure you have valid AWS credentials both in your provider config and in your env vars
• make sure you can make AWS API calls via the AWS CLI and AWS Go SDK


in my company we use temporaries AWS credentials, so we normally setup with envs.
is it necessary to have those credentials in the provider config?

I have no Go experience. May I test the JS SDK?

The library which stores your state in an s3 bucket uses the Go SDK 

the `pulumi init stack`  command works and creates the state file

Go it's pretty easy to setup.
I manage to put together an example to list my S3 buckets and it's working as expected:

do you have any other tip to help me?
I've tried everything I found on the internet, but it's still not working

```name: remix-poc
description: Remix app infrastructure
runtime: nodejs```

I've tried the `skipCredentialsValidation`  config, which makes the stack to start executing, at least. But one of my resources uses the `aws.getCallerIdentity()` , causing the error anyway

today a friend of mine ran the code in his environment and it worked.
definitely it's something in my local configuration, but I don't even know where to lookup to

<@UCWG26BH7> thanks for the tips. I did not solve yet, but I found that connected in other network the error does not occur.

it's probably something in my router.
I have no idea how to solve it