I am very new to Pulumi , just trying to understand its capability in the AWS and while trying to test ECS Farget sample tutorial, getting the following error pulumiproviders:aws (default_5_42_0): error: rpc error: code = Unknown desc = unable to validate AWS credentials. Details: validating provider credentials: retrieving caller identity from STS: operation error STS: GetCallerIdentity, https response error StatusCode: 0, RequestID: , request send failed, Post “https://sts.us-east-1.amazonaws.com/”: dial tcp: lookup sts.us-east-1.amazonaws.com: i/o timeout Make sure you have set your AWS region, e.g.

pulumi config set aws:region us-west-2

. Amazon Web Services, Inc. Access Management- AWS Identity and Access Management (IAM) - AWS Access management for AWS services and resources. Manage fine-grained permissions and analyze access to refine permissions.Where as I have AWS credentials is configured but still getting the same error message for Java Where as I have AWS credentials is configured but still getting the same error message for Java Thank you all for your help in advance.

Where as I have AWS credentials is configured but still getting the same error message for Java

Not sure how you've configured AWS CLI on your machine but can you run

aws sts get-caller-identity

without passing

--profile

and get a successful response? Also have you already followed the setup instructions for the AWS provider to help Pulumi use your AWS credentials?

Hi, Thanks for your response, yes I am getting caller identity, but seems the post operation is failing, please see details below: 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 “https://sts.us-east-1.amazonaws.com/”: dial tcp: lookup sts.us-east-1.amazonaws.com: i/o timeout

I missed something in your original message.

error: rpc error: code = Unknown desc = unable to validate AWS credentials.

dial tcp: lookup sts.us-east-1.amazonaws.com: i/o timeout

I don't know what is causing the HTTP request to timeout but that's the source of your problem. I don't know why the provider would have trouble hitting the STS endpoint but then AWS CLI would work. Are you using any sort of a VPN or a corporate proxy? It's hard to say diagnose this via Slack without knowing anything about your environment. Since the issue is really with the provider trying to "validate" the AWS credentials, you can temporarily turn of credential validation with `pulumi config set

aws:skipCredentialsValidation

to

true

or set the env var

AWS_SKIP_CREDENTIALS_VALIDATION

to

true

. However, I don't know if you'll encounter other issues when the AWS provider tries to talk to AWS.