Unable to send test message in Pinpoint Project: "PERMANENT_FAILURE The provided number does not exist or does not belong to the account, or its resource policy does not allow Pinpoint to use it."
I receive a an error message that reads:
However when I test in AWS End User Messaging with the same info/parameters, the message is sent successfully.
I believe the issue may be caused by a discrepancy with the Pinpoint project not being fully in production. The project dashboard shows the project as being in the Sandbox.
However in the project settings, the project shows as in production.
Any advice is much appreciated?
- Newest
- Most votes
- Most comments
The error message "PERMANENT_FAILURE The provided number does not exist or does not belong to the account, or its resource policy does not allow Pinpoint to use it" indicates that there's an issue with the permissions for your origination identity (phone number or sender ID).
With the introduction of AWS End User Messaging service, origination identities now require explicit permissions through resource policies to be used by services like Amazon Pinpoint. Even though you've acquired the necessary origination identity and can successfully send messages through the End User Messaging console, Pinpoint needs specific permissions to use this identity.
To resolve this issue:
-
Navigate to the "End User Messaging" console in your AWS account and region.
-
If you're using a phone number as your origination identity:
- Click on "Phone numbers" in the left navigation
- Select your origination number
- Navigate to the "Resource policy" tab
- Add permissions to allow Pinpoint to use this phone number
- If you're using a Sender ID:
- Click on "Sender IDs" in the left navigation
- Select your Sender ID
- Navigate to the "Resource policy" tab
- Add permissions to allow Pinpoint to use this Sender ID
The sandbox/production status you're seeing is related to your account's SMS capabilities and spending limits, but the immediate issue is that your origination identity's resource policy doesn't grant Pinpoint the necessary permissions to use it for sending messages.
After updating the resource policy, you should be able to send messages successfully through Pinpoint.
Sources
"The provided number does not exist or does not belong to the account." error when trying to send messages via SNS or Pinpoint even though the required origination identity is acquired in the account. | AWS re:Post
"NO_ORIGINATION_IDENTITIES_FOUND" error when trying to send messages via SNS or Pinpoint even though the required origination identity is acquired in the account. | AWS re:Post
Registered Sender ID not working in Pinpoint API | AWS re:Post
answered a year ago
Relevant content
asked a year ago
- AWS OFFICIALUpdated 4 years ago
