-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS IAM and other services don´t work anymore (TLS issue) #4573
Comments
I'm sorry you're running into this @timlukastlt. I'm starting to investigate it and will provide updates as soon as possible! |
@timlukastlt I'm not yet able to reproduce this on my end, but I'm strongly convinced that this was caused by upgrading the provider to use Go 1.23. @timlukastlt can you try downgrading pulumi-aws to v6.50.1. This one is still using Go 1.22 and shouldn't be affected. |
@flostadler thank you for investigating this issue so promptly. I tested with version v6.50.1, and it works with that one.👍 |
The fix got merged, I kicked off a release that should complete in the next hours |
This issue has been addressed in PR #4583 and shipped in release v6.54.1. |
Describe what happened
Pulumi is attempting to make a request to

iam.amazonaws.com
but uses TLS 1.0. Since AWS only supports higher versions of TLS, the request is blocked, as shown in the image below:For sts as an example the requests from Pulumi are working because is uses TLS3.
Sample program
Log output
The programm just shows creating... for one hour (55-65 minutes)
After that it shows that the connection to iam.amazonaws.com was not possible.
Affected Resource(s)
We got this error for iam
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: