aws-sqs
Work with Amazon SQS for reliable message queuing. Create standard and FIFO queues, configure dead-letter queues for failed messages, send and receive messages in batches, and build decoupled event-driven architectures.
What this skill does
# AWS SQS
Amazon Simple Queue Service (SQS) is a fully managed message queuing service for decoupling microservices. It offers two queue types: Standard (best-effort ordering, at-least-once delivery) and FIFO (exactly-once, ordered).
## Core Concepts
- **Standard Queue** — unlimited throughput, at-least-once delivery, best-effort ordering
- **FIFO Queue** — exactly-once processing, strict ordering, 3000 msg/s with batching
- **Visibility Timeout** — period a message is hidden after being received
- **Dead-Letter Queue (DLQ)** — destination for messages that fail processing
- **Message Group ID** — FIFO ordering key for parallel processing within a queue
- **Long Polling** — reduces empty responses and API costs
## Creating Queues
```bash
# Create a standard queue
aws sqs create-queue \
--queue-name order-processing \
--attributes '{
"VisibilityTimeout": "60",
"MessageRetentionPeriod": "1209600",
"ReceiveMessageWaitTimeSeconds": "20"
}'
```
```bash
# Create a FIFO queue (name must end in .fifo)
aws sqs create-queue \
--queue-name order-processing.fifo \
--attributes '{
"FifoQueue": "true",
"ContentBasedDeduplication": "true",
"VisibilityTimeout": "60"
}'
```
## Dead-Letter Queues
```bash
# Create the DLQ first
aws sqs create-queue --queue-name order-processing-dlq
# Get DLQ ARN
DLQ_ARN=$(aws sqs get-queue-attributes \
--queue-url https://sqs.us-east-1.amazonaws.com/123456789/order-processing-dlq \
--attribute-names QueueArn --query 'Attributes.QueueArn' --output text)
# Configure main queue to use DLQ after 3 failed attempts
aws sqs set-queue-attributes \
--queue-url https://sqs.us-east-1.amazonaws.com/123456789/order-processing \
--attributes '{
"RedrivePolicy": "{\"deadLetterTargetArn\":\"'$DLQ_ARN'\",\"maxReceiveCount\":\"3\"}"
}'
```
```bash
# Redrive messages from DLQ back to source queue
aws sqs start-message-move-task \
--source-arn "$DLQ_ARN" \
--destination-arn "arn:aws:sqs:us-east-1:123456789:order-processing"
```
## Sending Messages
```bash
# Send a single message
aws sqs send-message \
--queue-url https://sqs.us-east-1.amazonaws.com/123456789/order-processing \
--message-body '{"orderId":"12345","action":"process"}' \
--message-attributes '{
"OrderType": {"DataType":"String","StringValue":"premium"}
}'
```
```bash
# Send to FIFO queue with group ID
aws sqs send-message \
--queue-url https://sqs.us-east-1.amazonaws.com/123456789/order-processing.fifo \
--message-body '{"orderId":"12345","action":"process"}' \
--message-group-id "customer-789" \
--message-deduplication-id "order-12345-v1"
```
## Batch Operations
```bash
# Send up to 10 messages in a batch
aws sqs send-message-batch \
--queue-url https://sqs.us-east-1.amazonaws.com/123456789/order-processing \
--entries '[
{"Id":"1","MessageBody":"{\"orderId\":\"001\"}"},
{"Id":"2","MessageBody":"{\"orderId\":\"002\"}"},
{"Id":"3","MessageBody":"{\"orderId\":\"003\"}"}
]'
```
```python
# Batch consumer with boto3
import boto3
import json
sqs = boto3.client('sqs')
QUEUE_URL = 'https://sqs.us-east-1.amazonaws.com/123456789/order-processing'
def poll_and_process():
while True:
response = sqs.receive_message(
QueueUrl=QUEUE_URL,
MaxNumberOfMessages=10, # batch up to 10
WaitTimeSeconds=20, # long polling
MessageAttributeNames=['All']
)
messages = response.get('Messages', [])
if not messages:
continue
entries_to_delete = []
for msg in messages:
try:
body = json.loads(msg['Body'])
process_order(body)
entries_to_delete.append({
'Id': msg['MessageId'],
'ReceiptHandle': msg['ReceiptHandle']
})
except Exception as e:
print(f"Failed: {e}")
# Message returns to queue after visibility timeout
if entries_to_delete:
sqs.delete_message_batch(
QueueUrl=QUEUE_URL,
Entries=entries_to_delete
)
```
## Receiving and Deleting
```bash
# Receive messages with long polling
aws sqs receive-message \
--queue-url https://sqs.us-east-1.amazonaws.com/123456789/order-processing \
--max-number-of-messages 5 \
--wait-time-seconds 20 \
--message-attribute-names All
```
```bash
# Delete a processed message
aws sqs delete-message \
--queue-url https://sqs.us-east-1.amazonaws.com/123456789/order-processing \
--receipt-handle "AQEBzL..."
```
```bash
# Change visibility timeout for a message needing more processing time
aws sqs change-message-visibility \
--queue-url https://sqs.us-east-1.amazonaws.com/123456789/order-processing \
--receipt-handle "AQEBzL..." \
--visibility-timeout 120
```
## Monitoring
```bash
# Check queue depth
aws sqs get-queue-attributes \
--queue-url https://sqs.us-east-1.amazonaws.com/123456789/order-processing \
--attribute-names ApproximateNumberOfMessages,ApproximateNumberOfMessagesNotVisible,ApproximateNumberOfMessagesDelayed
```
```bash
# Purge all messages (use with caution)
aws sqs purge-queue \
--queue-url https://sqs.us-east-1.amazonaws.com/123456789/order-processing
```
## Best Practices
- Always enable long polling (WaitTimeSeconds=20) to reduce costs
- Set up dead-letter queues on every queue to catch poison messages
- Use FIFO queues only when ordering matters — standard queues have much higher throughput
- Process and delete messages in batches for efficiency
- Set visibility timeout to 6x your average processing time
- Use message group IDs in FIFO queues for parallel ordered processing
- Monitor `ApproximateNumberOfMessages` and alert on queue depth spikes
- Implement idempotent consumers — messages may be delivered more than once
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.