AWS End User Messaging
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

Connect AWS End User Messaging to PostHog to sync your data into the PostHog data warehouse for analysis and modeling.
Sync the SMS and voice resources of AWS End User Messaging (formerly Amazon Pinpoint SMS) from one AWS region: phone numbers, pools, sender IDs, configuration sets, opt-out lists, opted-out numbers, keywords, registrations, verified destination numbers, protect configurations, spend limits, and account attributes and limits.
Give the IAM user or role the sms-voice:Describe* actions, or only these for the tables you select:
sms-voice:DescribePhoneNumbers, sms-voice:DescribePools, sms-voice:DescribeSenderIds, sms-voice:DescribeConfigurationSets, sms-voice:DescribeOptOutLists, sms-voice:DescribeOptedOutNumbers, sms-voice:DescribeKeywords, sms-voice:DescribeRegistrations, sms-voice:DescribeVerifiedDestinationNumbers, sms-voice:DescribeProtectConfigurations, sms-voice:DescribeSpendLimits, sms-voice:DescribeAccountAttributes, and sms-voice:DescribeAccountLimits.
The API does not return sent or received messages. To analyze message events, send them from a configuration set to an event destination such as Amazon S3. All tables use full refresh because the API has no time filter.
Configuration
| Option | Description |
|---|---|
AWS access key IDType: text Required: True | |
AWS secret access keyType: password Required: True | |
AWS session tokenType: password Required: False | Temporary credentials expire. Update them before the next scheduled sync. |
AWS regionType: text Required: True |
Linking AWS End User Messaging to PostHog
- Go to the Data pipeline page in PostHog
- Click New source and select AWS End User Messaging
- Fill in the required configuration fields
- Click Next, select the tables you want to sync, and then press Import
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
phone_numbers | Origination phone numbers in the account, with their type, capabilities, and status. | Full refresh | — | — |
pools | Pools of origination identities, with their two-way and opt-out settings. | Full refresh | — | — |
sender_ids | Sender IDs in the account, with their country, message types, and registration state. | Full refresh | — | — |
configuration_sets | Configuration sets, with their event destinations and default sending settings. | Full refresh | — | — |
opt_out_lists | Opt-out lists in the account. | Full refresh | — | — |
opted_out_numbers | Destination phone numbers in each opt-out list, with the time they opted out. | Full refresh | — | — |
keywords | Keywords on each phone number and pool, with the message and action for each keyword. | Full refresh | — | — |
registrations | Registrations for phone numbers and sender IDs, with their type, status, and versions. | Full refresh | — | — |
verified_destination_numbers | Destination phone numbers that are verified for sending from a simulator or sandbox account. | Full refresh | — | — |
protect_configurations | Protect configurations that control which countries messages can go to. | Full refresh | — | — |
spend_limits | Monthly spend limits for text, voice, and media messages. | Full refresh | — | — |
account_attributes | Account attributes, such as the account tier and the default protect configuration. | Full refresh | — | — |
account_limits | Account quotas, with the quantity in use and the maximum for each resource type. | Full refresh | — | — |





