Argo Events SNS Quick Fix - AWS SNS Event Source

Argo Events SNS event source subscribes to AWS SNS topic notifications. Misconfigured topic subscriptions or IAM roles prevent message delivery. This guide covers the fix.

Quick Fix

Wrong

sns:
  example:
    topicArn: arn:aws:sns:us-east-1:123456789012:my-topic
    region: us-east-1

The issue: missing accessKey/secretKey for AWS authentication, no endpoint for the SNS HTTP subscription, and no filterPolicy for message filtering.

Right

sns:
  example:
    topicArn: arn:aws:sns:us-east-1:123456789012:my-topic
    region: us-east-1
    endpoint: http://eventsource-svc:12000/sns
    accessKey:
      key: accesskey
      name: aws-secrets
    secretKey:
      key: secretkey
      name: aws-secrets
    filterPolicy:
      event:
      - created
      - updated

# Expected output after applying the fix
# SNS subscription created for my-topic
# Endpoint: eventsource-svc:12000/sns
# Filter policy: only event=created or event=updated
# Messages delivered to event source

Prevention

• Always configure AWS credentials via Kubernetes secrets
• Set the endpoint URL where SNS delivers notifications
• Use filterPolicy to reduce message volume
• Confirm subscription with AWS SNS console
• Test subscription with SNS publish from AWS CLI

DodaTech Tools

Doda Browser's SNS subscription manager shows active subscriptions and message rates. DodaZIP archives SNS configurations for disaster recovery. Durga Antivirus Pro validates SNS topic policies.

FAQ