Fails to use key & secret on local dev environment about aws-ses-wp-mail

[joehoyle]

Doh, my bad I think!

[roborourke]

@joehoyle no worries! Super easy to miss, I was digging through the SDK for a while to find out what it was doing! I have the AWS CLI on my laptop rather than the VM so probably why I hit this problem. What do you think re. fetching the token? I can put some time into it.

[joehoyle]

Hmm this is the first I've heard about this token, this isn't required for other AWS Services, is this something SES specific?

[roborourke]

I think so. It's the first time I've come across it too. I may be missing something but just going off what the error messages say. You should be able to reproduce it by moving your ~/.aws folder temporarily and adding the key & secret & region constants

[BrookeDot]

I just ran into this today when installing this plugin for the first time in production. I went with option B (but didn't need the token) to get the creds to verify. Found the answer on StackOverflow then came here. I changed line 178 of inc/class-ses.php to read:

          if ( $this->key && $this->secret ) {
                $params['credentials']['key'] = $this->key;
                $params['credentials']['secret'] = $this->secret;
                }