1 Answer
- Newest
- Most votes
- Most comments
0
The issue was that I was using the wrong region for ses client. For some reason due to a configuration mishap a S3 region was used instead ('s3.us-east-1'). The extra s3 caused the issue.
answered 5 years ago
Relevant content
- asked 10 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 2 months ago