1 Answer
- Newest
- Most votes
- Most comments
2
Hi, You should probably read this very recent blog: https://aws.amazon.com/blogs/messaging-and-targeting/how-to-manage-global-sending-of-sms-with-amazon-pinpoint/
The section "Best Practices for Sending" answers some of your points.
Also, this blog post provides an architecture to share and control your SMS traffic: https://aws.amazon.com/blogs/messaging-and-targeting/queueing-amazon-pinpoint-api-calls-to-distribute-sms-spikes/
Hope it helps Didier
Relevant content
- asked 4 months ago
- asked 5 months ago
- asked 3 months ago
- asked 2 years ago
- How do I set up logging for Amazon Pinpoint voice messages for Amazon Pinpoint SMS and Voice v2 API?AWS OFFICIALUpdated a year ago
- How do I set up logging for Amazon Pinpoint voice messages for Amazon Pinpoint SMS and Voice v1 API?AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Hi Didier,
Thanks for the link to the post. It is very useful. I recommend the article to be listed as a must-read in aws's sms documentation.
May I ask one more question - from the knowledge base (link follows), it mentioned that "Amazon SNS and Amazon Pinpoint SMS charges can be higher than expected if messages exceed the message parts per second (MPS) limits." (https://repost.aws/knowledge-center/sns-pinpoint-high-sms-charges)
But according to the blog post (if I understand it correctly), Pinpoint does not queue the messages and will simply return error when rate exceed the carrier's limit. If this is true, how can SMS charges be higher than expected? Does it mean Pinpoint will charge all messages sent even if it resulted in error (with undeliverable endpoint, or with rate exceed error)?
Thank you very much for your link and your help! Frederick