Is your feature request related to a problem? Please describe.
Our customers receive OTP sender as "NOTICE" or some random phone number. We want to be able to use our own SenderID for branding.
Describe the solution you'd like
Be able to get the OTP from API call on the server and we'll send it to customer via Twilio/Nexmo.
Describe alternatives you've considered
Tried to set SenderID in AWS Cognito but there is none.
Hi @ianpogi5
Your use case might be possible using Cognito User Pool triggers, specifically:
Pre Sign-up Lambda Trigger
The pre sign-up Lambda function is triggered just before Amazon Cognito signs up a new user. It allows you to perform custom validation to accept or deny the registration request as part of the sign-up process.
@ianpogi5
If Amazon's SNS service supports SenderID in your country, then you can set the SenderID in the console go to SNS in your region and change the SenderID in the settings.
@manueliglesias
We also are experiencing issues with the random phone numbers used by cognito and sns, and need to use another provider to setup sender id.
It is possible to build our own code delivery system and verification, but I do not think committing that much time into overwriting cognito's code generation and delivery is wise. The better approach is to allow cognito to pass off any code sms or invitiation sms to a lambda trigger that would use a custom sms provider rather than attempting to bypass cognito all together.
@KhaledSoliman, can you elaborate more on "The better approach is to allow cognito to pass off any code sms or invitiation sms to a lambda trigger" please?
There are Custom Authentication Challenge Lambda Triggers to generate otp and send via my own sms api and get the verification..... but,
it would be much simpler if we have a way to bypass only sns's SMS sending part.
My requirements are,
SNS SMS price is too high and need my product's name as sms sender (mask) so, need to plug a third party sms api
@malithjkmt I was suggesting to the cognito devs to allow us to bypass the SNS provider using a lambda trigger that receives all message out bound and we use the API that would work better in our local area to send those messages
@KhaledSoliman yes, that'll help thousands of devs..
But, for now is there a workaround for this other than Custom Authentication Challenge Lambda Triggers? or anything?
@malithjkmt As far as I know, no the only way to bypass SNS is to create your own auth flow using triggers
@malithjkmt and team was able to send sms with local sms gateway. We used custom auth challenge and its three triggers, Define Auth Challenge, Create Auth Challenge and Verify Auth Challenge.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Closing this issue as @manueliglesias followed up with the customer above. As for the Cognito related feature request, please go to Cognito's AWS Forums to request feature requests to the Cognito Service team
Most helpful comment
@malithjkmt As far as I know, no the only way to bypass SNS is to create your own auth flow using triggers