AWS SQS: The specified queue does not exist or you do not have access to it
SQS gives the same answer whether the queue is missing or you lack permission, so you cannot tell which from the message. Most often the queue exists in another region or account from the one the client is using. Or the code built a URL from the queue name instead of calling GetQueueUrl. A queue deleted in the last 60 seconds cannot be recreated yet either.
Quick fix
Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.
# Which account and region is the client using?
aws sts get-caller-identity
aws configure get region
# Does the queue exist there?
aws sqs get-queue-url --queue-name orders --region eu-west-2
aws sqs list-queues --queue-name-prefix orders --region eu-west-2
# Cross account: pass the owner's account ID
aws sqs get-queue-url --queue-name orders --queue-owner-aws-account-id 111122223333
# Then check the queue policy and IAM allow sqs:SendMessage etc.
aws sqs get-queue-attributes --queue-url "$URL" --attribute-names PolicyHow to diagnose MessageQueue errors
Queue errors are usually about the balance between producers and consumers. Growing lag means consumers cannot keep up. Endless rebalancing usually means consumers are being evicted for exceeding a poll or heartbeat interval, not that the cluster is unhealthy. A poison message, one that always fails processing, will block an ordered partition forever unless there is a dead-letter path, which is why a DLQ is not optional in production.
If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.
- Measure lag over time, not once:
kafka-consumer-groups --describe --group <g>. The trend distinguishes a throughput problem from a stuck consumer. - For repeated rebalancing, compare processing time per batch against
max.poll.interval.ms. Slow processing looks exactly like a dead consumer to the coordinator. - Always configure a dead-letter queue with a bounded retry count. Without one, a single malformed message stops the partition indefinitely.
- Check message size against the broker limit before assuming a network failure: SQS caps at 256 KB, Kafka at
message.max.bytes. - Verify consumer ACLs and topic authorisation separately from connectivity; an authorisation failure often surfaces as a metadata error.
Tools worth reaching for
kafka-consumer-groupsrabbitmqctl list_queuesaws sqs get-queue-attributeskafkacat / kcatflower (Celery)
Authoritative references
Primary documentation for this error, worth reading before applying any fix in production.
Related MessageQueue errors
- AWS SQS: Message too large (256KB limit)The SQS message body exceeds the 256KB maximum size limit.
- Celery: Received unregistered task of type 'myapp.tasks.send_email'The worker took a message off the queue but has never imported the module that defines the…
- Celery: WorkerLostErrorA Celery worker process died unexpectedly during task execution, often due to OOM kill…
- Connection to node -1 could not be established. Broker may not be available.Node -1 is the bootstrap server, so the client could not even make its first connection. If…
- Kafka: LEADER_NOT_AVAILABLEPartition has no elected leader. Broker down, ISR empty, or topic just created and metadata…
- Kafka: Offset out of rangeConsumer trying to read from offset that doesn't exist. Data retention deleted old messages.
- Kafka: RecordTooLargeExceptionA message exceeded a size limit. Three separate limits must agree: the producer's…
- Kafka: The coordinator is not available (COORDINATOR_NOT_AVAILABLE)Consumer groups and transactions need the internal __consumer_offsets topic, and the broker…
Browse other categories
- HTTP 494xx client errors, 5xx server errors, redirects, headers and protocol problems.
- JavaScript 42npm resolution, async pitfalls, hydration, memory limits and runtime type…
- Database 41Connections, deadlocks, constraints, replication and memory limits.
- AI 35Rate limits, context windows, GPU memory and model-serving failures.
- Network 35Refused connections, timeouts, resets, MTU problems and port exhaustion.
- Python 35Imports, virtual environments, encoding, concurrency and dependency conflicts.
- Kubernetes 34CrashLoopBackOff, ImagePullBackOff, OOMKilled, RBAC, scheduling and storage.
- Docker 27Daemon connectivity, disk space, image pulls, ports and architecture mismatches.
- System 26Disk space, systemd units, file descriptors, OOM killer and scheduled jobs.
- Cloud 25IAM permissions, quotas, service limits and credential failures.
- Security 25JWT validation, CSRF, OAuth grants, SELinux, SSH host keys and CSP.
- TLS 24Untrusted authorities, expiry, hostname mismatch, chains and cipher negotiation.
Something missing or wrong?
This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.