SQS
Install
See the Install guide for the full setup, including Windows PowerShell.
curl -fsSL https://install.skippr.io/install.sh | shClick to copyConsumes messages from an Amazon SQS queue.
Configuration
yaml
source:
kind: sqs
queue_url: "https://sqs.us-east-1.amazonaws.com/123456/my-queue"
region: us-east-1| Field | Default | Description |
|---|---|---|
queue_url | (required) | SQS queue URL |
region | AWS region | |
endpoint_url | Custom endpoint | |
mode | Consumption mode such as stream or batch |
CLI
bash
skippr connect source sqs \
--queue-url https://sqs.us-east-1.amazonaws.com/123/my-queue \
--region us-east-1 \
--endpoint-url http://localhost:4566 \
--mode stream| Flag | Description |
|---|---|
--queue-url | SQS queue URL |
--region | AWS region |
--endpoint-url | Custom SQS endpoint URL |
--mode | Consumption mode |
Authentication
Authentication uses the AWS default credential chain.
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY- IAM roles, instance profiles, or task roles
- AWS SSO or shared config profiles
Permissions or Network Requirements
The AWS principal needs sqs:ReceiveMessage, sqs:DeleteMessage, and sqs:GetQueueAttributes on the selected queue. The runner must also be able to reach the SQS endpoint in the configured region.
Troubleshooting
| Symptom | Fix |
|---|---|
| AccessDenied or queue errors | Verify the AWS credential chain, queue URL, region, and SQS permissions. |
| no messages arriving | Check that producers are sending to the expected queue and that the queue is not empty. |
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