# AWS.SimpleQueueService.NonExistentQueue: The specified queue does not exist

AWS error fixes · Updated 17 November 2026

**Short answer:** SQS could not find a queue with that name or URL in the account and Region the request went to. Check the Region your client uses against the one in the queue URL, the exact name (case and the .fifo suffix matter), and whether the queue belongs to another account; a queue deleted in the last minute also returns this.

## What it looks like

```
An error occurred (AWS.SimpleQueueService.NonExistentQueue) when calling the
GetQueueUrl operation: The specified queue does not exist.
```

Newer SDK versions talk to SQS over its JSON protocol and report the same condition with the error code `QueueDoesNotExist`, so code that catches only one of the two names can miss it. Both mean the same thing. The queue URL itself encodes the account and Region, for example `https://sqs.eu-west-2.amazonaws.com/123456789012/orders`, which makes most cases quick to diagnose.

## Causes, most common first

1. **Region mismatch.** The client is configured for one Region and the queue lives in another. A Lambda function defaults to its own Region.
2. **Name mismatch.** Queue names are case-sensitive, and FIFO queues must include the `.fifo` suffix in every call.
3. **Another account.** `GetQueueUrl` by name searches your own account unless you pass the owner's account ID. Calls into another account's queue without permission can also come back as "does not exist" rather than access denied.
4. **Recently deleted or recreated.** Deletion takes up to 60 seconds, and you must wait about that long before creating a queue with the same name.
5. **Stale configuration.** An environment variable, event source mapping or SNS subscription still points at a queue that was renamed or torn down with an old stack.

## Diagnose

List queues with the name prefix in the Region you expect:

```
aws sqs list-queues --queue-name-prefix orders --region eu-west-2
```

Resolve the URL for an exact name, including another account's queue:

```
aws sqs get-queue-url --queue-name orders-events.fifo \
  --queue-owner-aws-account-id 210987654321 --region eu-west-2
```

Check the queue really exists and read its ARN:

```
aws sqs get-queue-attributes \
  --queue-url https://sqs.eu-west-2.amazonaws.com/123456789012/orders \
  --attribute-names QueueArn CreatedTimestamp
```

Compare the Region in the URL with the Region your code's client uses. Log both at start-up; it saves a lot of guessing.

## Fix it

- **Construct the client in the queue's Region**, or derive the Region from the queue URL when queues live in several Regions.
- **Inject the queue URL** from infrastructure code (a stack output, environment variable or SSM parameter) rather than building it from a hard-coded name.
- **Cross-account queues**: grant access in the queue policy for the calling principal (for example `sqs:SendMessage` and `sqs:GetQueueUrl`), and use the full queue URL.
- **After deleting a queue**, wait at least a minute before recreating it with the same name, and redeploy anything that cached the old URL.
- **Lambda triggers**: an event source mapping pointing at a deleted queue will not recover by itself; recreate it against the new queue.

## Mistakes to avoid

- Catching the error and silently dropping messages. A producer that cannot find its queue should fail loudly; messages that are never sent never reach a dead-letter queue either.
- Creating queues implicitly on first use in application code. It hides typos and spreads queues across Regions.
- Confusing this with an empty queue. A queue that exists but has no messages returns an empty receive, not an error; check depth with [how to check SQS queue depth](https://cloudconsole.dev/how-to/check-sqs-queue-depth).

## Questions

### Why does SQS say the queue does not exist when I can see it in the console?

The console is probably showing a different Region or account from the one your code uses, or the name differs in case or the .fifo suffix.

### What is the difference between NonExistentQueue and QueueDoesNotExist?

They are the same condition. Older query-protocol responses use AWS.SimpleQueueService.NonExistentQueue; SDKs using the JSON protocol report QueueDoesNotExist.

### How long after deleting an SQS queue can I recreate it?

Wait at least 60 seconds after deletion before creating a queue with the same name.

## When this happens away from your desk

A producer that cannot find its queue drops work silently unless something alarms on it. CloudConsole, a phone app for AWS, is built to show queue metrics and error alarms on your phone, so a queue that stops receiving messages stands out.

[About the CloudConsole app](https://cloudconsole.dev/aws-console-app) · [Download on the App Store](https://apps.apple.com/app/cloudconsole-for-aws/id6835419710)

## Sources

- [Amazon SQS Developer Guide](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/)
- [GetQueueUrl API reference](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/API_GetQueueUrl.html)

## Related

- [aws sqs get-queue-attributes](https://cloudconsole.dev/cli/sqs-get-queue-attributes)
- [aws sqs send-message](https://cloudconsole.dev/cli/sqs-send-message)
- [aws sqs receive-message](https://cloudconsole.dev/cli/sqs-receive-message)
- [How to check SQS queue size](https://cloudconsole.dev/how-to/check-sqs-queue-depth)
- [ResourceNotFoundException: Requested resource not found (DynamoDB)](https://cloudconsole.dev/errors/dynamodb-resourcenotfound)
- [How to change the AWS default Region](https://cloudconsole.dev/how-to/change-default-aws-region)
- [The request must contain the parameter MessageGroupId](https://cloudconsole.dev/errors/sqs-messagegroupid-required)

---

Source: https://cloudconsole.dev/errors/sqs-nonexistentqueue

CloudConsole is an independent iPhone and Android app for Amazon Web Services by Cloudconcur Ltd. It is not affiliated with Amazon Web Services.
