How to Set Up Multi-Channel Notifications in Your AWS Stack

1

gRPC

The notification service usually needs to expose an API to which other services can connect. The API can be synchronous, available through an HTTP REST or GRPC endpoint, or asynchronous and based on a message broker, like RabbitMQ.

#Web Servers #Web And Application Servers #Load Balancer / Reverse Proxy 86 social mentions

2

Mustache.js

Now we'll define an email template. We’ll use AWS SES’s built-in template functionality, but you could use a library like mustache.js or build your own templating system instead. Our template map contains the fields that SES requires in their API:.

#Javascript UI Libraries #Front-End Frameworks #Development 11 social mentions

3

cURL

Now we’ll try issuing a POST request to the /notify endpoint. We’ll use cURL for this purpose, but you can also use an app like Postman:.

#API Tools #APIs #Developer Tools 105 social mentions

4

Amazon SQS

As we mentioned above, any SNS notification that cannot be delivered will end up in a dead-letter queue. This queue is an Amazon Simple Queue Service (SQS) queue, and you’ll need to implement functionality to listen for messages on this channel.

#Data Integration #Stream Processing #Web Service Automation 64 social mentions

5

Amazon SNS

Amazon Web Services offers two products for end-user notifications: SES and SNS. Both services have a pay-per-use pricing model that’s ideal for companies that want to start small and scale up their AWS use as the business grows.

#Data Integration #Stream Processing #Web Service Automation 54 social mentions

6

Amazon SES

Amazon Web Services offers two products for end-user notifications: SES and SNS. Both services have a pay-per-use pricing model that’s ideal for companies that want to start small and scale up their AWS use as the business grows.

#Email Delivery #Email Marketing #Transactional Email 65 social mentions