AWS SQS

Pushes a message payload into any SQS standard or FIFO queue with optional message attributes and deduplication IDs.

Sends up to 10 messages in a single API call, slashing request overhead when your agent has a burst of events to dispatch.

Polls an SQS queue for up to 10 messages in a single long-poll call, returning message body, attributes, and receipt handles needed for deletion.

Permanently removes a processed message from the queue using its receipt handle, confirming successful consumption.

Deletes up to 10 messages in one API call using their receipt handles, ideal for high-throughput consumer loops.

Extends or shortens a message's visibility timeout so in-flight processing has more (or less) time before the message becomes re-available.

Deletes all messages currently in a queue in under 60 seconds — useful for resetting a test queue or clearing a backlog caused by a bad deploy.

Provisions a new SQS standard or FIFO queue with configurable visibility timeout, retention period, and encryption settings.

Permanently removes an SQS queue and all its messages — use after confirming all consumers are drained.

Retrieves metadata for a queue including approximate message count, DLQ configuration, and encryption settings.

Updates an existing queue's configuration — visibility timeout, message retention, policy, or redrive policy — without re-creating the queue.

Resolves a queue's full HTTPS endpoint URL by name and optional owner account ID, needed before any message operation.

Returns the URLs of all queues in the account and region, optionally filtered by name prefix.

Returns all queues configured to send their failed messages to a specific dead-letter queue.

Applies cost-allocation, environment, or ownership tags to an SQS queue for billing breakdowns and resource governance.

Grants a principal (AWS account, IAM role, or service) the right to send, receive, or delete messages on a queue via its resource policy.

Fires when one or more messages arrive in a monitored SQS queue, delivering the message body and attributes for immediate downstream processing.

Fires via CloudWatch alarm when the ApproximateNumberOfMessages metric on a queue exceeds a configured threshold, signalling a consumer lag.

Fires when a message lands in a dead-letter queue after exhausting its maxReceiveCount retries, indicating a persistent processing failure.

Fires when a message's visibility timeout expires without deletion, making it re-available and indicating the consumer failed or stalled mid-processing.

Fires via CloudTrail event when a new SQS queue is provisioned in the account, enabling automated governance and tagging workflows.

Fires via CloudTrail event when an SQS queue is deleted, triggering audits or dependent resource clean-up.

Fires when a message fails all consumer retry attempts and cannot be delivered, often surfaced through CloudWatch Logs or DLQ depth metrics.