Amazon SNS pricing explained
SNS bills $0.50 per million publish requests after the first million each month, plus a delivery charge that depends on the protocol: deliveries to SQS and Lambda are free, HTTP/HTTPS endpoints cost $0.60 per million after 100,000 free, and email costs $2.00 per 100,000 after 1,000 free, in us-east-1 at the time of writing. SMS and mobile push are priced separately.
Pricing dimensions (standard topics)
| Dimension | Free each month | Price after that |
|---|---|---|
| Publish and other API requests | 1 million | $0.50 per million |
| Deliveries to SQS | Free | |
| Deliveries to Lambda | Free | |
| Deliveries to HTTP/HTTPS | 100,000 | $0.06 per 100,000 |
| Deliveries to email / email-JSON | 1,000 | $2.00 per 100,000 |
| Deliveries to Data Firehose | — | $0.19 per million |
From the AWS Price List API at the time of writing. Each 64 KB chunk of a published message counts as one request. SMS prices vary by destination country and carrier; FIFO topics have their own per-request and per-GB prices.
Worked examples
1. Fan-out to three queues. 10 million events published to a topic with three SQS subscribers: (10 − 1) × $0.50 = $4.50 for SNS; the 30 million deliveries cost nothing on the SNS side, but each queue bills its own receives and deletes.
2. Webhooks. 5 million messages delivered to one HTTPS endpoint: publishes (5 − 1) × $0.50 = $2.00 plus deliveries 4,900,000 × $0.0000006 = $2.94, $4.94.
3. Email notifications. 200,000 email deliveries: (200,000 − 1,000) × $0.00002 = $3.98. Email is for people, not systems: it is the most expensive protocol per delivery.
Batching publishes
PublishBatch sends up to 10 messages in one API call, and the batch is billed by its total payload in 64 KB chunks rather than per message. Publishing 10 million small messages in batches of 10 takes 1 million requests, which the free tier covers, against (10 − 1) × $0.50 = $4.50 when each message is published on its own. The saving is small in dollars but scales with volume, and fewer API calls also means less throttling at peak.
Filtering and delivery behaviour
Subscription filter policies stop unwanted deliveries, and messages filtered out are not billed as deliveries. Payload-based filtering, however, is charged per GB of payload scanned. Retries to a failing HTTP endpoint follow the delivery policy, and each attempt is a billed delivery.
Charges people miss
- SMS: per-message prices vary widely by country and can dwarf everything else; set a monthly SMS spend limit.
- CloudWatch alarm actions to SNS are cheap, but email subscriptions for noisy alarms add up across many recipients.
- KMS-encrypted topics call KMS on publish, billed by KMS.
- Delivery status logging writes to CloudWatch Logs, billed per GB.
Seeing SNS cost
In Cost Explorer under Simple Notification Service, group by Usage type: Requests-Tier1 is publishes, DeliveryAttempts-HTTP, DeliveryAttempts-SMTP and DeliveryAttempts-SQS are deliveries by protocol. The NumberOfNotificationsDelivered metric per topic shows volume.
Questions
How much does SNS cost per message?
Publishing is $0.50 per million requests after 1 million free. Delivery adds nothing for SQS and Lambda, $0.60 per million for HTTP/HTTPS and $2.00 per 100,000 for email, in us-east-1 at the time of writing.
Is SNS to SQS free?
The delivery from SNS to SQS is free. You still pay for the publish request and for the SQS requests that consume the message.
How much does SNS email cost?
The first 1,000 email notifications a month are free, then $2.00 per 100,000.
How much does SNS SMS cost?
It depends on the destination country and message type; check the SNS SMS pricing page for current rates.
SNS is how most CloudWatch alarms reach people today. CloudConsole is being built to show those alarms on a phone with the context around them.
About the app → · Download on the App Store