1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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.
con risposta 5 anni fa