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

Can you please show your provider code, or stack config if using the default provider?

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

are you using an ec2 instance profile for this role?

&gt; 
&gt; ``` 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-&gt;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?

~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.

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>