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

<@U03QV9ATT61> do you have security software on your machine that might block outbound connections? pulumi connects to resource providers over GRPC on localhost, sometimes software can block these

I haven't changed any config that Im aware of in the past week or two since I last ran the automation api script

I've found the source of the issue, I had forgot to sso login and specify my AWS_PROFILE before running the command to invoke the automation API

This is an awful error message for a situation where it simply can't find/authenticate with my AWS credentials.

I will open a GitHub issue reporting this

<@U03QV9ATT61> agreed that he failure mode and error messages here should be substantially better.

Would you mind opening an issue? <http://github.com/pulumi/pulumi/issues/new|github.com/pulumi/pulumi/issues/new>

Looks like this is the exact issue you hit, already an open issue: <https://github.com/pulumi/pulumi/issues/12970>

And luckily there is a PR open with a fix! <https://github.com/pulumi/pulumi/pull/13070>