Skip to content
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

[Bug]: CredentialsProviderError is not treated as a connection error #473

Closed
jamesmbourne opened this issue Mar 12, 2024 · 2 comments · Fixed by #474
Closed

[Bug]: CredentialsProviderError is not treated as a connection error #473

jamesmbourne opened this issue Mar 12, 2024 · 2 comments · Fixed by #474

Comments

@jamesmbourne
Copy link
Contributor

Describe the bug

The isConnectionError function does not account for the CredentialsProviderError which can be thrown by the AWS SDK for JavaScript v3.

Failure to handle this error means the default pollingWaitTimeMs of 0ms will be used, instead of the 10,000ms authenticationErrorTimeout, producing a high volume of errors if there is an IAM misconfiguration or failure.

Your minimal, reproducible example

N/A

Steps to reproduce

  1. Pass invalid IAM configuration
  2. Receive messages

Expected behavior

Delay of 10s applies

How often does this bug happen?

Every time

Screenshots or Videos

No response

Platform

macOS, Linux

Package version

v9.0.0

AWS SDK version

v3

Additional context

No response

Copy link

🎉 This issue has been resolved in version 9.1.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Copy link

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant