Amazon SNS

Amazon SNS

Utilities / Communications / Mobile Push Messaging
Director Product Management at Centime·
Needs advice
on
Amazon SNSAmazon SNS
and
TwilioTwilio

Hi, We are looking to implement 2FA - so that users would be sent a Verification code over their Email and SMS to their phone.

We faced some limitations with Amazon SNS where we could either send the verification code to email OR to the phone number, while we want to send it to both.

We also are looking to make the 2FA more flexible by adding any other options later on.

What are the best alternatives to SNS for this use case and purpose? Looked at Twilio but want to explore other options before making a decision.

Would be great to know what the experience with Twilio has been, especially the limitations/issues with Twilio...

Appreciate any input from users of Twilio and others who have had similar use cases.

READ MORE
7 upvotes·207.2K views
Replies (4)
Head of Engineering at Stream Financial Technology·

I would recommend Twilio as well. If you're objective is to get off the ground quickly and build something that is robust without much effort, Twilio really nails the developer experience and easy of use. It's also light on any kind of set up or infrastructure as code. That said, it's a lot more expensive that AWS alternatives, so if you're operating at scale you may want to look closer at AWS options.

READ MORE
2 upvotes·11.9K views
VP Engineering at Not disclosed·

2FA Security is a pretty important topic. While as a convince it would be great to broadcast the security code to as many devices as possible this is fundamentally a bad security practice. Imagine for a minute that a bad actor has compromised one or the other of your message platforms now when you attempt to login to fix things they're also given your security code. If you read enough stories you will find that both email and SMS can be compromised to grab peoples codes.

Secondly, I have never interacted with a product that broadcasts to both messages upon login, they always present a choice of where to send it.

To you actual question; Twilio + SendGrid (a Twillo company) would be the default choice because both of these log what happened when you send a message. For instance with SendGrid you can see the delivery events in their UI to debug issues (e.g. was it delivered to a mailbox, or what was the error code). If you use Amazon SNS you will have to build out all of the logging to know what happened. At some point you'll need to have all of this info in your product because your CS agents will need it for quick debugging of customer issues, but when you first roll out it's great to just let the service do the logging.

READ MORE
2 upvotes·22.2K views
View all (4)
Needs advice
on
Amazon SNSAmazon SNS
and
FirebaseFirebase

We are developing an app with Angular 11, Node.js & MongoDB. The app is hosted on AWS. We are now building the in-app push notification (batch & events). What would be a better option - Amazon SNS or Firebase?

READ MORE
2 upvotes·10.6K views
Lead Consultant at Knoldus Software LLp·
Needs advice
on
Amazon PinpointAmazon Pinpoint
and
Amazon SNSAmazon SNS

Instead of Amazon SNS, which is currently being used to send outbound push notification and including SMS, we want to build the 2 Way SMS using Amazon Pinpoint. Just want to know about Pinpoint and any outstanding issues if we drop SNS since it does not support 2 Way and use Pinpoint for both incoming and outgoing flow.

READ MORE
6 upvotes·248.3K views
Engineering Manager at Taylor and Francis·

We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.

To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas

To build #Webapps we decided to use Angular 2 with RxJS

#Devops - GitHub , Travis CI , Terraform , Docker , Serverless

READ MORE
19 upvotes·1 comment·4.1M views
Jon Senterfitt
Jon Senterfitt
·
January 29th 2021 at 7:07AM

But why not just use Contentful?

·
Reply