https://pulumi.com logo
Powered by
#general
Title
# general
g

gifted-gigabyte-53859

11/16/2023, 3:28 AM
I'm getting an error
Copy code
error: unable to validate AWS credentials.
    Details: error validating provider credentials: error calling sts:GetCallerIdentity: operation error STS: GetCallerIdentity, exceeded maximum number of attempts, 3, https response error StatusCode: 0, RequestID: , request send failed, Post "<https://sts.ap-southeast-1.amazonaws.com/>": dial tcp: lookup <http://sts.ap-southeast-1.amazonaws.com|sts.ap-southeast-1.amazonaws.com> on 1.1.1.1:53: read udp 192.168.65.21:49796->1.1.1.1:53: i/o timeout
    
    Make sure you have:
    
         • Set your AWS region, e.g. `pulumi config set aws:region us-west-2`
         • Configured your AWS credentials as per <https://pulumi.io/install/aws.html>
         You can also set these via cli using `aws configure`.
My aws credentials are properly configured and working in the shell using 
aws sts get-caller-identity --profile MYPROFILE
c

cuddly-computer-18851

11/16/2023, 3:34 AM
Can you please show your provider code, or stack config if using the default provider?
g

gifted-gigabyte-53859

11/16/2023, 3:38 AM
@cuddly-computer-18851 sure, I'm using the default provider. I've made no changes since yesterday when this was working. Here's my 
Pulumi.develop.yaml
file with some redactions
Copy code
config:
  aws:profile: 12345_AWSAdministratorAccess
  aws:region: ap-southeast-1
  xxx-onsite-payment-app:aws_account_id: "12345"
  xxx-onsite-payment-app:aws_route53_zoneid: Z0xxxxxPEXY1
  xxx-onsite-payment-app:dns_domain: <http://xxx.xxx.io|xxx.xxx.io>
  xxx-onsite-payment-app:dns_subdomain: develop
  xxx-onsite-payment-app:protect_dynamodb_tables: false # currently not working
c

cuddly-computer-18851

11/16/2023, 4:00 AM
are you using an ec2 instance profile for this role?
Copy code
Post "<https://sts.ap-southeast-1.amazonaws.com/>": dial tcp: lookup <http://sts.ap-southeast-1.amazonaws.com|sts.ap-southeast-1.amazonaws.com> on 1.1.1.1:53: read udp 192.168.65.21:49796->1.1.1.1:53: i/o timeout
actually this kind of just looks like a local connection issue - reboot, check for any firewall changes etc?
g

gifted-gigabyte-53859

11/16/2023, 4:42 AM
No, just normal credentials
Yep, it's working now. Not sure why aws CLI would work but Pulumi doesn't work. False alarm, still not working. I'll try rebooting the laptop. 
aws sts get-caller-identity --profile 12345_AWSAdministratorAccess
is still working fine
My internet went down shortly after my last message so was unable to test. Trying again this morning
It's working again. Seems not unlikely that it was internet related. Like the connection was beginning to drop out or something.
s

salmon-account-74572

11/17/2023, 8:55 PM
We just opened an issue on this, can you upvote and add any additional pertinent information about what you were seeing? https://github.com/pulumi/pulumi-aws/issues/3023
2 Views
Powered by