From 5a5f91abdc82b06a4ef2649cf7337658f9b476f3 Mon Sep 17 00:00:00 2001
From: adisht <36517802+adisht@users.noreply.github.com>
Date: Mon, 19 Jul 2021 00:24:50 +0300
Subject: [PATCH 01/23] Support for SWIFT was removed a while ago (#1455)
* Support for SWIFT was removed a while ago
Support for SWIFT was removed a while ago
* Support for SWIFT was removed a while ago
Support for SWIFT was removed a while ago
* Support for SWIFT was removed a while ago
Support for SWIFT was removed a while ago
---
content/embeds/backup-locations.md | 14 --------------
.../administering/import-export/database-backup.md | 1 -
.../administering/import-export/exporting-data.md | 1 -
3 files changed, 16 deletions(-)
diff --git a/content/embeds/backup-locations.md b/content/embeds/backup-locations.md
index a719aaadb1e..f56137c798e 100644
--- a/content/embeds/backup-locations.md
+++ b/content/embeds/backup-locations.md
@@ -71,20 +71,6 @@ To backup to a local mount point for a node:
For example: `/mnt/Public`
-### OpenStack Swift
-
-{{< note >}}
-Support for OpenStack Object Storage ("Swift") for backup, import and export location ends on November 30, 2020.
-{{< /note >}}
-
-Before you choose to backup to OpenStack Swift, make sure that you have:
-
-- Storage URL in the format: `https:///v1`
-- Container
-- Prefix (Optional)
-- User
-- Key
-
### Azure Blob Storage
Before you choose to backup to Azure Blob Storage, make sure that you have:
diff --git a/content/rs/administering/import-export/database-backup.md b/content/rs/administering/import-export/database-backup.md
index 8d8b2431790..78a9649f427 100644
--- a/content/rs/administering/import-export/database-backup.md
+++ b/content/rs/administering/import-export/database-backup.md
@@ -17,7 +17,6 @@ You can schedule backups to these locations:
- SFTP server
- Amazon S3
- Local mount point
-- OpenStack Swift (Object Storage)
- Azure Blob Storage
- Google Cloud Storage
diff --git a/content/rs/administering/import-export/exporting-data.md b/content/rs/administering/import-export/exporting-data.md
index 767c958ded9..d2ba80e1020 100644
--- a/content/rs/administering/import-export/exporting-data.md
+++ b/content/rs/administering/import-export/exporting-data.md
@@ -17,7 +17,6 @@ You can export a database to these locations:
- SFTP server
- Amazon AWS S3
- Local mount point
-- OpenStack Swift (Object Storage)
- Azure Blob Storage
- Google Cloud Storage
From 9bf63137ac5cc6fab4555b388261a0d153d8bcdd Mon Sep 17 00:00:00 2001
From: adisht <36517802+adisht@users.noreply.github.com>
Date: Mon, 19 Jul 2021 00:26:18 +0300
Subject: [PATCH 02/23] Consolidate 2 consecutive notes (#1456)
Consolidate 2 consecutive notes
---
.../rs/installing-upgrading/customize-install-directories.md | 3 ---
1 file changed, 3 deletions(-)
diff --git a/content/rs/installing-upgrading/customize-install-directories.md b/content/rs/installing-upgrading/customize-install-directories.md
index 897456eb199..adbabc247e5 100644
--- a/content/rs/installing-upgrading/customize-install-directories.md
+++ b/content/rs/installing-upgrading/customize-install-directories.md
@@ -17,9 +17,6 @@ The files are installed in the `redislabs` directory located in the path that yo
- When you install with custom directories, the installation does not run as an RPM file.
- If a `redislabs` directory already exists in the path that you specify, the installation fails.
- All nodes in a cluster must be installed with the same file locations.
-{{< /note >}}
-
-{{< note >}}
- Custom installation directories are not supported for databases using Redis on Flash.
{{< /note >}}
From 1fca28efa7de55d60cc6d4f34426efc061d22125 Mon Sep 17 00:00:00 2001
From: adisht <36517802+adisht@users.noreply.github.com>
Date: Tue, 20 Jul 2021 15:49:30 +0300
Subject: [PATCH 03/23] Correct a typo (#1458)
Correct a typo
---
content/modules/add-module-to-cluster.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/modules/add-module-to-cluster.md b/content/modules/add-module-to-cluster.md
index decc4729102..86b659dfbc7 100644
--- a/content/modules/add-module-to-cluster.md
+++ b/content/modules/add-module-to-cluster.md
@@ -95,7 +95,7 @@ To add a module package to the cluster using the admin console:
## Upgrading the module for the database
-After you add and updated module to the cluster, go to the configuration of the databases that use the module.
+After you add an updated module to the cluster, go to the configuration of the databases that use the module.
The database configuration shows that a new version of the module is available for the database.
![update_available-1](/images/rs/update_available.png?width=1346&height=1600)
From 0b6d5133d025119f0e05086bd7a485f9135e4c9e Mon Sep 17 00:00:00 2001
From: Yoni <57891224+yorozen@users.noreply.github.com>
Date: Wed, 21 Jul 2021 15:49:09 +0300
Subject: [PATCH 04/23] Update client_ioredis.md (#1461)
The readFileSync syntax is wrong
should be without the encoding=
---
content/rs/references/client_references/client_ioredis.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/rs/references/client_references/client_ioredis.md b/content/rs/references/client_references/client_ioredis.md
index 80cab728939..92256ae2f52 100644
--- a/content/rs/references/client_references/client_ioredis.md
+++ b/content/rs/references/client_references/client_ioredis.md
@@ -52,9 +52,9 @@ const redis = new Redis({
host: 'hostname',
port: ,
tls: {
- key: fs.readFileSync('path_to_keyfile', encoding='ascii'),
- cert: fs.readFileSync('path_to_certfile', encoding='ascii'),
- ca: [ fs.readFileSync('path_to_ca_certfile', encoding='ascii') ]
+ key: fs.readFileSync('path_to_keyfile', 'ascii'),
+ cert: fs.readFileSync('path_to_certfile', 'ascii'),
+ ca: [ fs.readFileSync('path_to_ca_certfile', 'ascii') ]
}
});
```
From e8d71949e916d3962c6aeac75f48d146398f49f5 Mon Sep 17 00:00:00 2001
From: WonkyWumpus
Date: Wed, 21 Jul 2021 09:46:26 -0700
Subject: [PATCH 05/23] Update _index.md (#1462)
Unless I am mistaken, you cannot add users or manage roles and permissions through the API. At least not in the AWS version of Redis Enterprise Cloud.
---
content/rc/api/_index.md | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/content/rc/api/_index.md b/content/rc/api/_index.md
index 1daeb706a97..d899923fbac 100644
--- a/content/rc/api/_index.md
+++ b/content/rc/api/_index.md
@@ -13,11 +13,9 @@ aliases: /rv/api/
The [Redis Enterprise Cloud REST API](https://api.redislabs.com/v1/swagger-ui.html) helps you manage your Redis Cloud subscription programmatically.
You can use the API to:
-
-- Add or update users
+
- Create or manage databases
-- Define or change hosting credentials
-- Define or manage roles and permissions
+- Define or change hosting credentials
- Audit access via logs
- Backup or import databases
From 09e581e2e8b7eb5bb4cc4f946782df533d498046 Mon Sep 17 00:00:00 2001
From: Lance Leonard
Date: Wed, 21 Jul 2021 11:39:34 -0700
Subject: [PATCH 06/23] Initial draft (#1459)
---
content/platforms/faqs/_index.md | 76 +++++++++-----------------------
1 file changed, 22 insertions(+), 54 deletions(-)
diff --git a/content/platforms/faqs/_index.md b/content/platforms/faqs/_index.md
index b5fb81ffb14..7367ec6c720 100644
--- a/content/platforms/faqs/_index.md
+++ b/content/platforms/faqs/_index.md
@@ -1,5 +1,6 @@
---
-Title: FAQs
+Title: Redis Enterprise on Kubernetes FAQs
+linkTitle: FAQs
description:
weight: 100
alwaysopen: false
@@ -7,24 +8,22 @@ categories: ["Platforms"]
---
Here are some frequently asked questions about Redis Enterprise on integration platforms.
-## RS on Kubernetes
+## What is an Operator?
-{{< expand-control >}}
-{{% expand "What is an Operator?" %}}
An Operator is a [Kubernetes custom controller]( https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources#custom-controllers) which extends the native K8s API. Refer to the article [Redis Enterprise K8s Operator-based deployments – Overview]({{< relref "/platforms/kubernetes/concepts/operator.md" >}}).
-{{% /expand %}}
-{{% expand "Does Redis Enterprise Operator support multiple clusters per namespace?" %}}
+## Does Redis Enterprise Operator support multiple clusters per namespace?
+
The Redis Enterprise Operator may only deploy a single Redis Enterprise Cluster per namespace. Each Redis Enterprise Cluster can run multiple databases while maintaining high capacity and performance.
-{{% /expand %}}
-{{% expand "Do I need to deploy a Redis Enterprise Operator per namespace?" %}}
+## Do I need to deploy a Redis Enterprise Operator per namespace?
+
Yes, one Operator per namespace, each managing a single Redis Enterprise Cluster.
Each Redis Enterprise Cluster can run multiple databases while maintaining high capacity and performance.
-{{% /expand %}}
-{{% expand "How can I see the CRDs (Custom Resource Definitions) created for my cluster?" %}}
+## How can I see the Custom Resource Definitions (CRDs) created for my cluster?
+
Run the following:
```sh
@@ -32,9 +31,8 @@ kubectl get rec
kubectl describe rec my-cluster-name
```
-{{% /expand %}}
+## How can I change the cluster admin user password?
-{{% expand "How can I change the cluster admin user password?" %}}
The cluster admin user password is created by the Operator during the deployment of the Redis Enterprise cluster and is stored in a Kubernetes secret.
{{< warning >}}
@@ -44,9 +42,8 @@ Changing the admin password impacts the proper operation of the K8s deployment.
If you must use a different admin password, create an additional user with admin privileges and configure with the new password.
-{{% /expand %}}
+## How is using Redis Enterprise Operator superior to using Helm Charts?
-{{% expand "How is using Redis Enterprise Operator superior to using Helm Charts?" %}}
While Helm Charts help automate multi-resource deployments, they do not provide the lifecycle management and lack many of the benefits provided by the Operator:
- Operators are a K8s standards while Helm is a proprietary tool
@@ -54,25 +51,25 @@ While Helm Charts help automate multi-resource deployments, they do not provide
- Operators allow full control over the Redis Enterprise Cluster lifecycle
- We’ve experienced difficulties managing state and lifecycle of the application through Helm as it essentially only allows to determine the resources being deployed, which is a problem when upgrading and evolve the Redis Enterprise Cluster settings
- Operators support advanced flows which would otherwise require using an additional 3rd party
-{{% /expand %}}
-{{% expand "How to connect to the Redis Enterprise Cluster UI?" %}}
-Create a port forwarding rule to expose the cluster UI port. For example, when the default port 8443 is used, run:
+## How to connect to the Redis Enterprise Cluster user interface
+
+Create a port forwarding rule to expose the cluster user interface (UI) port. For example, when the default port 8443 is used, run:
```sh
kubectl port-forward –namespace service/-cluster-ui 8443:8443
```
Connect to the UI by pointing your browser to `https://localhost:8443`
-{{% /expand %}}
-{{% expand "How should I size Redis Enterprise Cluster nodes?" %}}
+## How should I size Redis Enterprise Cluster nodes?
+
For nodes hosting the Redis Enterprise Cluster statefulSet pods, please follow the guidelines provided for Redis Enterprise in the [hardware requirements]({{< relref "/rs/administering/designing-production/hardware-requirements.md" >}}).
For additional information please also refer to [Kubernetes Operator Deployment – Persistent Volumes]({{< relref "/platforms/kubernetes/concepts/persistent-volumes.md" >}}).
-{{% /expand %}}
-{{% expand "How to retrieve the username/password for a Redis Enterprise Cluster?" %}}
+## How to retrieve the username/password for a Redis Enterprise Cluster?
+
The Redis Enterprise Cluster stores the username/password of the UI in a K8s secret.
To retrieve, first, find the secret by retrieving secrets and locating one of type Opaque with a name identical or containing your Redis Enterprise Cluster name.
@@ -99,49 +96,27 @@ A possible response may look like this:
```yaml
apiVersion: v1
-
data:
-
password: Q2h5N1BBY28=
-
username: cmVkaXNsYWJzLnNi
-
kind: Secret
-
metadata:
-
creationTimestamp: 2018-09-03T14:06:39Z
-
labels:
-
app: redis-enterprise
-
redis.io/cluster: test
-
name: redis-enterprise-cluster
-
namespace: redis
-
ownerReferences:
-
– apiVersion: app.redislabs.com/v1alpha1
-
blockOwnerDeletion: true
-
controller: true
-
kind: RedisEnterpriseCluster
-
name: test
-
uid: 8b247469-c715-11e8-a5d5-0a778671fc2e
-
resourceVersion: “911969”
-
selfLink: /api/v1/namespaces/redis/secrets/redis-enterprise-cluster
-
uid: 8c4ff52e-c715-11e8-80f5-02cc4fca9682
-
type: Opaque
```
@@ -156,9 +131,8 @@ Do not change the default admin user password in the Redis Enterprise admin cons
Changing the admin password impacts the proper operation of the K8s deployment.
{{< /warning >}}
-{{% /expand %}}
+## How to retrieve the username/password for a Redis Enterprise Cluster through the OpenShift Console?
-{{% expand "How to retrieve the username/password for a Redis Enterprise Cluster through the OpenShift Console?" %}}
To retrieve your password, navigate to the OpenShift management console, select your project name, go to Resources->Secrets->your_cluster_name
Retrieve your password by selecting “Reveal Secret.”
@@ -169,11 +143,9 @@ Do not change the default admin user password in the Redis Enterprise admin cons
Changing the admin password impacts the proper operation of the K8s deployment.
{{< /warning >}}
-{{% /expand %}}
+## What capabilities, privileges and permissions are defined by the Security Context Constraint (SCC) yaml and the Pod Security Policy (PSP) yaml?
-{{% expand "What capabilities, privileges and permissions are defined by the Security Context Constraint (SCC) yaml and the Pod Security Policy (PSP) yaml?" %}}
-
-The scc.yaml file is defined like this:
+The `scc.yaml` file is defined like this:
```yaml
kind: SecurityContextConstraints
@@ -195,7 +167,7 @@ seLinuxContext:
([latest version on GitHub](https://raw.githubusercontent.com/RedisLabs/redis-enterprise-k8s-docs/master/scc.yaml))
-The psp.yaml file is defined like this:
+The `psp.yaml` file is defined like this:
```yaml
apiVersion: extensions/v1beta1
@@ -241,7 +213,3 @@ and allows that account to create pods with the PSP shown above.
- The NET_RAW capability requirement in PSP was removed.
- The allowPrivilegeEscalation is set to 'false' by default.
{{< /note >}}
-
-{{% /expand %}}
-
-{{< /expand-control >}}
From 3adbe92cbd678c60179653abe9447322db0f0f68 Mon Sep 17 00:00:00 2001
From: Lance Leonard
Date: Wed, 21 Jul 2021 11:39:59 -0700
Subject: [PATCH 07/23] Initial set of updates. (#1460)
---
.../import-export/exporting-data.md | 4 ++--
content/rs/concepts/_index.md | 3 ++-
content/rs/installing-upgrading/_index.md | 16 +++++++++-------
.../installing-upgrading/configuring/_index.md | 4 ++--
.../configuring/centos-rhel-7-firewall.md | 2 +-
...nfiguring-aws-route53-dns-redis-enterprise.md | 2 +-
.../rs/installing-upgrading/file-locations.md | 2 +-
.../installing-upgrading/supported-platforms.md | 2 +-
content/rs/installing-upgrading/uninstalling.md | 2 +-
content/rs/installing-upgrading/upgrading.md | 2 +-
content/rs/technology-behind-redis-enterprise.md | 5 +++--
11 files changed, 24 insertions(+), 20 deletions(-)
diff --git a/content/rs/administering/import-export/exporting-data.md b/content/rs/administering/import-export/exporting-data.md
index d2ba80e1020..0ba7e04e15c 100644
--- a/content/rs/administering/import-export/exporting-data.md
+++ b/content/rs/administering/import-export/exporting-data.md
@@ -20,7 +20,7 @@ You can export a database to these locations:
- Azure Blob Storage
- Google Cloud Storage
-{{comment}}The backup process creates compressed (.gz) RDB files that you can [import into a database]({{< relref "/rs/administering/import-export/importing-data.md" >}}).
+{{}}The backup process creates compressed (.gz) RDB files that you can [import into a database]({{< relref "/rs/administering/import-export/importing-data.md" >}}).
If you backup a database configured for database clustering,
RS copies a backup file for each shard to the specified backup location.
@@ -28,7 +28,7 @@ RS copies a backup file for each shard to the specified backup location.
Make sure that you have enough space available in your storage location.
If there is not enough space in the backup location, the backup fails.
{{< /note >}}
-{{/comment}}
+{{}}
## Export data from a database
diff --git a/content/rs/concepts/_index.md b/content/rs/concepts/_index.md
index d342888bf02..d92fd3860b7 100644
--- a/content/rs/concepts/_index.md
+++ b/content/rs/concepts/_index.md
@@ -1,5 +1,6 @@
---
-Title: Concepts and Architecture
+Title: Concepts and architecture
+linkTitle: Concepts and architecture
description:
weight: 40
alwaysopen: false
diff --git a/content/rs/installing-upgrading/_index.md b/content/rs/installing-upgrading/_index.md
index ec303fc6040..d84ec229649 100644
--- a/content/rs/installing-upgrading/_index.md
+++ b/content/rs/installing-upgrading/_index.md
@@ -1,5 +1,6 @@
---
-Title: Install and Setup
+Title: Install and setup
+linkTitle: Install and setup
description:
weight: 35
alwaysopen: false
@@ -180,6 +181,12 @@ To install without answering the installation questions, either:
For geo-distributed Active-Active replication, create an [Active-Active]({{< relref "/rs/administering/creating-databases/create-active-active.md" >}}) database.
+## Notes
+
+- Redis Enterprise Software installation creates the `redislabs:redislabs` user and group. Assigning other users to the `redislabs` group is optional. Users belonging to the `redislabs` group will have permission to read and execute (e.g. use the `rladmin` status command) but not to write or delete files and directories.
+
+- Redis Enterprise Software serves a large variety of industries. The common industry standard for permissions is `750` permissions. Reducing the permissions to `700` has not been tested and isn't supported.
+
## More info and options
If you've already installed Redis Enterprise Software, you can also:
@@ -191,7 +198,7 @@ If you've already installed Redis Enterprise Software, you can also:
More info is available to help with customization and related questions:
- [AWS EC2 configuration]({{}})
-- [CentOS/RHEL Firewall conifugration]({{< relref "rs/installing-upgrading/configuring/centos-rhel-7-firewall.md" >}})
+- [CentOS/RHEL Firewall configuration]({{< relref "rs/installing-upgrading/configuring/centos-rhel-7-firewall.md" >}})
- [Change socket file location]({{< relref "rs/installing-upgrading/configuring/change-location-socket-files.md" >}})
- [Cluster DNS configuration]({{< relref "rs/installing-upgrading/configuring/cluster-dns.md" >}})
- [Cluster load balancer setup]({{< relref "rs/installing-upgrading/configuring/cluster-lba-setup.md" >}})
@@ -210,8 +217,3 @@ Now that your cluster is set up with nodes, you can:
- [Add users]({{< relref "/rs/security/passwords-users-roles.md" >}}) to the cluster with specific permissions. To begin, start with [Authentication and authorization]({{< relref "/rs/security/admin-console-security/user-security" >}}).
- [Create databases]({{< relref "/rs/administering/creating-databases/_index.md" >}}) to use with your applications.
-## Additional notes
-
-Redis Enterprise installation creates the redislabs:redislabs user and group. Assigning other users to the redislabs group is optional. Users belonging to the redislabs group will have permission to read and execute (e.g. use the rladmin status command) but not to write or delete files and directories.
-
-Redis Enterprise serves a large variety of industries. The common industry standard for permissions is 750 permissions. Reducing the permissions to 700 has not been tested and isn't supported.
diff --git a/content/rs/installing-upgrading/configuring/_index.md b/content/rs/installing-upgrading/configuring/_index.md
index bd52f51355b..403957c7616 100644
--- a/content/rs/installing-upgrading/configuring/_index.md
+++ b/content/rs/installing-upgrading/configuring/_index.md
@@ -1,11 +1,11 @@
---
-Title: Additional Configuration
+Title: Additional configuration
description:
weight: 80
alwaysopen: false
categories: ["RS"]
aliases: /rs/administering/installing-upgrading/configuring/
---
-This section contains instructions for additional configuration of your OS and Redis Enterprise Software installation.
+This section describes additional configuration options for Redis Enterprise Software installation.
{{< allchildren style="h2" description="true" />}}
diff --git a/content/rs/installing-upgrading/configuring/centos-rhel-7-firewall.md b/content/rs/installing-upgrading/configuring/centos-rhel-7-firewall.md
index aa343e3ec01..3c03bbf846d 100644
--- a/content/rs/installing-upgrading/configuring/centos-rhel-7-firewall.md
+++ b/content/rs/installing-upgrading/configuring/centos-rhel-7-firewall.md
@@ -1,6 +1,6 @@
---
title: Configure CentOS/RHEL 7 Firewall
-linkTitle: CentOS/RHEL 7 Firewall
+linkTitle: CentOS/RHEL 7 firewall
description:
weight: $weight
alwaysopen: false
diff --git a/content/rs/installing-upgrading/configuring/configuring-aws-route53-dns-redis-enterprise.md b/content/rs/installing-upgrading/configuring/configuring-aws-route53-dns-redis-enterprise.md
index 47df7d09944..736516c7d37 100644
--- a/content/rs/installing-upgrading/configuring/configuring-aws-route53-dns-redis-enterprise.md
+++ b/content/rs/installing-upgrading/configuring/configuring-aws-route53-dns-redis-enterprise.md
@@ -1,5 +1,5 @@
---
-Title: Configuring AWS Route53 DNS Management
+Title: AWS Route53 DNS management
linkTitle: AWS Route 53 DNS
description:
weight: $weight
diff --git a/content/rs/installing-upgrading/file-locations.md b/content/rs/installing-upgrading/file-locations.md
index 83eb1b0db06..99bc883097e 100644
--- a/content/rs/installing-upgrading/file-locations.md
+++ b/content/rs/installing-upgrading/file-locations.md
@@ -1,5 +1,5 @@
---
-Title: File Locations
+Title: File locations
description:
weight: 20
alwaysopen: false
diff --git a/content/rs/installing-upgrading/supported-platforms.md b/content/rs/installing-upgrading/supported-platforms.md
index 9c2a9bebb33..bba57d1c709 100644
--- a/content/rs/installing-upgrading/supported-platforms.md
+++ b/content/rs/installing-upgrading/supported-platforms.md
@@ -1,5 +1,5 @@
---
-Title: Supported Platforms
+Title: Supported platforms
description:
weight: 10
alwaysopen: false
diff --git a/content/rs/installing-upgrading/uninstalling.md b/content/rs/installing-upgrading/uninstalling.md
index 63499d3e29b..03fd3d25b2e 100644
--- a/content/rs/installing-upgrading/uninstalling.md
+++ b/content/rs/installing-upgrading/uninstalling.md
@@ -1,6 +1,6 @@
---
Title: Uninstall Redis Enterprise Software
-LinkTitle: Uninstall Redis Enterprise Software
+LinkTitle: Uninstall existing deployment
description:
weight: 70
alwaysopen: false
diff --git a/content/rs/installing-upgrading/upgrading.md b/content/rs/installing-upgrading/upgrading.md
index afbd6914bc2..860f9e8ec5d 100644
--- a/content/rs/installing-upgrading/upgrading.md
+++ b/content/rs/installing-upgrading/upgrading.md
@@ -1,6 +1,6 @@
---
Title: Upgrade Redis Enterprise Software
-linkTitle: Upgrade Redis Enterprise Software
+linkTitle: Upgrade existing deployment
description:
weight: 60
alwaysopen: false
diff --git a/content/rs/technology-behind-redis-enterprise.md b/content/rs/technology-behind-redis-enterprise.md
index 2812f82d878..05b8e3a3d5f 100644
--- a/content/rs/technology-behind-redis-enterprise.md
+++ b/content/rs/technology-behind-redis-enterprise.md
@@ -1,12 +1,13 @@
---
-Title: Redis Enterprise Technical Overview
+Title: Redis Enterprise Software technical overview
+linkTitle: Technical overview
description:
weight: 10
alwaysopen: false
categories: ["RS"]
---
-Redis Enterprise is designed to simplify operations while providing seamless scalability, top performance, and high availability.
+Redis Enterprise Software is designed to simplify operations while providing seamless scalability, top performance, and high availability.
Here are some of the features and design decisions that make this possible.
From 4397e2477815d813f9719bba62a86be1ff4e2880 Mon Sep 17 00:00:00 2001
From: Amiram Mizne
Date: Thu, 22 Jul 2021 07:43:40 -0700
Subject: [PATCH 08/23] Fixed an error in EKS supported version (#1463)
We've certified on 1.18; 1.19 was written in error.
---
content/platforms/release-notes/k8s-6-0-20-12-2021-07.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/platforms/release-notes/k8s-6-0-20-12-2021-07.md b/content/platforms/release-notes/k8s-6-0-20-12-2021-07.md
index 87461335008..69f02898b59 100644
--- a/content/platforms/release-notes/k8s-6-0-20-12-2021-07.md
+++ b/content/platforms/release-notes/k8s-6-0-20-12-2021-07.md
@@ -120,7 +120,7 @@ is required, the only fix is to upgrade the K8s cluster to a newer version.
## Compatibility Notes
-* EKS is now supported (K8s 1.19)
+* EKS is now supported (K8s 1.18)
* OpenShift 4.4 (previously deprecated) is no longer supported
* GKE K8s versions 1.15, 1.16 (previously deprecated) is no longer supported
* VMWare TKGIE 1.10 (K8s 1.19) is now supported
@@ -129,4 +129,4 @@ is required, the only fix is to upgrade the K8s cluster to a newer version.
* GKE K8s version 1.17 (no longer supported by Google) is deprecated
* kOps 1.15 is deprecated
-* VMWare TKGIE 1.7 (K8s 1.16), VMWare TKGIE 1.8 (K8s 1.17) are deprecated (no longer supported by VMWare)
\ No newline at end of file
+* VMWare TKGIE 1.7 (K8s 1.16), VMWare TKGIE 1.8 (K8s 1.17) are deprecated (no longer supported by VMWare)
From 266765c0c196b607e4f8fc0c2c61950a7b44c149 Mon Sep 17 00:00:00 2001
From: Lance Leonard
Date: Fri, 23 Jul 2021 12:00:57 -0700
Subject: [PATCH 09/23] Initial draft (#1465)
---
content/rs/administering/database-operations/_index.md | 6 +++---
content/rs/security/_index.md | 4 +++-
2 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/content/rs/administering/database-operations/_index.md b/content/rs/administering/database-operations/_index.md
index 8a4d995a404..2edb8ec3dca 100644
--- a/content/rs/administering/database-operations/_index.md
+++ b/content/rs/administering/database-operations/_index.md
@@ -5,11 +5,11 @@ weight: 60
alwaysopen: false
categories: ["RS"]
---
-This section contains all you need to know to maintain Redis Enterprise Software (RS) databases.
+This section helps you maintain your Redis Enterprise Software databases.
Your data is critical to your business and securing is one of your top priorities. This section shows how you can secure access to your data and secure your data in transit.
Your data is critical to your business and securing it is one of your top priorities. Here's where to learn how to secure access to your data and secure your data in transit.
{{< allchildren style="h2" description="true" />}}
diff --git a/content/rs/security/_index.md b/content/rs/security/_index.md
index 6cbc21d04ee..33703d3c55b 100644
--- a/content/rs/security/_index.md
+++ b/content/rs/security/_index.md
@@ -4,7 +4,9 @@ description:
weight: 60
alwaysopen: false
categories: ["RS"]
-aliases: ["/rs/administering/designing-production/security/"]
+aliases: /rs/administering/designing-production/security/
+ /rs/security/database-security/
+ /rs/security/database-security.md
---
Security is an important part of any production system. This section describes the security features and settings available in Redis Enterprise.
From 897672c4c661be3c1a559f5641ea64b9557f0b89 Mon Sep 17 00:00:00 2001
From: Jamie Scott
Date: Thu, 29 Jul 2021 05:20:25 -0700
Subject: [PATCH 10/23] Small fix (#1468)
back from the dead - also this is ugly. Miss you guys.
---
content/rs/references/crdb-cli-reference.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/rs/references/crdb-cli-reference.md b/content/rs/references/crdb-cli-reference.md
index 21cc3fdd759..56a27506eae 100644
--- a/content/rs/references/crdb-cli-reference.md
+++ b/content/rs/references/crdb-cli-reference.md
@@ -89,7 +89,7 @@ Task 2b3d62c6-395b-4679-87b1-eef006ad4a38 created
---> Status changed: started -> finished
```
-If you only specify the required fields, the properties of the database are::
+If you only specify the required fields, the properties of the database are:
- Compression level 3
- Causal consistency is off
From 05493adb65ab6c18941dd3e2d3be6a486a03a15a Mon Sep 17 00:00:00 2001
From: Alon Magrafta <50071256+AlonMagrafta@users.noreply.github.com>
Date: Thu, 29 Jul 2021 15:22:42 +0300
Subject: [PATCH 11/23] can add module only on creation (#1469)
* can add module only on creation
* Update add-module-to-database.md
---
content/modules/add-module-to-database.md | 4 +++-
content/rs/administering/creating-databases/_index.md | 7 ++++++-
2 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/content/modules/add-module-to-database.md b/content/modules/add-module-to-database.md
index 9ca68198dd3..a11694420ad 100644
--- a/content/modules/add-module-to-database.md
+++ b/content/modules/add-module-to-database.md
@@ -14,11 +14,13 @@ aliases:
Modules add additional functionality to your databases for specific use cases.
You can add modules to the database when you create the database.
-## Add modules to a database
+## Create a database with a module
{{< note >}}
- Before you add a module to a database,
we recommend that you [upgrade the module]({{< relref "/modules/add-module-to-cluster.md" >}}) to the latest version.
+- Modules can be add to database only when creating a new database.
+ You can't add a module to an existing database.
- After you add a module to the database,
certain database fields for the database are disabled according to the supported capabilities of the module.
{{< /note >}}
diff --git a/content/rs/administering/creating-databases/_index.md b/content/rs/administering/creating-databases/_index.md
index e058069ad9e..2869254324d 100644
--- a/content/rs/administering/creating-databases/_index.md
+++ b/content/rs/administering/creating-databases/_index.md
@@ -78,7 +78,12 @@ for this database. Minimum RAM portion is 10%, and maximum RAM portion is 50%.
- [**Redis Modules**]({{< relref "/rs/developing/modules/_index.md" >}}) - When you create a new in-memory database,
you can enable multiple Redis modules to the database.
For RoF databases, you can add modules that support RoF.
-
+
+ {{< note >}}
+ Modules can be add to database only when creating a new database.
+ You can't add a module to an existing database.
+ {{< /note >}}
+
To add a module to the database:
1. In the Redis Modules field, click ![Add](/images/rs/icon_add.png#no-click "Add").
From 8e27e28e15e4372a401faea9b472e0f648385360 Mon Sep 17 00:00:00 2001
From: Rachel Elledge <86307637+rrelledge@users.noreply.github.com>
Date: Thu, 29 Jul 2021 09:14:03 -0500
Subject: [PATCH 12/23] Cleaned up RS clients index page and added an
auto-generating table shortcode (#1467)
---
.../rs/references/client_references/_index.md | 12 ++++--
.../references/client_references/client_c.md | 3 +-
.../client_references/client_csharp.md | 3 +-
.../client_references/client_drupal.md | 3 +-
.../client_references/client_ioredis.md | 3 +-
.../client_references/client_java.md | 3 +-
.../client_references/client_nodejs.md | 3 +-
.../client_references/client_php.md | 3 +-
.../client_references/client_python.md | 3 +-
.../client_references/client_ruby.md | 3 +-
layouts/shortcodes/table-children.html | 40 +++++++++++++++++++
11 files changed, 67 insertions(+), 12 deletions(-)
create mode 100644 layouts/shortcodes/table-children.html
diff --git a/content/rs/references/client_references/_index.md b/content/rs/references/client_references/_index.md
index 77886e37268..11bb716dc8b 100644
--- a/content/rs/references/client_references/_index.md
+++ b/content/rs/references/client_references/_index.md
@@ -1,9 +1,15 @@
---
-Title: Developing with Redis Clients
-description:
+Title: Develop with Redis clients
+linkTitle: Redis clients
+description: Redis client libraries allow you to connect to Redis instances from within your application. This section provides an overview of several recommended Redis clients for popular programming and scripting languages.
weight: 80
alwaysopen: false
categories: ["RS"]
---
+To connect to Redis instances from within your application, use a Redis client library that matches your application's language.
-{{< allchildren style="h2" description="true" />}}
+The [Redis Clients page](https://redis.io/clients) contains a list of available Redis client libraries for a variety of popular programming and scripting languages.
+
+The following links discuss a few recommended clients in more detail, including installation instructions and usage examples.
+
+{{< table-children columnNames="Language,Client reference" columnSources="LinkTitle,Title" enableLinks="Title" >}}
\ No newline at end of file
diff --git a/content/rs/references/client_references/client_c.md b/content/rs/references/client_references/client_c.md
index 81e1344983e..0e8993852ff 100644
--- a/content/rs/references/client_references/client_c.md
+++ b/content/rs/references/client_references/client_c.md
@@ -1,5 +1,6 @@
---
-Title: Using Redis with C
+Title: Redis with C
+linkTitle: C
description:
weight:
alwaysopen: false
diff --git a/content/rs/references/client_references/client_csharp.md b/content/rs/references/client_references/client_csharp.md
index 836aa78aa79..1a64baaf959 100644
--- a/content/rs/references/client_references/client_csharp.md
+++ b/content/rs/references/client_references/client_csharp.md
@@ -1,5 +1,6 @@
---
-Title: Using Redis with .NET
+Title: Redis with .NET
+linkTitle: .NET
description:
weight:
alwaysopen: false
diff --git a/content/rs/references/client_references/client_drupal.md b/content/rs/references/client_references/client_drupal.md
index 0bc958dd9e0..45eff8ef571 100644
--- a/content/rs/references/client_references/client_drupal.md
+++ b/content/rs/references/client_references/client_drupal.md
@@ -1,5 +1,6 @@
---
-Title: Using Redis with Drupal 7
+Title: Redis with Drupal 7
+linkTitle: Drupal
description:
weight:
alwaysopen: false
diff --git a/content/rs/references/client_references/client_ioredis.md b/content/rs/references/client_references/client_ioredis.md
index 92256ae2f52..ade54c9f777 100644
--- a/content/rs/references/client_references/client_ioredis.md
+++ b/content/rs/references/client_references/client_ioredis.md
@@ -1,5 +1,6 @@
---
-Title: Using Redis with Node.js (ioredis)
+Title: Redis with Node.js (ioredis)
+linkTitle: Node.js (ioredis)
description:
weight:
alwaysopen: false
diff --git a/content/rs/references/client_references/client_java.md b/content/rs/references/client_references/client_java.md
index 148b4776431..2f1dee4f451 100644
--- a/content/rs/references/client_references/client_java.md
+++ b/content/rs/references/client_references/client_java.md
@@ -1,5 +1,6 @@
---
-Title: Using Redis with Java
+Title: Redis with Java
+linkTitle: Java
description:
weight:
alwaysopen: false
diff --git a/content/rs/references/client_references/client_nodejs.md b/content/rs/references/client_references/client_nodejs.md
index 268f9d5f0d7..ab3c57162e2 100644
--- a/content/rs/references/client_references/client_nodejs.md
+++ b/content/rs/references/client_references/client_nodejs.md
@@ -1,5 +1,6 @@
---
-Title: Using Redis with Node.js (node_redis)
+Title: Redis with Node.js (node_redis)
+linkTitle: Node.js (node_redis)
description:
weight:
alwaysopen: false
diff --git a/content/rs/references/client_references/client_php.md b/content/rs/references/client_references/client_php.md
index 7358409f3e2..ae4b5abf3b6 100644
--- a/content/rs/references/client_references/client_php.md
+++ b/content/rs/references/client_references/client_php.md
@@ -1,5 +1,6 @@
---
-Title: Using Redis with PHP
+Title: Redis with PHP
+linkTitle: PHP
description:
weight:
alwaysopen: false
diff --git a/content/rs/references/client_references/client_python.md b/content/rs/references/client_references/client_python.md
index 822c57e8a7a..e3af6b59bad 100644
--- a/content/rs/references/client_references/client_python.md
+++ b/content/rs/references/client_references/client_python.md
@@ -1,5 +1,6 @@
---
-Title: Using Redis with Python
+Title: Redis with Python
+linkTitle: Python
description:
weight:
alwaysopen: false
diff --git a/content/rs/references/client_references/client_ruby.md b/content/rs/references/client_references/client_ruby.md
index 17666eaf7c9..417ab1e0f5b 100644
--- a/content/rs/references/client_references/client_ruby.md
+++ b/content/rs/references/client_references/client_ruby.md
@@ -1,5 +1,6 @@
---
-Title: Using Redis with Ruby
+Title: Redis with Ruby
+linkTitle: Ruby
description:
weight: $weight
alwaysopen: false
diff --git a/layouts/shortcodes/table-children.html b/layouts/shortcodes/table-children.html
new file mode 100644
index 00000000000..c173ac5ede0
--- /dev/null
+++ b/layouts/shortcodes/table-children.html
@@ -0,0 +1,40 @@
+{{ $columnNamesStr := .Get "columnNames" }}
+{{ $columnNames := split $columnNamesStr "," }}
+{{ $columnSourcesStr := .Get "columnSources" }}
+{{ $columnSources := split $columnSourcesStr "," }}
+{{ $enableLinksStr := .Get "enableLinks" }}
+{{ $enableLinks := split $enableLinksStr "," }}
+{{ $children := .Page.Pages }}
+
+
+
+
+ {{ range $i, $column := $columnNames }}
+
{{ $column }}
+ {{ end }}
+
+
+
+
+ {{ range $i, $child := $children }}
+
+ {{ range $j, $cSource := $columnSources }}
+ {{ if eq $cSource "LinkTitle" }}
+ {{ if in $enableLinks $cSource }}
+
-To flush data from a database:
+This _permanently_ removes all data from the database. The data cannot be recovered, except by restoring from earlier backups.
-1. Connect to the database with Redis CLI.
+We _strongly_ recommend backing up databases before flushing them.
+{{}}
-2. Use the [FLUSHALL](https://redis.io/commands/flushall) command:
+## The Redis-CLI utility
+
+To use the `redis-cli` utility:
```sh
redis-cli -h -p -a flushall
@@ -27,5 +34,61 @@ redis-cli -h -p -a flushall
Example:
```sh
-redis-cli -h redis-12345.c24.us-east-mz-1.ec2.cloud.redislabs.com -p 12345 -a xyz flushall
+redis-cli -h redis-12345.server.cloud.redislabs.example.com -p 12345 -a xyz flushall
+```
+
+## The netcat utility
+
+If you have shell access to the server hosting your database, you can use the [netcat](https://en.wikipedia.org/wiki/Netcat) (`nc`) to send the `flush_all` command to your database:
+
+```sh
+echo "flush_all" | nc redis-12345.server.cloud.redislabs.example.com 12345
+```
+
+## RedisInsight CLI
+
+If you've installed [RedisInsight]({{}}) and added your database, you can use the RedisInsight command-line interface (CLI) to issue commands:
+
+1. Start RedisInsight and connect to your database.
+
+2. From the RedisInsight menu, select **CLI** and wait for the client to connect to your database.
+
+3. In the command area, enter `flushall` and then press _Enter_.
+
+ {{}}{{< /image >}}
+
+ The 'OK' response indicates that the command executed properly.
+
+## SASL connection
+
+If you do not have permission to access the command shell of the server hosting your database or are unable to use RedisInsight, but you have connection credentials and your database supports [Simple Authentication and Security Layer](https://en.wikipedia.org/wiki/Simple_Authentication_and_Security_Layer) connections, you can use an SASL-enabled command-line client.
+
+For example, suppose you're using Memcached Enterprise Cloud and that your database has SASL enabled. In this case, you can can use the [bmemcached-CLI](https://github.com/RedisLabs/bmemcached-cli) client to connect and issue commands to your database.
+
+Setup instructions vary according to the environment. Many Linux systems, such as Ubuntu, follow this process:
+
+```sh
+$ wget https://github.com/RedisLabs/bmemcached-cli/archive/master.zip
+$ sudo apt-get install unzip python-pip
+$ unzip master.zip -d bmemcached-cli
+$ cd bmemcached-cli/bmemcached-cli-master/
+$ sudo pip install --upgrade pip
+$ sudo pip install . -r requirements.pip
+```
+
+Adjust as needed for your operating system and configuration.
+
+When the client is properly installed, you can use it to run the `flush_all` command:
+
+```sh
+bmemcached-cli [user]:[password]@[host]:[port]
```
+
+Here's an example:
+
+```sh
+$ bmemcached-cli username:password@redis-12345.server.cloud.redislabs.example.com:12345
+([B]memcached) flush_all
+True
+exit
+```
\ No newline at end of file
diff --git a/content/rc/how-to/all-memcached-cloud.md b/content/rc/how-to/all-memcached-cloud.md
deleted file mode 100644
index 1acd5d383f5..00000000000
--- a/content/rc/how-to/all-memcached-cloud.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-Title: Using flush_all for Memcached Cloud
-description:
-weight: $weight
-alwaysopen: false
-categories: ["RC"]
----
-Follow the instructions below to use flush_all.
-
-## flush_all for SASL protected Memcached Enterprise cloud databases
-
-If your resource has SASL authentication enabled, you can't use nc
-command or telnet to run flush_all on your Memcached Enterprise Cloud
-resource. You have to download a Memcached CLI client that supports
-SASL. We recommend to use the bmemcached-CLI client, and the
-instructions here is for this client. This instruction refers to Ubuntu
-OS. Make the necessary changes if you are using other Linux
-flavor.
-
-```sh
-$ wget https://github.com/RedisLabs/bmemcached-cli/archive/master.zip
-$ sudo apt-get install unzip python-pip
-$ unzip master.zip -d bmemcached-cli
-$ cd bmemcached-cli/bmemcached-cli-master/
-$ sudo pip install --upgrade pip
-$ sudo pip install . -r requirements.pip
-```
-
-Now you can run the flush_all command using the bmemcached-cli. The
-usage is simple:
-
-```sh
-bmemcached-cli [user]:[password]@[host]:[port]
-```
-
-usage example:
-
-```sh
-$ bmemcached-cli memcached-app123:x298k37@pub-memcache-1010.us-east-1-3.4.ec2.garantiadata.com:1010
-([B]memcached) flush_all
-True
-exit
-```
-
-## flush_all for Memcached Enterprise cloud databases
-
-```sh
-$ telnet memcached-12345.c69.us-east-1-2.ec2.cloud.redislabs.com 12345
-Trying 54.165.69.88...
-Connected to memcached-12345.c69.us-east-1-2.ec2.cloud.redislabs.com.
-Escape character is '^]'.
-flush_all
-OK
-quit
-Connection closed by foreign host.
-```
diff --git a/content/rc/how-to/creating-iam-resources/_index.md b/content/rc/how-to/creating-iam-resources/_index.md
deleted file mode 100644
index 1648155c235..00000000000
--- a/content/rc/how-to/creating-iam-resources/_index.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-Title: Create IAM entities for AWS cloud accounts
-linkTitle: Create IAM entities
-description:
-weight: 30
-categories: ["RC"]
----
-For most Redis Enterprise Cloud Flexible or Annual subscriptions deployed to Amazon Web Services (AWS), we manage the supporting infrastructure for you in dedicated AWS accounts.
-Redis Enterprise Cloud Annual subscriptions let you manage this infrastructure with your own AWS accounts.
-You'll want these accounts to be separate from any AWS application accounts,
-and you'll need to create some dedicated [identity and access management](https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction.html) (IAM) entities to allow us to manage the infrastructure for you.
-
-In the new AWS account, you need to create:
-
-- An **instance role**
-- A user with an **access key**
-- A role that grants **AWS console access**
-
-Make sure that you save the access key in a secure location so that you can enter the key when you create the Redis Cloud account.
-
-{{< warning >}}
-We use the provided credentials to configure your AWS environment and provision required resources.
-
-To make sure that we can manage your AWS resources, you must not:
-
-- Manually change the configurations of provisioned resources, such as security groups
-- Manually stop or terminate provisioned instances
-{{< /warning >}}
-
-For more about creating an AWS user, see the [AWS IAM documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html).
-
-We offer three methods for creating these IAM resources:
-
-- Via [CloudFormation]({{}}) - the 'AWS native' automation tool
-- Via [Terraform]({{}}) - this has the most extensive support for further automation within the Redis world
-- Via the [AWS Console]({{}})
diff --git a/content/rc/how-to/creating-iam-resources/terraform.md b/content/rc/how-to/creating-iam-resources/terraform.md
deleted file mode 100644
index 1129a70c1f6..00000000000
--- a/content/rc/how-to/creating-iam-resources/terraform.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-Title: Create IAM resources using Terraform
-linkTitle: Terraform
-Weight: 20
-categories: ["RC"]
-alwaysopen: false
----
-To automate the creation of the IAM resources needed, simply create a template that references the `terraform-aws-Redislabs-Cloud-Account-IAM-Resources` module, located in S3, as instructed below:
-
-
-1. create a `main.tf` as shown below (replacing the `profile`, `region`, and `pgp_key` values for your own:
-{{% code-include file="rv/terraformIAMTemplate.json" language="js" %}}
-
-Notes:
-- a `pgp_key` is required. See the [Terraform docs](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_user_login_profile#pgp_key) for more details.
-
-2. Initialize Terraform with the module:
-
-Note: Terraform requires [AWS credentials be supplied](https://www.terraform.io/docs/language/modules/sources.html#s3-bucket), but the source of the module is a public S3 bucket, so any valid credentials will do! Replace the `XXXX` fields below with your relevant values
-
-```
-AWS_ACCESS_KEY_ID=XXXX AWS_SECRET_KEY=XXXX terraform init
-```
-
-3. Build the resources:
-
-```
-terraform apply
-```
-This will output the various data you need; although, you'll have to access the sensitive data thus:
-
-* accessSecretKey: `echo $(terraform output -raw accessSecretKey)`
-* consolePassword: `
-echo $(terraform output -raw consolePassword | base64 --decode | keybase pgp decrypt)`
diff --git a/content/rc/how-to/multiple-accounts.md b/content/rc/how-to/multiple-accounts.md
deleted file mode 100644
index dd5551f8dd8..00000000000
--- a/content/rc/how-to/multiple-accounts.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-Title: Member of multiple accounts
-description:
-weight: $weight
-alwaysopen: false
-categories: ["RC"]
----
-You can be a member of multiple accounts in Redis Cloud.
-For example, if you created your own account and your company has arranged its subscriptions into multiple accounts (Dev,
-Test, and Prod) that you are a member of.
-
-When you open the Redis Cloud menu, you see a menu like the screenshot below.
-When you click on the arrow, you see all of the accounts you are a member of, and you can switch between the accounts.
-The permissions for each account are defined by the role you are assigned by the account owner.
-
-![account_multiple_teams](/images/rc/account_multiple_teams.png)
diff --git a/content/rc/how-to/view-edit-cloud-account.md b/content/rc/how-to/view-edit-cloud-account.md
deleted file mode 100644
index 18094e7774c..00000000000
--- a/content/rc/how-to/view-edit-cloud-account.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-Title: Create and edit a Cloud Account
-description:
-weight: 20
-alwaysopen: false
-categories: ["RC"]
-aliases: /rv/how-to/view-edit-cloud-account/
- /rv/how-to/creating-cloud-account/
- /rc/how-to/creating-cloud-account/
----
-
-Many customers use cloud provider accounts provisioned and maintained by Redis Labs.
-
-Customers with existing Amazon Web Services accounts can provision their Flexible or Annual subscriptions to use their existing AWS accounts.
-
-To do so, you associate your existing AWS account as a _cloud account_ for your subscription, which requires entering credentials to enable monitoring, maintenance, and technical support.
-
-You need to create:
-
-1. A programmatic user and provide us with the access key and secret access key for that user.
-1. A console role and provide us with that role name.
-
-To create or edit a cloud account in Redis Cloud:
-
-1. Sign into the admin console and then select the target subscription.
-
-1. From the console menu, select **Cloud Accounts** and then either:
-
- - Select the ![Add](/images/rs/icon_add.png#no-click "Add") to add a new account.
-
- - Select the account that you want to edit and then select **Edit**.
-
-1. Enter the cloud account details, which include:
-
- - **Account Name** - A meaningful name for the account
- - **AWS_ACCESS_KEY_ID** - The AWS access key for the programmatic user
- - **AWS_SECRET_ACCESS_KEY** - The AWS secret access key for the programmatic user
- - **IAM Role Name** - The name of the console role with access to the console
-
-1. Select **Save**.
-
-Use the **Delete** button to remove a cloud account from your subscription.
diff --git a/content/rc/rc-quickstart.md b/content/rc/rc-quickstart.md
index fc2f72940f1..9a47cdc3d01 100644
--- a/content/rc/rc-quickstart.md
+++ b/content/rc/rc-quickstart.md
@@ -170,12 +170,10 @@ Here's how to connect to your database using the `redis-py` library for Python.
bar
```
-
-
## More info
-- [Manage Databases]({{< relref "/rc/databases/_index.md" >}})
-- [Data Persistence with Redis Cloud]({{< relref "rc/concepts/data-persistence.md" >}})
-- [Secure Your Redis Cloud Database]({{< relref "/rc/administration/security/_index.md" >}})
+- [Manage databases]({{< relref "/rc/databases/_index.md" >}})
+- [Data persistence]({{< relref "/rc/databases/configuration/data-persistence.md" >}})
+- [Secure your Redis Enterprise Cloud database]({{< relref "/rc/administration/security/_index.md" >}})
- [Back-up Flexible databases]({{< relref "/rc/databases/back-up-data.md" >}})
-- [Monitor Redis Cloud Performance]({{< relref "/rc/databases/monitor-performance.md" >}}).
+- [Monitor Redis Enterprise Cloud performance]({{< relref "/rc/databases/monitor-performance.md" >}}).
diff --git a/content/rc/security/database-security/encryption-at-rest.md b/content/rc/security/database-security/encryption-at-rest.md
index cec8747b07c..60103778bd1 100644
--- a/content/rc/security/database-security/encryption-at-rest.md
+++ b/content/rc/security/database-security/encryption-at-rest.md
@@ -5,7 +5,7 @@ weight: 40
alwaysopen: false
categories: ["RC"]
---
-Redis Cloud databases write their data to disk whenever [persistence]({{}}) is enabled.
+Redis Cloud databases write their data to disk whenever [persistence]({{}}) is enabled.
On [Google Cloud Platform](#gcp) (GCP) and [Microsoft Azure](#azure), Redis Cloud deployments are always encrypted at rest.
diff --git a/content/rc/subscriptions/create-flexible-subscription.md b/content/rc/subscriptions/create-flexible-subscription.md
index d8bb53efb9b..64c6f2efbdb 100644
--- a/content/rc/subscriptions/create-flexible-subscription.md
+++ b/content/rc/subscriptions/create-flexible-subscription.md
@@ -49,7 +49,7 @@ There are three sections on this tab:
| **Cloud Vendor** | The public cloud provider |
| **Region(s)** | The cloud region for your subscription |
| **Multi-AZ** | Whether in-memory data is replicated to another zone within the deployment region. For best results, choose a region with at least three availability zones.|
-| **Cloud Account** | (_AWS_) Credentials allowing Redis Cloud to be deployed to an existing AWS account. See [Create and Edit a Cloud Account]({{< relref "/rc/how-to/view-edit-cloud-account.md" >}})|
+| **Cloud Account** | (_AWS_) Credentials allowing Redis Cloud to be deployed to an existing AWS account. See [Manage cloud accounts]({{< relref "/rc/cloud-accounts/" >}})|
### Advanced options {#advanced-options}
diff --git a/content/rc/subscriptions/view-flexible-subscription.md b/content/rc/subscriptions/view-flexible-subscription.md
index 3679fb5375d..6388cf04f10 100644
--- a/content/rc/subscriptions/view-flexible-subscription.md
+++ b/content/rc/subscriptions/view-flexible-subscription.md
@@ -25,7 +25,7 @@ Two tabs are available:
|:---------|:--------------|
| **Subscription name** | A descriptive name for the plan; can be changed at any time.|
| **Runs on** | Either _RAM_ or _RAM+Flash_ |
- | **Cloud account** | (_AWS only_) Descriptive name of the associated cloud account (Useful for organizations that manage [multiple accounts]({{}})) |
+ | **Cloud account** | (_AWS only_) Descriptive name of the associated cloud account (Useful for organizations that manage [multiple accounts]({{}})) |
| **Cloud** | Describes the subscription cloud provider |
| **Region** | Deployment region details |
| **Multi-AZ** | Indicates whether replication is deployed across multiple availability zones within the region |
diff --git a/content/rs/administering/designing-production/networking/using-oss-cluster-api.md b/content/rs/administering/designing-production/networking/using-oss-cluster-api.md
index 3965b205f77..ef599fceaae 100644
--- a/content/rs/administering/designing-production/networking/using-oss-cluster-api.md
+++ b/content/rs/administering/designing-production/networking/using-oss-cluster-api.md
@@ -16,7 +16,7 @@ Before you enable Redis OSS Cluster API for a database, make sure that:
- The database proxy policy does not use node `include` or `exclude`.
When you enable the Redis OSS Cluster API from the command line or RS admin console,
-[multi-key commands]({{< relref "/rc/concepts/clustering#multikey-operations" >}}) are only allowed when all keys are mapped to the same slot.
+[multi-key commands]({{< relref "/rc/databases/configuration/clustering#multikey-operations" >}}) are only allowed when all keys are mapped to the same slot.
To verify that your database meets this requirement, make sure that the `CLUSTER KEYSLOT` reply is the same for all keys in the [multi-key command]({{< relref "/rs/concepts/high-availability/clustering#multikey-operations" >}}).
## Enabling OSS Cluster API support from the admin console
diff --git a/layouts/partials/home/options.html b/layouts/partials/home/options.html
index b896d17dec5..171e6b1ab65 100644
--- a/layouts/partials/home/options.html
+++ b/layouts/partials/home/options.html
@@ -10,12 +10,12 @@