SMS · Cloud-native, one bill

Connect your own AWS End User Messaging account

Native AWS messaging that lands on your existing AWS invoice — the natural choice if your infrastructure already lives in AWS.

Scope. This integration sends SMS. Delivery events come back through the provider’s webhook and are normalized into the same three statuses as SMS, so a delivery reads the same way whichever channel carried it. Routing and automatic failover, per-number pacing and segment accounting are SMS-channel features. Opt-out suppression is applied to marketing sends on every channel. Whaleal Platform is a message orchestration layer: it calls AWS End User Messaging’s public API using your account. We do not resell message volume, do not mark up your AWS End User Messaging bill, and do not own your account.

What you need from AWS End User Messaging

Gather these in the AWS End User Messaging portal first. The connection form asks for exactly these fields and nothing more.

FieldWhat it is
accessKeyIdAccess Key ID. An IAM access key with permission to send SMS.
accessKeySecretSecret Access Key. Paired with the access key above.

Credentials are sealed with AES-256-GCM and the console only ever shows a masked value afterwards. Plaintext is never written to logs and never sent back to the browser.

What we configure on the connection

  • AWS region. Required. Messaging availability and sender identities differ per region.
  • Sender IDs. Numbers, short codes or sender IDs available in that region.
  • Default send pacing: 1 message per second. This is a conservative starting point, applied per connection, and you can change it at any time. Your real ceiling is set by AWS End User Messaging — check your account quota and raise the value to match.
  • Region is required. Sending quotas and available sender identities differ per region.

Why teams pick AWS End User Messaging

  • Billing and IAM stay inside your AWS account
  • Per-region sender identities
  • Consistent with the rest of an AWS-based stack

Worth knowing

  • The region is mandatory — messaging limits and available sender types are region-specific.
  • Our default pacing starts at 1 message/second. AWS grants sending quotas per account and region, so check your Service Quotas page and raise the pacing to match.

What stays on your side

These are yours to hold — and that is the point of bringing your own account: the relationship, the rates and the compliance stay in your name, not ours.

  • Account approval, credit checks and arrears
  • Sender ID, number and short-code registration for each destination
  • Local telecom and privacy compliance in the countries you send to, including opt-out rules
  • The quotas and rate limits AWS End User Messaging grants your account

Next

Whaleal Platform currently offers self-service connections to 6 SMS providers, 4 email providers and 3 WhatsApp providers. Underlying the SMS channel is an SMS adapter library of 33 adapters; the ones outside this list are unlocked on request rather than self-service.