- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hello,
Using a Separate account for sending One Time Password messages has no effect on the delivery speed.
-
From service side, Pinpoint messages will not be queued when we send messages (Transactional and OTP). Amazon pinpoint does not differentiate OTP and transactional messages.
-
Amazon Pinpoint does not follow any prioritization of One Time Passwords over Transactional messages. One needs to follow the SMS guidelines and best practices like using Short Codes/long Codes/10DLC/Sender ID’s to avoid being marked as spam by carriers.
-
For this we can make use of a Lambda Function for event_type:_SMS.FAILURE with a delay of X seconds:
[+] https://docs.aws.amazon.com/pinpoint/latest/developerguide/event-streams-data-sms.html
Also, Downstream Providers retry sending the messages until TTL expires. In case of API call failure, you can make use of the above Custom Lambda logic.
Contenus pertinents
- demandé il y a un an
- demandé il y a 5 mois
- demandé il y a un an
- demandé il y a 21 jours
- AWS OFFICIELA mis à jour il y a 5 mois
- AWS OFFICIELA mis à jour il y a 9 mois
- AWS OFFICIELA mis à jour il y a 6 mois
Hi Support team, can you explain more about what I could be able to achieve with lambda function? Does it delay the delivery failure report by X seconds or it will retry during that delay period on the AWS side?
Is there any possibility by which we can stop retry until the TTL expiry of the Downstream aggregator & carrier?