I believe your access key and secret key are only authorized for one region at a time. I would suggest to generate a new access key and secret key for the other regions…
I.e. I am authorized to send from us-west-1, but the keys to do that do not work for other regions. You need to setup new keys authorizations to send from other regions.
Oddly, I also verified my domain with another region us-west-2 (Oregon) and sending works for that region with the same access key and secret key. Maybe my account is limited to the US regions but I cannot see that mentioned anywhere.
@andrewcv@danwaterloo There is a new release, 1.3.0, of the plugin that uses AWS signature version 4, instead of version 2. That works for me with the “new” regions as well as the old ones.
You can update the Amazon SES plugin on the Manage Plugins page but you also need to update Common Plugin as well to version 3.12.0. Or you can continue using your currently installed plugins if you want to.
There is an additional field on the Settings page for the region, e.g. ap-south-1.
By the way, i just noticed that the database settings were updated to us-east-1 when I upgraded the plugin (to support the new curl commands). Previous to the update, it was set to us-west-2, which is where I am authenticated.
The region was a new field which defaults to us-east-1 but the endpoint should have not been changed by the plugin update. It looks like that gave you an inconsistent pair of fields. Are you able to confirm whether that is what seems to have happened?
Hi Duncan, yes, that seems to be what happened. Somehow the endpoint was automatically defined or re-defined when updating the plugin. It could be that I originally defined the endpoint in the config.php file, and one one of the more recent updates of the plugin it defined it in the database, which overpowered the config file?