queue

Author: sommeeeer

pages/aws/config/overrides/queue.mdx

@@ -7,7 +7,7 @@ If you want to better understand how to implement your own Queue, the easiest wa
 
 Couple of things to note :
 - The default implementation use an SQS queue. This has the main advantage of being able to control the concurrency of the revalidations as well as avoiding trigerring the revalidation multiple times for the same route.
-- You don't have to use a queue at all. You could trigger the revalidation directly in the Queue override itself. You can see a very simple implementation of this [in the `queue` override](/aws/contribute/local_run#devqueuets).
+- You don't have to use a queue at all. You could trigger the revalidation directly in the Queue override itself. You can see a very simple implementation of this [in the `direct` override](https://github.com/opennextjs/opennextjs-aws/blob/main/packages/open-next/src/overrides/queue/direct.ts).
 
 ## Included Queue
 
@@ -18,7 +18,7 @@ It uses the `@aws-sdk/client-sqs` to interact with SQS.
 
 #### Requirements
 
-- You need to provide the `QUEUE_URL` environment variable to your server.
+- You need to provide the `REVALIDATION_QUEUE_URL` environment variable to your server.
 
 ### sqs-lite
 
@@ -27,7 +27,7 @@ This implementation is a lighter version of the `sqs` Queue as it uses `aws4fetc
 
 #### Requirements
 
-- You need to provide the `QUEUE_URL`, `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY` and `AWS_SESSION_TOKEN` environment variables to your server.
+- You need to provide the `REVALIDATION_QUEUE_URL`, `REVALIDATION_QUEUE_REGION`(will fallback to `us-east-1`), `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY` and `AWS_SESSION_TOKEN` environment variables to your server.
 
 ### direct