-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Redis docs #10693
Add Redis docs #10693
Changes from all commits
533a92f
50374ec
3bbb5bd
d0fb641
c674ff9
3e1a4b9
4633f40
2e51a0f
870b018
101f9cc
781d9ad
e1d05f6
80117ee
03d5c31
4dcc90c
dc57790
d0f3b82
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -192,3 +192,34 @@ keep the Password field empty: | |
![DataGrip connection options](../../../img/database-access/guides/sqlserver/[email protected]) | ||
|
||
Click OK to connect. | ||
|
||
## Redis Insight | ||
|
||
<Admonition type="note"> | ||
Teleport's Redis Insight integration only supports Redis standalone instances. | ||
</Admonition> | ||
|
||
After opening Redis Insight click `ADD REDIS DATABASE`. | ||
|
||
![Redis Insight Startup Screen](../../../img/database-access/guides/redis/redisinsight-startup.png) | ||
|
||
Log in to your Redis instance with a Redis user first by using: | ||
|
||
`tsh db login --db-user=alice redis-db-name`. | ||
|
||
Click `Add Database Manually`. Use `127.0.0.1` as the `Host` and port printed by `tsh proxy db` as described [here](#get-connection-information). | ||
|
||
Provide your Redis username as `Username` and password as `Password`. | ||
|
||
![Redis Insight Configuration](../../../img/database-access/guides/redis/redisinsight-add-config.png) | ||
|
||
Next, check the `Use TLS` and `Verify TLS Certificates` boxes and copy the CA certificate returned by `tsh proxy db`. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We should include the instructions to copy the certificate when we first tell the reader to run There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes,
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That's helpful, thanks. To make this clearer, I think we should replace line 210 with something like the following (removing the code fence escapes): Run the following command to start the Database Access proxy for your
Redis instance.
\`\`\`code
$ tsh proxy db redis
Started DB proxy on 127.0.0.1:51823
Use following credentials to connect to the redis proxy:
ca_file=path/to/example.com.pem
cert_file=path/to/example.com/redis-x509.pem
key_file=path/to/example.com/bob
\`\`\`
In Redis Insight, click `Add Database Manually`. Use `127.0.0.1` as the
`Host`. Copy the port printed by `tsh proxy db` and use it for the
`Port` field. |
||
Copy the private key and certificate to corresponding fields. | ||
|
||
Click `Add Redis Database`. | ||
|
||
![Redis Insight TLS Configuration](../../../img/database-access/guides/redis/redisinsight-tls-config.png) | ||
|
||
Congratulations! You have just connected to your Redis instance. | ||
|
||
![Redis Insight Connected](../../../img/database-access/guides/redis/redisinsight-connected.png) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: Maybe move this above SQL Server section? To keep it grouped with other self-hosted guides and also move the preview SQL Server to the bottom.