1 Answer
- Newest
- Most votes
- Most comments
0
Our problem is solved with including the 'X-SES-CONFIGURATION-SET' custom header parameter in the call to SES. But so, the default configuration set seems not to get used when making the call via IAM user
answered 5 years ago
Relevant content
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 10 months ago
