SNS

Install

See the Install guide for the full setup, including Windows PowerShell.

curl -fsSL https://install.skippr.io/install.sh | shClick to copy

Consumes AWS SNS messages via an SQS subscription.

Configuration

source:
  kind: sns
  topic_arn: "arn:aws:sns:us-east-1:123456:my-topic"
  sqs_queue_url: "https://sqs.us-east-1.amazonaws.com/123456/my-sns-queue"
  region: us-east-1

Field	Default	Description
topic_arn	(required)	SNS topic ARN
sqs_queue_url	(required)	SQS queue URL subscribed to the topic
region		AWS region
endpoint_url		Custom endpoint

Namespace: sns.{topic_name}

CLI

skippr connect source sns \
  --topic-arn arn:aws:sns:us-east-1:123:my-topic \
  --sqs-queue-url https://sqs.us-east-1.amazonaws.com/123/sns-queue \
  --region us-east-1 \
  --endpoint-url http://localhost:4566

Flag	Description
--topic-arn	SNS topic ARN
--sqs-queue-url	SQS queue URL subscribed to the topic
--region	AWS region
--endpoint-url	Custom SNS endpoint URL

Authentication

Authentication uses the AWS default credential chain.

• AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY
• IAM roles, instance profiles, or task roles
• AWS SSO or shared config profiles

Permissions or Network Requirements

The AWS principal needs access to the subscribed SQS queue, and the SNS topic must already deliver messages into that queue. The runner must also be able to reach the AWS APIs for the configured region.

Troubleshooting

Symptom	Fix
no messages arriving	Verify the SNS topic is subscribed to the target SQS queue and that the queue policy allows delivery.
AccessDenied	Check the AWS credential chain and access to the queue and topic resources.

Next steps

• Pair this source with a destination from Destination Connectors.
• See How It Works for the end-to-end pipeline flow.

Install

See the Install guide for the full setup, including Windows PowerShell.

curl -fsSL https://install.skippr.io/install.sh | shClick to copy