- Newest
- Most votes
- Most comments
Hello,
I see that you are encountering the error "The request signature we calculated does not match the signature you provided." This kind of error typically comes from an error in the canonicalization of the request, the incorrect derivation or use of the signing key, or a validation failure of signature-specific parameters sent along with the request. In this case, it would be suggested to check your AWS Secret Access Key and signing method.
https://docs.aws.amazon.com/general/latest/gr/signature-v4-troubleshooting.html
If the signature sent in your request and the one calculated by AWS do not match, the API request will be denied. This applies to requests to start/stop your instances.
https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html
However, since you mentioned that you used the console and not an API call, you might want to try another solution. Actually, there have been previous reports of this issue when attempting to create a CloudWatch Alarm and it was resolved by logging out of the AWS Console session and logging back in.
Since re:Post is a public platform, it is not recommended to discuss signatures in detail due to security and privacy reasons. To further troubleshoot your issue, feel free to reach out to us via a support case to facilitate a discussion on the specifics of your resources.
Relevant content
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 10 months ago
It's not very clear what are you trying to do. You're trying to add cloudwatch alarm for EC2 instance from AWS Console, right? But what about Apache, not clear why you mentioned it. Is it running on that instance?
Hey A-Shevchenko
Thanks for answering. I was trying to add a cloudwatch alarm for CPU overage to my instance from the cloudwatch console page. After configuring what I wanted and clicking "add alarm", the console UI "spun" for about 2 minutes, and as a side note, apache that was running on the instance in question became unresponsive; eventually, the alarm failed to set, and the above error was returned.
My real question is what does that error actually mean, and will other console functions like stopping / restarting the instance fail due to the same issue.
thanks