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
IncompleteSignatureException - SSM #4285
Comments
Same here with the SES service. IncompleteSignature: Authorization header requires 'Credential' parameter. Authorization header requires 'Signature' parameter. Authorization header requires 'SignedHeaders' parameter. Authorization=AWS ASIA6NIRPE3ZBWHOQTEZ:fjLvBCuKKlNJnxPJ1Frz23LNrm8= |
+1 |
1 similar comment
+1 |
+1 |
@jeyarajcs @kayman-mk Do you have a minimal repro that we can use to reproduce this? |
Related to #4286, the team is working on pushing a fix. |
Closing as duplicate of #4286 Please comment with a minimal repro, or open a new bug report if the issue continues to exist after |
Describe the bug
The recent release
2.1262.0
, causes the SSM parameter fetching issue and leads to container crashes.I am attaching the traces below.
Everything was working fine till today morning, and we pushed some changes from our side, but then the containers started crashing. After spending an hour, we figured that the issue was from
aws-sdk@2.1262.0
. Now we reverted toaws-sdk@2.1259.0
and things are working well.Expected Behavior
The containers/code should work without any issues.
Current Behavior
The containers/code crashes constantly.
Reproduction Steps
Try the new SDK version
2.1262.0
Possible Solution
I think the latest change in the SDK might contain some strict validation. Please add some backward compatibility.
Additional Information/Context
No response
SDK version used
2.1262.0
Environment details (OS name and version, etc.)
Linux/Ubuntu
The text was updated successfully, but these errors were encountered: