> For the complete documentation index, see [llms.txt](https://docs.taskforce.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taskforce.sh/getting-started/direct-redis-connection.md).

# Direct Redis Connection

## Direct Redis connection

Connecting to an existing Redis instance that is running in a publicly opened server is straightforward, just create a new connection in the left side panel clicking on the + symbol:

![](/files/-MGsXTXNAQSfWViEIwcl)

{% hint style="danger" %}
It is crucial that your existing Redis instance is configured with the setting **maxmemory: noeviction** for Bull/BullMQ to work without issues. <https://redis.io/topics/lru-cache>
{% endhint %}

You can now fill the connection details. We **highly** recommend you to use TLS for encrypted communication with your database, please refer to your provider on how to activate it if it is not activated already, normally the TLS enabled connection will be available in a different port than the standard unencrypted connection:

![Dialog for configuring a connection to a redis server](/files/-MGsY8ecSumlcaEQReNo)

{% hint style="info" %}
The Redis passwords are always stored encrypted using highly secure cryptographic standards.
{% endhint %}

#### Securing by IP

If you have a Redis connection hosted somewhere, one important security practice is to limit which I&#x50;**'**&#x73; are allowed to connect to your instance. Taskforce.sh will connect to your instances using the IP:

**18.193.189.120**

So you will need to configure your Redis service to allow the IP above so that Taskforce.sh can access the queues on your instance.