SNS SMS fails: No origination identity available to send to destination number — Sender ID is active

Question

We are using Amazon SNS to send SMS messages in the EU (Ireland) region.

Our Sender ID is already registered and confirmed active by AWS Support.

Our account has exited SMS sandbox mode, and delivery status logging is working, but when we attempt to send messages with the Sender ID, we get this error:

"No origination identity available to send to destination number"

It appears that although the Sender ID is active, it is not linked as an origination identity in Amazon Pinpoint SMS and Voice V2, which SNS now uses after sandbox removal.

We don’t have access to the Pinpoint SMS V2 origination identity page in the console, and Support referred us to the documentation and forums.

How can we ensure our Sender ID is fully usable with SNS under the current Pinpoint V2 infrastructure?

Thank you!

re:Post Agent · Answer

The error you're encountering suggests that there might be an issue with the permissions or resource policy associated with your Sender ID. Even though your Sender ID is registered and confirmed active, it may not have the correct permissions to be used by Amazon SNS for sending SMS messages.

To resolve this issue, you need to update the resource policy for your Sender ID to grant the necessary permissions to SNS. Here's what you should do:

1. Navigate to the AWS End User Messaging console.

2. Go to the "Sender IDs" section.

3. Select your active Sender ID.

4. Update the resource policy for the Sender ID by adding a JSON policy that grants permissions to SNS (and Pinpoint if you plan to use it) to use this origination identity.

The policy should look similar to this:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AllowSNSAndPinpoint",
            "Effect": "Allow",
            "Principal": {
                "Service": [
                    "sns.amazonaws.com",
                    "pinpoint.amazonaws.com"
                ]
            },
            "Action": [
                "sms-voice:SendTextMessage",
                "sms-voice:SendVoiceMessage"
            ],
            "Resource": "arn:aws:sms-voice:eu-west-1:YOUR_ACCOUNT_ID:sender-id/YOUR_SENDER_ID/COUNTRY_CODE"
        }
    ]
}

Make sure to replace YOUR_ACCOUNT_ID, YOUR_SENDER_ID, and COUNTRY_CODE with your specific details. The region (eu-west-1 in this example) should be set to the EU (Ireland) region you're using.

If you don't have access to the console to make these changes, you may need to use the AWS CLI or SDK to update the resource policy. You can use the `PutResourcePolicy` API call from the Pinpoint SMS and Voice V2 service to do this programmatically.

After updating the resource policy, try sending an SMS message again through SNS. This should resolve the "No origination identity available" error and allow you to use your Sender ID with SNS under the current Pinpoint V2 infrastructure.

If you continue to experience issues after updating the resource policy, it would be advisable to open a new support case with AWS, providing details of the steps you've taken and any error messages you receive.  
**Sources**  
["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](https://repost.aws/articles/ARq-jq4ZWQTJqRg5_B4fqFZw/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)  
["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](https://repost.aws/articles/ARq-jq4ZWQTJqRg5_B4fqFZw/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)  
[A Guide to the New Resource Policies for SMS Origination Identities in AWS | AWS Messaging & Targeting Blog](https://aws.amazon.com/blogs/messaging-and-targeting/a-guide-to-the-new-resource-policies-for-sms-origination-identities-in-aws/)

SNS SMS fails: No origination identity available to send to destination number — Sender ID is active

Relevant content