Our website hasn't changed in several years. Now it's generating the following error.
x-amz-target' is named as a SignedHeader, but it does not exist in the HTTP request.
Any pointers to documentation would be much appreciated.
Okay, I've done a bit more digging. I have inherited a nonprofit Drupal 7 site that uses AWS SES to send the organization's newsletter.
SES is dependent on the Drupal 7 AWS SDK library. This library uses the v1 version of Amazon's AWS SDK for PHP. Amazon is now on v3!
Unfortunately the Drupal AWS library hasn't been changed in 7 years.
We are facing the same issue since September 22, when calling an SES API
I'm going to add information here as I discover it. Hopefully this will be helpful to others. Or, better yet, someone can help me! :)
This seems to be the process for resolving the issue. I don't understand it (yet). https://docs.aws.amazon.com/general/latest/gr/sigv4-add-signature-to-request.html
getting same error in SQS functions started at September 19. No solution yet, already contacted AWS business support. We discovered this error happens just on some ip ranges. Check response header "primary_ip" field for this.
I think I have a solution.
The awssdk sets the key even if the value is null. Adding an IF_STMT seems to fix the issue. For me at least. This is line 385 of signature_v4query.class.php
if($x_amz_target) { $this->headers['X-Amz-Target'] = $x_amz_target; }
@rePost-User-3736199 thanks for your suggestion. We implement this now like you described to our services, is working now again. AWS Business Support suggested us same after reading your comment. Nevertheless, updating SDK is a must to be save for future.