Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug in 0.4.0 - SES #170

Closed
jantman opened this issue Mar 15, 2016 · 2 comments
Closed

Bug in 0.4.0 - SES #170

jantman opened this issue Mar 15, 2016 · 2 comments

Comments

@jantman
Copy link
Owner

jantman commented Mar 15, 2016

SES only currently supports three regions and throws a connection error if used to connect to any other region.

jantman added a commit that referenced this issue Mar 15, 2016
fixes #170 and bump to 0.4.0 - emergency fix for SES unavailable region bug
@pdecat
Copy link

pdecat commented Mar 15, 2016

Hi, I was about to report this issue, you're too fast! ;)

@jantman
Copy link
Owner Author

jantman commented Mar 15, 2016

@pdecat many apologies for this. My integration tests all run against us-east-1...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants