Event Sources and Destinations
Event-driven computing is a model in which subscriber services automatically perform work in response to events triggered by publisher services. This paradigm can be applied to automate workflows while decoupling the services that collectively and independently work to fulfil these workflows.
Amazon SNS is an event-driven computing hub that has native integration with a wide variety of AWS event sources (including Amazon EC2, Amazon S3, and Amazon RDS) and AWS event destinations (including Amazon SQS, and Lambda).
The full set of Amazon SNS event sources includes the following AWS services:
- Compute: Elastic Beanstalk, Elastic Load Balancing, EC2 Auto Scaling, AWS Lambda
- Storage: Simple Storage Service, Elastic File System, Glacier, Snowball
- Database: Relational Database Service, ElastiCache, Redshift, Database Migration Service
- Networking: Route 53, Direct Connect
- Developer Tools: CodeCommit, CodeBuild, CodeDeploy, CodePipeline
- Management Tools: CloudWatch (Alarms, Events), CloudFormation, CloudTrail, Config
- Customer Engagement: Simple Email Service, Pinpoint
- Analytics: Data Pipeline
- Security: Inspector
- Media: Elastic Transcoder
- Internet of Things: IoT Platform
- Game Development: Lumberyard
Amazon SNS can filter and fanout events to the following destinations to support event-driven computing use cases:
Message filtering empowers the subscriber to create a filter policy, so that it only gets the notifications it is interested in, as opposed to receiving every single message posted to the topic. Visit our blog to learn how to simplify your pub/sub messaging with Amazon SNS message filtering and get to know message filtering operators for numeric matching, prefix matching, and blacklisting in Amazon SNS. Additionally, you may monitor your Amazon SNS message filtering activity with Amazon CloudWatch and manage Amazon SNS filter policies with AWS CloudFormation.
Message fanout occurs when a message is sent to a topic and then replicated and pushed to multiple endpoints. Fanout provides asynchronous event notifications, which in turn allows for parallel processing. Try our 10-minute tutorial to learn how to send fanout event notifications with Amazon SNS.
Amazon SNS supports VPC Endpoints (VPCE) via AWS PrivateLink. You can use VPC Endpoints to privately publish messages to Amazon SNS topics, from an Amazon Virtual Private Cloud (VPC), without traversing the public internet. This feature brings additional security, helps promote data privacy, and aligns with assurance programs.
When you use AWS PrivateLink, you don’t need to set up an Internet Gateway (IGW), Network Address Translation (NAT) device, or Virtual Private Network (VPN) connection. You don’t need to use public IP addresses, either.
You may visit our blog to learn how to secure messages published to Amazon SNS with AWS PrivateLink. You can also deploy Amazon VPC endpoints for Amazon SNS with AWS CloudFormation.
Amazon SNS mobile notifications make it simple and cost effective to fanout mobile push notifications to iOS, Android, Fire OS, Windows and Baidu-based devices. You can also use SNS to fanout text messages (SMS) to 200+ countries and fanout email messages (SMTP).
Alternatively, if your use case can benefit from advanced user engagement and retention features such as mobile notification templates, delivery schedules, targeted customer segments, campaigns, analytics, and A/B testing, then Amazon Pinpoint is the recommended AWS service to support your mobile messaging use case.