2 Answers
- Newest
- Most votes
- Most comments
1
There is an exception for region ap-south-1. You need to get out of the sandbox in a different region: ap-southeast-1 I found this exception here:
SMS messages from Amazon Cognito user pools are routed through Amazon SNS in the same region unless noted in the following table.
| Amazon Cognito Region | Supported SNS regions |
|---|---|
| US East (Ohio) us-east-2 | us-east-1 |
| Asia Pacific (Mumbai) ap-south-1 | ap-southeast-1 |
| Asia Pacific (Seoul) ap-northeast-2 | ap-notheast-1 |
| Canada(Central) ca-central-1 | us-east-1 |
| Europe (Frankfurt) eu-central-1 | eu-west-1 |
| Europe (London) eu-west-2 | eu-west-1 |
Example: If your Cognito user pool is in us-east-1 region, you can update the Amazon SNS limit in us-east-1 region.
Example: If your Cognito user pool is in ap-south-1 region, you can update the Amazon SNS limit in ap-southeast-1 region.
answered 4 years ago
1
Please check and confirm your SPF and DKIM settings. I faced similar issue with AWS SES with office365, once I fixed the DKIM it started working properly.
For more information on AWS SES DKIM and SPF:
- Authenticating Email with SPF in Amazon SES
- Authenticating Email with DKIM in Amazon SES
- Setting Up Easy DKIM for a Domain
Also please check following:
answered 4 years ago
Relevant content
- asked 3 years ago
- asked 7 months ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 9 months ago
