John L.

Hi @ctanonyome - thanks for reaching out. This's more of a feature request for service team (Amazon SES) which you can either contact SES team directly via [AWS Support](https://aws.amazon.com/contact-us/) or...

Thanks for reaching out. I'm taking a look. Does this only apply to the use case with expired credentials?

Hi @zeeshanmakeen - thanks for stopping by. I wasn't able to reproduce this using our https://github.com/aws-samples/aws-sdk-js-tests repo. Just to confirm you're running this in React?

Appreciate the update, it sounds like service team need to add the header on their end. I'll check in with them internally.

Hi @jaube-litify - thanks for reaching out! Back in January, we [adopted](https://github.com/aws/aws-sdk-js-v3/issues/6810) S3 default integrity change starting on the version of `v3.729.0` where clients now default to enabling an additional...

Hi @H1Gdev - thanks for stopping by. This sounds like a testing error by Jest, rather than SDK issue. Per [this comment](https://stackoverflow.com/a/79143885), you may need to explicitly enable the `--experimental-vm-modules`...

Hi @racdev - thanks for stopping by. In order for me to provide some guidance, can you share your SDK code snippet? Since it's intermittent, are you able to share...

HI @ghassen-chetioui - thanks for reaching out. Based off the error, it sounds like you might be missing permission to assume cross-account resource-based policy in Lambda. Here's [docs page](https://docs.aws.amazon.com/lambda/latest/dg/access-control-resource-based.html#permissions-resource-xaccountinvoke) on...

Appreciate you for getting back. It sounds like this occurs intermittently. We would need minimal repro code and error logs that would give us more insight on finding the root...

Since we haven't heard back, I'll be closing the issue. Feel free to open a new one if issue persists.