aws
messaging_error
ai_generated
true
SNS delivery to endpoint failed: Endpoint is disabled or does not exist
ID: aws/aws-sns-delivery-failed
83%Fix Rate
85%Confidence
60Evidence
2023-01-01First Seen
Version Compatibility
| Version | Status | Introduced | Deprecated | Notes |
|---|---|---|---|---|
| 2 | active | — | — | — |
Root Cause
SNS message delivery to a subscription endpoint failed due to disabled endpoint, permission issues, or endpoint errors.
genericWorkarounds
-
88% success Enable delivery status logging to identify the specific failure reason
Configure delivery status logging in SNS topic attributes, then check CloudWatch Logs for delivery failure details
Sources: https://docs.aws.amazon.com/sns/latest/dg/sns-topic-attributes.html
-
85% success Re-enable disabled endpoints or resubscribe for platforms like SQS, Lambda, HTTP
aws sns set-subscription-attributes or delete/recreate the subscription for the failing endpoint
Sources: https://docs.aws.amazon.com/sns/latest/dg/sns-troubleshooting.html
Dead Ends
Common approaches that don't work:
-
Republish the same message repeatedly to a disabled endpoint
95% fail
Disabled endpoints reject all messages; republishing without re-enabling won't help
-
Delete and recreate the SNS topic to fix delivery issues
80% fail
Recreating the topic loses all subscriptions and requires reconfiguring all subscribers
Error Chain
Preceded by: