Amazon Simple Notification Service (AWS SNS) is a fully managed messaging service designed for high-throughput, push-based messaging between applications and subscribers. It allows developers to set up, operate, and send notifications from the cloud, simplifying decoupling and scaling microservices, distributed systems, and serverless applications.
Using SNS, users can easily send messages to a large number of subscriber endpoints, including Amazon SQS queues, AWS Lambda functions, HTTP/S endpoints, email, SMS, and mobile device push notifications. The service ensures reliable delivery of messages and allows for the straightforward management of publishing rights and subscriber permissions.
In this article
SNS offers the following features.
AWS SNS supports application-to-application messaging by enabling communication between distributed software systems and components. Developers can broadcast event notifications to multiple subscribers via a single SNS topic, creating an event-driven architecture that enhances applications’ responsiveness and efficiency.
Messages are pushed to subscribers in real-time, ensuring that events are processed quickly. This capability is crucial for scenarios involving time-sensitive information, where delays can drastically affect application outcomes.
SNS supports application-to-person communication, providing a straightforward way to engage with end-users by sending messages directly to their devices. This feature is useful for various scenarios, from alerting users about transactional activities to broadcasting relevant updates.
Through various message formats such as SMS, mobile push notifications, and emails, businesses can tailor their communication strategies according to the target audience’s needs, ensuring effective outreach and engagement.
AWS SNS offers two types of topics: standard and First-In-First-Out (FIFO). Standard topics provide high-throughput, best-effort ordering, and at-least-once message delivery. This makes them suitable for applications that require massive scale and multicast messaging, where messages are delivered to many subscribers at once.
Conversely, FIFO topics guarantee message ordering and exactly-once processing, ideal for scenarios where the order of events is critical. These topics prevent duplicates and ensure that messages are delivered exactly as they were published.
With AWS SNS, users can archive and analyze messages using other AWS services, such as AWS Lambda for processing or Amazon Kinesis for real-time data streaming. This integration is useful for creating an audit trail, which assists in decoding event patterns and understanding message interactions.
Replaying messages is another critical feature. It allows users to resend the same message to troubleshoot issues or test system performance under specific conditions. This enhances the application’s overall reliability and resilience by ensuring that critical information is not lost.
AWS SNS operates on a pay-as-you-go model, with prices depending on the type of service used—Standard or FIFO topics—and the volume of activity. Here’s an overview of how AWS SNS charges for its services, using the US East (Ohio) region as an example:
For Standard topics, AWS SNS provides the first million API requests each month at no cost. Beyond this free tier, each request costs $0.50 per million. It’s important to note that AWS calculates data transfer in 64KB chunks, billing a 256KB message as four requests. FIFO topic pricing differs slightly, with publish and publish batch requests priced at $0.30 per million and $0.017 per GB of payload data.
Various endpoints have their own pricing within the AWS SNS ecosystem. Mobile push notifications are priced at $0.50 per million after the free tier of one million notifications. Similarly, email notifications are $2.00 per 100,000, and HTTP/s notifications are charged at $0.60 per million after the respective free tiers.
Data transfer costs also factor into AWS SNS pricing. All incoming data transfers are free, while data transferred out of AWS services is priced based on volume, starting at $0.09 per GB for the first 10TB per month, scaling down in cost as the volume increases.
Message filtering using SNS varies in cost depending on the method. Attribute-based message filtering is free, while payload-based filtering is $0.09 per GB. Message protection, which includes scanning and protecting messages, is charged at $0.08 per GB, and audit reporting costs $0.19 per GB.
AWS SNS allows for message archiving and replay, where archive processing costs $0.10 per GB of payload data, and in-place storage is charged at $0.023 per GB-month. According to FIFO API request and payload data rates, any archived data is billed for at least one day.
The Amazon SNS SDK is a set of libraries and tools that allow developers to interact with AWS SNS programmatically. These SDKs are available for various programming languages and platforms, including Java, .NET, Node.js, Python, and Ruby, enabling developers to integrate and manage SNS capabilities within their applications seamlessly.
Through the SDK, users can programmatically create topics, publish messages, and subscribe to topics. It simplifies the complexity of making direct API calls, providing a more intuitive way to implement SNS functionalities and accelerating development cycles.
Simple Notification Service (SNS) is a pub/sub messaging service ideal for multicast messaging, where messages are pushed to multiple subscribers simultaneously. These may include SQS queues, AWS Lambda functions, HTTP/S endpoints, mobile push notifications, and emails. SNS is useful for fan-out architecture scenarios where a message needs to be broadcast to many receivers.
Simple Queue Service (SQS) decouples application components and enables message queuing to ensure independent microservices operate smoothly without message loss. It offers a reliable, highly scalable hosted queue for storing messages as they travel between computers. While SNS distributes the same message to multiple consumers, SQS holds the message in a queue until it’s processed by a consumer, making it more suitable for a point-to-point communication model.
Here are some of the limitations of the Simple Notification Service.
With SNS, messages can only have a payload of up to 256 KB. For applications needing to send larger payloads, additional mechanisms must be implemented to split messages or reference payloads stored elsewhere. This limitation can restrict the usability of SNS in scenarios where large data must be transmitted directly.
While SNS ensures high availability and durability, it doesn’t inherently provide redundancy in message delivery to multiple regions. Additional configurations and duplicate topics across regions might be necessary for critical systems requiring multi-region redundancy. This could increase operational complexity and costs, particularly for global applications.
AWS SNS does not offer built-in retry logic for messages not delivered to subscribers. If a message delivery fails, SNS does not automatically retry sending the message. Developers must implement their retry logic within their applications or handle failed deliveries manually, adding complexity to the application architecture.
Here’s an overview of how to use Simple Notification Service.
To create a topic, start by signing into the Amazon SNS console. Once logged in, navigate to the Topics section via the left navigation pane and click Create topic.
A FIFO (First-In-First-Out) topic is set to be created by default, but you can select Standard for standard messaging needs. In the Details section of the form, provide a name for your topic. In this case, we’ll use “ExampleTopic”.
After filling out the necessary information, scroll to the bottom and click on Create topic. You will then be directed to the details page of your newly created topic.
The next step involves creating a subscription to the topic you just created. Go back to the left navigation pane and select Subscriptions. Click on Create subscription to proceed to the next page and select the Topic ARN (Amazon Resource Name) field to display a list of available topics in your account.
Choose the relevant topic (i.e., ExampleTopic). Set the protocol as Email and input an email address capable of receiving notifications. After these details are configured, click Create subscription.
You must check your email for a confirmation message from AWS Notifications, typically sent from no-reply@sns.amazonaws.com. Click on Confirm subscription in the email, which will open a web browser displaying a confirmation of your subscription with your subscription ID.
Finally, to publish a message to your topic, navigate back to the Topics page using the left navigation pane. Select your topic and click on Publish message. This action brings up the Publish message to topic page. Optionally, you can enter a Subject for your message, such as “This message was sent from Amazon SNS!”
In the Message body section, select Identical payload for all delivery protocols and fill in the message body. For example, the message might say: “Publish a message to my SNS topic.” Once the message details are filled, click Publish message.
This will send your message to the topic, and a confirmation page will open, indicating the message has been published. Check your email inbox to verify if you have received the message from Amazon SNS with the details of the published message.
These best practices can help you make the most of Simple Notification Service.
When naming topics in AWS SNS, adopt a systematic approach that reflects the application’s structure and usage context. Consistency in naming helps easier management and reduces confusion, especially when operating at scale.
Names should be descriptive and potentially include project names, environment (dev, test, prod), and the nature of the messages (e.g., alerts, events). Using delimiters like hyphens or underscores can improve readability and organization. Avoid using sensitive information in topic names, such as customer identifiers or secret keys.
AWS CloudWatch integrates seamlessly with SNS to provide metrics such as the number of messages published, delivery attempts, and failures, which are vital for performance tracking and alerting on operational issues. Setting up CloudWatch alarms for unusual activity or errors can preemptively address issues before they impact the system.
Logs should be maintained for all message transactions, including timestamps, publisher and subscriber data, and message IDs. AWS CloudTrail can log API calls, helping track changes to the SNS resources and ensure compliance with governance and auditing requirements.
Error handling helps maintain the integrity of message delivery in SNS. Configure retry policies and dead-letter queues (DLQs) to manage how undeliverable messages are retried and handled. Setting up a DLQ helps capture messages that cannot be delivered after several attempts, allowing developers to analyze and rectify the issues.
It’s important to tailor retry strategies based on messages’ criticality and subscriber endpoints’ characteristics. For example, exponential backoff strategies can effectively handle temporary issues with subscriber endpoints without overwhelming them with repeated attempts.
While AWS SNS supports large message payloads up to 256KB, it is recommended to keep message sizes smaller whenever possible to reduce delivery latency and costs. Large messages may require publishing multiple API calls, incurring higher charges.
For messages nearing the size limit, consider compressing the data or using a reference-based messaging pattern, where the message contains a reference to the payload stored in an Amazon S3 bucket rather than the payload itself. When designing messages, include only necessary data and choose structured formats like JSON to optimize parsing and handling by the subscribers.
Using AWS Identity and Access Management (IAM) policies, you can define who can publish messages to a topic or subscribe to it. Policies should be as restrictive as possible, following the principle of least privilege.
Encrypting messages in transit using HTTPS and at rest using AWS Key Management Service (KMS) ensures that sensitive data is protected against unauthorized access. Regular audits of permissions and access policies help maintain a secure SNS environment, preventing unauthorized access and data breaches.
Lumigo is a cloud native observability and troubleshooting tool. Lumigo automatically enriches traces with complete in-context request and response payloads and correlates them to the appropriate logs and metrics. This unified view of all troubleshooting data enables users to solve cloud native issues 80% faster than similar tools. With Lumigo, users can:
Get started with a free trial of Lumigo for your microservice applications
