- Issue created by @orakili
- First commit to issue fork.
- Merge request !23Issue #3446425: Catch the "credentials expired" AWS error and retry after obtaining new ones. → (Merged) created by cafuego
- First commit to issue fork.
- 🇺🇸United States davisben NH
I rebased against 3.x and did a quick review. The changes look good, but I don't have any expiring credentials set up to test with. If someone can confirm this works as intended, I'll get it committed.
- 🇦🇺Australia cafuego
I live tested this on one of my Drupals yesterday, with the credential timeout set to 900s and a sleep(910); in the send() code :-) It took a bit of fiddling, as I expected the code to throw an `Aws\Sts\Exception\ExpiredTokenException` class but that never happened, it was an SesV2Exception instead with the error code it now checks for.
About 15 minutes after the gateway timeout from nginx I got the logs I expected *and* the amazon_ses test email.
How do you feel about adding a counter in the class to limit the number of retries?
-
davisben →
committed 1d74be7d on 3.x authored by
cafuego →
Issue #3446425: Catch the "credentials expired" AWS error and retry...
-
davisben →
committed 1d74be7d on 3.x authored by
cafuego →
Automatically closed - issue fixed for 2 weeks with no activity.