An Amazon SNS gateway needs a sending identity appropriate for its destination. PD AWS SNS lets you enter a Sender ID or Origination number; those fields do not create, register or authorise the identity in AWS.

Check the identity in AWS first

Use an identity available to the same AWS account and region as the gateway. Sender ID support varies by destination, and some destinations require registration before use. For example, AWS requires UK sender IDs to be registered. Review the current AWS destination and sender-ID guidance.

For an origination number, use a number allocated to the sending account and enabled for the intended traffic. AWS also requires a resource policy allowing Amazon SNS to use that number, including when it is in the same account. Follow AWS’s number setup guidance; do not solve a resource-policy refusal by granting the module’s IAM user broad administrative access.

Save the gateway identity

1. Open PD Modules → AWS SNS → Gateways and configure the intended Amazon SNS gateway.
2. Confirm AWS Region matches the sending setup.
3. Enter the approved Sender ID (optional) or owned Origination number (optional) in international format, as appropriate.
4. Review SMS type, save, and use Test connection to check the saved connection.

The Default Sender ID in Settings can provide a fallback when the gateway’s own sender ID is blank. Check the effective identity instead of assuming every gateway uses the same brand. For UK destinations, the module refuses a send when neither a sender ID nor an origination number is available to it.

Separate connection from delivery

A connection check does not send a text or verify identity registration and destination delivery. Before an intended real test, check sandbox verified destinations, permissions, resource policies and account limits. A real test can incur AWS charges.

If AWS accepts the request but the text does not arrive, correlate its provider reference with SMS delivery-status logs. Preserve the destination country, gateway label and redacted failure reason. Do not repeatedly resend an Unknown outcome, substitute another account’s number or post a secret key in a ticket.

See the PD AWS SNS Blesta guide for related tasks, or explore PD AWS SNS.