# Using with Vapor

To replace the default SQS-Lambda integration with Workerless in your Vapor-powered application, you need to update the environment variables to add, or adjust, the SQS_QUEUE variable:



You should follow this naming convention strictly. This queue is created by default for every Vapor environment. Since we're going to disable queue consumption in Vapor, we have to set this variable manually. Otherwise, dispatching to this queue will start throwing exceptions.

Next, you need to disable queues inside your vapor.yml file:


id: 1
name: myapp
        queues: false
        queue-concurrency: 30
        queue-memory: 512
        queue-timeout: 120

Once these changes are performed, deploy your environment.

After the deployment is done, your application will still dispatch jobs normally to the default queue or any queue you created via Vapor. However, it will not be processing any jobs. For that, you need to run Workerless.

Refer to the installation guide for more information on how to run Workerless.


To avoid delaying consumption for too long, make sure Workerless is ready to run as soon as the Vapor deployment is done.