> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/system-settings/data-sources/connection-settings/nosql/redis.md).

# Redis

### Connecting to Redis <a href="#connecting-to-redis" id="connecting-to-redis"></a>

Set the Server connection property to the name or address of the server your Redis instance is running on.

If your Redis server is running on a port other than the default (6379), you can specify your port in the Port property.

### Authenticating to Redis <a href="#authenticating-to-redis" id="authenticating-to-redis"></a>

The provider supports Password and ACL authentication. Connections to Redis instances that aren't password protected are supported as well.

#### No Authentication <a href="#no-authentication" id="no-authentication"></a>

Set the AuthScheme property to None. This indicates the Redis instance is not password protected (using the requirepass directive in the configuration file).

#### Password <a href="#password" id="password"></a>

Set the AuthScheme property to Password and set the Password property to the password used to authenticate with a password protected Redis instance using the Redis AUTH command.

#### ACL (Access Control List) <a href="#acl-access-control-list" id="acl-access-control-list"></a>

Set the following to connect:

* AuthScheme: Set this to ACL.
* User: Set this to the username you use to authenticate with Redis ACL.
* Password: Set this to the password you use to authenticate with Redis ACL.

### Securing Redis Connections <a href="#securing-redis-connections" id="securing-redis-connections"></a>

You can set UseSSL to negotiate SSL/TLS encryption when you connect.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/system-settings/data-sources/connection-settings/nosql/redis.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.