AWS SQS
Collect event message bodies directly from SQS with a queue-scoped identity
Collect events whose payload is the SQS message body. Use S3 via SQS when messages announce S3 objects instead. Direct SQS uses Vector's aws_sqs source and does not download objects.
Setup
You need source_configs:create (and credentials:use to attach a credential) and a published parser for the log source the queue feeds. Review the pull permissions matrix before granting access.
1. Prepare the queue and identity
Use an SQS queue containing the event bodies your parser accepts. Give nano a dedicated queue so another consumer does not take its events.
Grant the identity Vector reads with sqs:ReceiveMessage, sqs:DeleteMessage, sqs:ChangeMessageVisibility, and sqs:GetQueueAttributes on that one queue. For SSE-KMS, also grant kms:Decrypt on the key, restricted by kms:ViaService to sqs.REGION.amazonaws.com, and allow the identity in the key policy. Direct SQS needs no s3:GetObject grant.
The identity is either an access key you store in nano, or the deployment's ambient identity (EC2 instance profile, EKS IRSA or ECS task role) when you attach no credential. Either can assume a role in another account.
2. Add the pull source
Open Ingestion → Log Sources → Cloud pull. If you use an access key, add it under Credentials first. Then choose Add cloud pull, pick AWS SQS, and enter:
| Field | Value |
|---|---|
| SQS Queue URL | The full queue URL, e.g. https://sqs.us-east-1.amazonaws.com/123456789012/nano-events |
| AWS Region | The queue's Region |
| Credential | Your AWS credential, or none for the ambient identity |
| Poll interval, Client concurrency, Visibility timeout | Leave the defaults unless you need to tune throughput |
Route it to your log source (Single source type), or add body-based routing rules, then Deploy it.
Verify
Send a new event body to the queue, then search the log source:
metadata.log_source="your_source" | head 20Replace your_source with the log source you routed to. Check the producer and parser if the source is deployed but Search is empty.
Streams and fields
One pull source binds one queue. Vector exposes the message body as message; SQS message attributes are not exposed for routing, so route by fields inside the body. Map the event fields with your parser.
Troubleshoot
Need help with these checks? Contact support with the deployment, request ID and time with timezone.
Access denied in Vector logs
Check the four queue actions, the KMS key policy, explicit denies, and that the queue URL and Region match. If you assume a role, check its trust policy.
Events arrive in another consumer
Check whether another application reads this queue. Create a dedicated queue and configure the producer to deliver a copy to it.
Routing or parsing fails
Check the message body against your deployed parser. A rule matching SQS message attributes cannot work because the transport does not expose them. An S3 notification needs the S3 via SQS path.