Amazon SNS Topic
Does ZopNight manage Amazon SNS Topic?
Amazon SNS bills per million publish requests plus a delivery charge that varies by protocol: SQS and Lambda deliveries are free, HTTP carries a per-million rate, and SMS is priced per message. ZopNight tracks 90 days of SNS topic metrics and records messages published per topic; its idle-topic rule (RC-182) stays silent, since a topic with no publishes costs nothing.
Rules that fire on Amazon SNS Topic
At a glance
| Field | Value |
|---|---|
| Scheduling notes | discovery, metrics, and cost tracking only; no SNS recommendation fires today. |
Amazon Simple Notification Service (SNS) delivers pub/sub messages to subscribers, billed per publish and per delivery by protocol. Topics with defunct subscriptions or high-volume fan-out patterns can accumulate meaningful delivery charges.
Publishes in, deliveries out, priced by protocol
SNS meters two things. Publishes bill per million requests, with payloads over 64 KB metered in 64 KB chunks. Deliveries then bill by protocol, and the spread is enormous: delivery to SQS queues and Lambda functions is free, HTTP endpoints and email carry their own per-message rates, and SMS is priced per message at rates that vary by destination country, routinely the largest SNS line item by orders of magnitude. A topic with 5 subscribers turns one publish into five metered deliveries, so fan-out multiplies cost by subscription count and protocol mix.
Waste shapes
Topics with zero publishes for months are hygiene debt rather than direct cost, since an idle topic bills nothing, but they anchor stale subscriptions and confuse audits, so they are worth a manual cleanup pass; ZopNight’s idle-topic rule (RC-182) never fires on them. The real money problems: defunct HTTP subscriptions retrying against dead endpoints, SMS fan-out that nobody has audited since it was wired up, and high-volume topics delivering to paid protocols where an SQS or Lambda subscriber would carry the same traffic for free.
Topic-level tracking
Topics are discovered on the 6-hour cycle. Hourly CloudWatch metrics from the SNS namespace (messages published) run with a 90-day lookback, and per-topic cost comes from Cost Explorer or CUR 2.0. No SNS recommendation fires today. Nothing stops or schedules here: since an idle topic bills nothing, all cost work happens on the subscription list and the protocol choices.
Subscription lists in the console
SNS console, then Topics, then a topic’s Subscriptions tab. The subscription list is where dead endpoints hide. Every entry there is a delivery meter attached to each future publish.