1 Answer
- Newest
- Most votes
- Most comments
0
After some help from AWS technical support, the issue was resolved by following the steps below.
- Create a policy as shown below. There are two key points;
- Ignore the two "Invalid Action" errors related to SendOTPMessage and VerifyOTPMessage in the GUI. Save the policy
- Ensure that the Resource URL is exactly as specified and uses your account id.
In other words, use this instead of the policy example in "Step 2.1: Create an IAM policy" at https://docs.aws.amazon.com/pinpoint/latest/developerguide/tutorials-two-way-sms-part-2.html
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "UseConsole",
"Effect": "Allow",
"Action": [
"mobiletargeting:SendOTPMessage",
"mobiletargeting:VerifyOTPMessage"
],
"Resource": "arn:aws:mobiletargeting:*:YOUR_ACCOUNT_ID:apps/*"
}
]
}
- Attach this policy to the user.
answered 4 years ago
