Amazon SNS vs SuprSend

Amazon SNS

IAM and topic policies limit a credential to single actions and topics, a read-only managed policy exists, and CloudTrail can log each publish. Standard topics take no idempotency token, so a retried Publish can send twice. SNS has no user preferences, digests or in-app channel, email is plain text to confirmed subscribers, and SMS starts in a sandbox.

SuprSend

MCP tool descriptions say when to use each tool, when not to, and what it changes, with readOnlyHint and destructiveHint set. No rate-limit page or 429 guidance.

Amazon SNS

1. Sign requests with SigV4 for service sns at sns.<region>.amazonaws.com, or call aws sns publish --topic-arn <arn> --message <text> from the AWS CLI
2. Track MessageId yourself on standard topics, because a retried Publish sends again. Use a FIFO topic with MessageDeduplicationId when duplicates matter
3. Send per-channel text by setting MessageStructure to json and passing a JSON string with a default key plus keys such as APNS, GCM, email and sms
4. Check GetSMSSandboxAccountStatus and the monthly spend quota before texting. Sandbox sends reach only verified numbers
5. Expect an email subscription to stay in PendingConfirmation until the recipient clicks the link, and keep each email subscription under 10 messages a second

SuprSend

1. Pass an idempotency key on each trigger. It holds for 24 hours
2. Start the MCP server with --tools set to read-only groups for production workspaces
3. Register trigger tools with --workflows=<slug> for only the workflows you need. The default registers none
4. Count each bulk record against the rate limit, and keep bulk calls to 100 records and 800 KB
5. Treat management API responses as secrets. They include the workspace secret in plain text