Relref fixes

Author: cmilesb

content/embeds/rc-vpc-peering-cidr-list.md

@@ -1 +1 @@
-If you've enabled the database's [CIDR allow list]({{< relref "/operate/rc/security/cidr-whitelist" >}}), you must also [add the VPC peered IP addresses to the CIDR allow list]({{< relref "/operate/rc/security/cidr-whitelist#define-cidr-allow-list" >}}) to connect to the database via the private endpoint.
+If you've enabled the database's [CIDR allow list]({{< relref "/operate/rc/security/network-security/cidr-whitelist" >}}), you must also [add the VPC peered IP addresses to the CIDR allow list]({{< relref "/operate/rc/security/network-security/cidr-whitelist#define-cidr-allow-list" >}}) to connect to the database via the private endpoint.

content/glossary/_index.md

@@ -18,7 +18,7 @@ aliases: /glossary/
 {{%definition "access control list (ACL)"%}}
 Allows you to manage permissions based on key patterns.
 
-More info: [redis.io/operate/oss_and_stack/management/security/acl]({{< relref "/operate/oss_and_stack/management/security/acl" >}}); [ACL wikipedia](https://en.wikipedia.org/wiki/Access-control_list); [Database access control]({{<relref "/operate/rs/security/access-control">}}); [Update database ACLs]({{<relref "/operate/rs/security/access-control/ldap/update-database-acls">}}); [Role-based access control]({{<relref "/operate/rc/security/access-control/data-access-control/role-based-access-control">}})
+More info: [redis.io/operate/oss_and_stack/management/security/acl]({{< relref "/operate/oss_and_stack/management/security/acl" >}}); [ACL wikipedia](https://en.wikipedia.org/wiki/Access-control_list); [Database access control]({{<relref "/operate/rs/security/access-control">}}); [Update database ACLs]({{<relref "/operate/rs/security/access-control/ldap/update-database-acls">}}); [Role-based access control]({{<relref "/operate/rc/security/data-access-control/role-based-access-control">}})
 {{%/definition%}}
 
 <a name="active-active"></a>
@@ -64,7 +64,7 @@ More info: [Causal consistency wikipedia](https://en.wikipedia.org/wiki/Causal_c
 {{%definition "CIDR allowlist"%}}
 Classless Inter-Domain Routing (CIDR) is a method to allocate and route IP addresses. A CIDR allowlist defines a range of IP addresses and permits connections to them.
 
-More info: [CIDR wikipedia](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing), [Configure CIDR allowlist]({{<relref "/operate/rc/security/cidr-whitelist">}})
+More info: [CIDR wikipedia](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing), [Configure CIDR allowlist]({{<relref "/operate/rc/security/network-security/cidr-whitelist">}})
 {{%/definition%}}
 
 {{%definition "concurrent writes"%}}
@@ -349,7 +349,7 @@ More info: [Database replication]({{<relref "/operate/rs/databases/durability-ha
 {{%definition "role-based access control (RBAC)"%}}
 A security approach that restricts system access to authorized users.
 
-More info: [RBAC wikipedia](https://en.wikipedia.org/wiki/Role-based_access_control); [Database access control]({{<relref "/operate/rs/security/access-control">}}); [Role-based access control]({{<relref "/operate/rc/security/access-control/data-access-control/role-based-access-control">}})
+More info: [RBAC wikipedia](https://en.wikipedia.org/wiki/Role-based_access_control); [Database access control]({{<relref "/operate/rs/security/access-control">}}); [Role-based access control]({{<relref "/operate/rc/security/data-access-control/role-based-access-control">}})
 {{%/definition%}}
 
 ## S {#letter-s}
@@ -401,7 +401,7 @@ More info: [TLS wikipedia](https://en.wikipedia.org/wiki/Transport_Layer_Securit
 {{%definition "VPC peering"%}}
 Networking connection between two VPCs that enables you to route traffic between them using private IP addresses. Instances in either VPC can communicate with each other as if they are within the same network.
 
-More info: [VPC wikipedia](https://en.wikipedia.org/wiki/Virtual_private_cloud), [Enable VPC peering]({{<relref "/operate/rc/security/vpc-peering">}})
+More info: [VPC wikipedia](https://en.wikipedia.org/wiki/Virtual_private_cloud), [Enable VPC peering]({{<relref "/operate/rc/security/network-security/connect-private-endpoint/vpc-peering">}})
 {{%/definition%}}
 
 

content/integrate/confluent-with-redis-cloud/_index.md

@@ -65,7 +65,7 @@ To add the Redis Sink connector to your Confluent Cloud environment from the Red
     - **Redis hostname**: The Public endpoint of your database, without the port number. This can be found in the [Redis Cloud console](https://cloud.redis.io/) from the database list or from the **General** section of the **Configuration** tab for the source database.
     - **Redis port number**: The database's port. This is the number at the end of your database's Public endpoint.
     - **Redis database index**: Set this to 0 for a Redis Cloud database.
-    - **Redis server password**: Enter the database password. If you have not set your own database user and password, use the [default user password]({{< relref "/operate/rc/security/access-control/data-access-control/default-user" >}}), which appears in the **Security** section of the **Configuration** tab of the database details screen.
+    - **Redis server password**: Enter the database password. If you have not set your own database user and password, use the [default user password]({{< relref "/operate/rc/security/data-access-control/default-user" >}}), which appears in the **Security** section of the **Configuration** tab of the database details screen.
     - **SSL mode**: Set depending on what type of [TLS authentication]({{< relref "/operate/rc/security/database-security/tls-ssl" >}}) is set for your database.
         - If TLS authentication is turned off, select **disabled**.
         - If TLS authentication is turned on, select **server**. 

content/integrate/datadog-with-redis-cloud/_index.md

@@ -42,7 +42,7 @@ Select 'Integrations' from the menu in the Datadog portal and then enter 'Redis'
 'Redis Cloud by Redis, Inc.'. Next click 'Install Integration' in the top-right corner of the overview page.
 
 If you have not already created a VPC between the Redis Cloud cluster and the network in which the machine hosting the 
-Datadog agent lives you should do so now. Please visit [VPC Peering](https://redis.io/docs/latest/operate/rc/security/vpc-peering/) 
+Datadog agent lives you should do so now. Please visit [VPC Peering](https://redis.io/docs/latest/operate/rc/security/network-security/connect-private-endpoint/vpc-peering/) 
 and follow the instructions for the cloud platform of your choice.
 
 Returning to the Datadog console, open the 'Configure' tab of the integration and follow the instructions for installing 

content/integrate/dynatrace-with-redis-cloud/_index.md

@@ -39,7 +39,7 @@ another destination using remote writes. This will require a Prometheus installa
 Redis Cloud deployment.
 
 If you have not already created a VPC between the Redis Cloud cluster and the network in which the machine hosting 
-Prometheus lives you should do so now. Please visit [VPC Peering](https://redis.io/docs/latest/operate/rc/security/vpc-peering/) 
+Prometheus lives you should do so now. Please visit [VPC Peering](https://redis.io/docs/latest/operate/rc/security/network-security/connect-private-endpoint/vpc-peering/) 
 and follow the instructions for the cloud platform of your choice.
 
 

content/integrate/new-relic-with-redis-cloud/_index.md

@@ -40,7 +40,7 @@ another destination using remote writes. This will require a Prometheus installa
 Redis Cloud deployment.
 
 If you have not already created a VPC between the Redis Cloud cluster and the network in which the machine hosting 
-Prometheus lives you should do so now. Please visit [VPC Peering](https://redis.io/docs/latest/operate/rc/security/vpc-peering/) 
+Prometheus lives you should do so now. Please visit [VPC Peering](https://redis.io/docs/latest/operate/rc/security/network-security/connect-private-endpoint/vpc-peering/) 
 and follow the instructions for the cloud platform of your choice.
 
 Finally, the Prometheus installation must be configured to pull metrics from Redis Cloud and write them to New Relic. There 

content/integrate/prometheus-with-redis-cloud/_index.md

@@ -23,7 +23,7 @@ You can use Prometheus and Grafana to collect and visualize your Redis Cloud met
 
 Redis Cloud exposes its metrics through a Prometheus endpoint. You can configure your Prometheus server to scrape metrics from your Redis Cloud subscription on port 8070.
 
-The Redis Cloud Prometheus endpoint is exposed on Redis Cloud's internal network. To access this network, enable [VPC peering]({{< relref "/operate/rc/security/vpc-peering" >}}) or [Private Service Connect]({{< relref "/operate/rc/security/private-service-connect" >}}). Both options are only available with Redis Cloud Pro. You cannot use Prometheus and Grafana with Redis Cloud Essentials.
+The Redis Cloud Prometheus endpoint is exposed on Redis Cloud's internal network. To access this network, enable [VPC peering]({{< relref "/operate/rc/security/network-security/connect-private-endpoint/vpc-peering" >}}) or [Private Service Connect]({{< relref "/operate/rc/security/network-security/connect-private-endpoint/private-service-connect" >}}). Both options are only available with Redis Cloud Pro. You cannot use Prometheus and Grafana with Redis Cloud Essentials.
 
 For more information on how Prometheus communicates with Redis Enterprise clusters, see [Prometheus integration with Redis Enterprise Software]({{< relref "/integrate/prometheus-with-redis-enterprise/" >}}).
 
@@ -35,7 +35,7 @@ You can quickly set up Prometheus and Grafana for testing using the Prometheus a
 
 1. Create a [Redis Cloud Pro database]({{< relref "/operate/rc/databases/create-database/create-pro-database-new" >}}). 
 
-1. Set up [VPC peering]({{< relref "/operate/rc/security/vpc-peering" >}}).
+1. Set up [VPC peering]({{< relref "/operate/rc/security/network-security/connect-private-endpoint/vpc-peering" >}}).
 
 1. Extract the Prometheus endpoint from the private endpoint to your database. The private endpoint is in the [Redis Cloud console](https://cloud.redis.io/) under the [Configuration tab]({{< relref "/operate/rc/databases/view-edit-database#configuration-tab" >}}) of your database. The Prometheus endpoint is on port 8070 of the internal server.
 

content/integrate/pulumi-provider-for-redis-cloud/_index.md

@@ -53,7 +53,7 @@ The "bring your own AWS account" option for Redis Cloud has been deprecated. The
 * [`ActiveActiveSubscriptionDatabase`](https://www.pulumi.com/registry/packages/rediscloud/api-docs/activeactivesubscriptiondatabase/): Represents a Redis database which belongs to a specific Redis Cloud active-active subscription.
 * [`ActiveActiveSubscriptionRegions`](https://www.pulumi.com/registry/packages/rediscloud/api-docs/activeactivesubscriptionregions/): The different regions where the active-active subscription will be deployed.
 * [`ActiveActiveSubscriptionPeering`](https://www.pulumi.com/registry/packages/rediscloud/api-docs/activeactivesubscriptionpeering/): A VPC peering connection (AWS or GCP) to a specific Redis Cloud active-active subscription.
-* [`AclRule`](https://www.pulumi.com/registry/packages/rediscloud/api-docs/aclrule/), [`AclRole`](https://www.pulumi.com/registry/packages/rediscloud/api-docs/aclrole/), and [`AclUser`](https://www.pulumi.com/registry/packages/rediscloud/api-docs/acluser/): Rules, Roles, and Users for [Role-based access control]({{< relref "/operate/rc/security/access-control/data-access-control/role-based-access-control" >}}).
+* [`AclRule`](https://www.pulumi.com/registry/packages/rediscloud/api-docs/aclrule/), [`AclRole`](https://www.pulumi.com/registry/packages/rediscloud/api-docs/aclrole/), and [`AclUser`](https://www.pulumi.com/registry/packages/rediscloud/api-docs/acluser/): Rules, Roles, and Users for [Role-based access control]({{< relref "/operate/rc/security/data-access-control/role-based-access-control" >}}).
 
 It also allows for the following functions:
 
@@ -70,7 +70,7 @@ The "bring your own AWS account" option for Redis Cloud has been deprecated. The
 * [`GetRegions`](https://www.pulumi.com/registry/packages/rediscloud/api-docs/getregions/): Get the regions related to an active-active subscription
 * [`GetSubscription`](https://www.pulumi.com/registry/packages/rediscloud/api-docs/getsubscription/): Get the information related to a specific subscription.
 * [`GetSubscriptionPeerings`](https://www.pulumi.com/registry/packages/rediscloud/api-docs/getsubscriptionpeerings/): Get the VPC peerings (AWS or GCP) related to a specific subscription.
-* [`GetAclRule`](https://www.pulumi.com/registry/packages/rediscloud/api-docs/getaclrule/), [`GetAclRole`](https://www.pulumi.com/registry/packages/rediscloud/api-docs/getaclrole/), and [`GetAclUser`](https://www.pulumi.com/registry/packages/rediscloud/api-docs/getacluser/): Get the Rules, Roles, and Users for [Role-based access control]({{< relref "/operate/rc/security/access-control/data-access-control/role-based-access-control" >}}).
+* [`GetAclRule`](https://www.pulumi.com/registry/packages/rediscloud/api-docs/getaclrule/), [`GetAclRole`](https://www.pulumi.com/registry/packages/rediscloud/api-docs/getaclrole/), and [`GetAclUser`](https://www.pulumi.com/registry/packages/rediscloud/api-docs/getacluser/): Get the Rules, Roles, and Users for [Role-based access control]({{< relref "/operate/rc/security/data-access-control/role-based-access-control" >}}).
 
 ## More info
 

content/operate/_index.md

@@ -45,10 +45,10 @@ hideListLinks: true
 | | <nobr>{{<color-bubble color="bg-blue-bubble" >}} Redis</nobr> Cloud | <nobr>{{<color-bubble color="bg-yellow-bubble">}} Redis</nobr> Software | <nobr>{{<color-bubble color="bg-purple-bubble">}} Redis</nobr> Open Source | <nobr><div class="h-3 w-3 rounded-md border border-redis-pen-600 inline-block mr-1" style="background-color: #8A99A0"></div> Redis for</nobr> Kubernetes |
 |:-----------|:--------------|:-----------|:--------------|:--------------|
 | Transport Layer Security (TLS) | [TLS]({{<relref "/operate/rc/security/database-security/tls-ssl">}}) | [TLS]({{<relref "/operate/rs/security/encryption/tls">}}) | [TLS]({{< relref "/operate/oss_and_stack/management/security/encryption" >}}) | [REDB tlsMode]({{<relref "/operate/kubernetes/reference/redis_enterprise_database_api/#spec">}}) |
-| Role-based access control (RBAC) | [Role-based access control]({{<relref "/operate/rc/security/access-control/data-access-control/role-based-access-control">}}) | [Access control]({{<relref "/operate/rs/security/access-control">}}) | [Access control list]({{< relref "/operate/oss_and_stack/management/security/acl" >}}) | [REC credentials]({{<relref "/operate/kubernetes/security/manage-rec-credentials/">}}) |
+| Role-based access control (RBAC) | [Role-based access control]({{<relref "/operate/rc/security/data-access-control/role-based-access-control">}}) | [Access control]({{<relref "/operate/rs/security/access-control">}}) | [Access control list]({{< relref "/operate/oss_and_stack/management/security/acl" >}}) | [REC credentials]({{<relref "/operate/kubernetes/security/manage-rec-credentials/">}}) |
 | Lightweight Directory Access Protocol (LDAP) |  | [LDAP authentication]({{<relref "/operate/rs/security/access-control/ldap">}}) |  | [Enable LDAP]({{<relref "/operate/kubernetes/security/ldap/">}}) |
 | Single sign-on (SSO) | [SAML SSO]({{< relref "/operate/rc/security/access-control/saml-sso" >}}) |  |  |  |
 | Self-signed certificates |  | [Certificates]({{<relref "/operate/rs/security/certificates">}}) | [Certificate configuration]({{< relref "/operate/oss_and_stack/management/security/encryption#certificate-configuration" >}}) | [REC certificates]({{<relref "operate/kubernetes/security/manage-rec-certificates/">}}) |
-| Internode encryption | [Encryption at rest]({{< relref "/operate/rc/security/encryption-at-rest" >}}) | [Internode encryption]({{<relref "/operate/rs/security/encryption/internode-encryption">}}) |  | [Enable internode encryption]({{<relref "operate/kubernetes/security/internode-encryption/">}}) |
+| Internode encryption | [Encryption at rest]({{< relref "/operate/rc/security/database-security/encryption-at-rest" >}}) | [Internode encryption]({{<relref "/operate/rs/security/encryption/internode-encryption">}}) |  | [Enable internode encryption]({{<relref "operate/kubernetes/security/internode-encryption/">}}) |
 | Auditing |  | [Audit events]({{<relref "/operate/rs/security/audit-events">}}) | [Keyspace notifications]({{< relref "/develop/use/keyspace-notifications" >}}) |  |
 

content/operate/rc/_index.md

@@ -51,7 +51,7 @@ Manage [secure connections]({{< relref "/operate/rc/security" >}}) to cloud data
 - [Cloud database security]({{< relref "/operate/rc/security/database-security" >}})
 - [Multi-factor authentication]({{< relref "/operate/rc/security/access-control/multi-factor-authentication" >}})
 - [Single sign-on]({{< relref "/operate/rc/security/access-control/saml-sso" >}}) and [social login]({{< relref "/operate/rc/security/access-control/social-login" >}})
-- [Data access control]({{< relref "/operate/rc/security/access-control/data-access-control" >}})
+- [Data access control]({{< relref "/operate/rc/security/data-access-control" >}})
 
 ## REST API
 Use the [REST API]({{< relref "/operate/rc/api" >}}) to manage the database.