AWS: How to Log SMS Events to CloudWatch

Select Language:

If you’re sending SMS messages through AWS End User Messaging SMS (Pinpoint SMS Voice V2) and aren’t seeing any logs in CloudWatch, even when everything seems set up correctly, here’s a straightforward way to troubleshoot and resolve the issue.

First, check your setup. Make sure the necessary parts are configured properly:

– Confirm that your CloudWatch Log Group, named ‘eum/messaging-events,’ exists in the correct region (like us-east-2) and has a retention period of 14 days.
– Verify that your IAM role, called ‘eum-logging-service-role,’ has the correct permissions, including the ability to create log groups, streams, describe them, and put log events. Also, ensure the trust policy allows the SMS service to assume this role.
– Look at your configuration set, which should be named ‘production-config-set.’ Make sure it has an enabled CloudWatch event destination named ‘sms-events-cloudwatch.’ Double-check the event types you want to log are selected, such as ‘TEXT_SENT.’

Next, review your event destination details. The destination should have the correct IAM Role ARN, and the log group ARN must be accurate. For example:

– IAM Role ARN: ‘arn:aws:iam::123456789012:role/eum-logging-service-role’
– Log Group ARN: ‘arn:aws:logs:us-east-2:123456789012:log-group:eum/messaging-events’

Once everything looks good, test sending an SMS directly via CloudShell:

1. Run this command, replacing phone numbers and identities with your data:

bash
aws pinpoint-sms-voice-v2 send-text-message \
–destination-phone-number “+1YOURNUMBER” \
–origination-identity “+1YOURID” \
–message-body “Configuration test – $(date)” \
–configuration-set-name “production-config-set” \
–region us-east-2

2. After successful sending, check the response for a message ID.

3. To verify logs, first list your log streams:

bash
aws logs describe-log-streams \
–log-group-name “eum/messaging-events” \
–region us-east-2 \
–order-by LastEventTime \
–descending

If no log streams appear, then no logs have been generated yet.

4. Next, look for recent log events from the past 15 minutes:

bash
aws logs filter-log-events \
–log-group-name “eum/messaging-events” \
–region us-east-2 \
–start-time $(date -d ’15 minutes ago’ +%s)000

If still no events are returned, no logs have been captured.

5. Lastly, search for your specific message ID in the logs to find related events:

bash
aws logs filter-log-events \
–log-group-name “eum/messaging-events” \
–region us-east-2 \
–filter-pattern “YOUR_MESSAGE_ID”

If this yields nothing, there’s a service-level problem you might need support to investigate.

To sum it up: double-check all permissions, confirm configuration details, and perform the send and log checks again. Sometimes, logs just take a little time to appear, but if you’ve waited longer than 15 minutes with no results, it points to a deeper issue.

If everything seems set up correctly but logs still don’t show up, contact AWS Support. They can help identify if there’s a service issue affecting log events for your SMS messages.