This page explains how to set up connectivity for multiple Virtual Private Cloud (VPC)
networks and a new Memorystore for Redis Cluster instance.

To set up connectivity, do the following:

- Create Private Service Connect endpoints in consumer networks.

- Target the service attachments for your Memorystore for Redis Cluster instance.

- Register the components with the instance.

After completing these tasks, you connect your client to the instance through
the Private Service Connect connections that you create.

For instructions on how to set up multiple VPC networking for an instance that
already has some [automatically registered Private Service Connect connections](https://docs.cloud.google.com/memorystore/docs/cluster/about-multiple-vpc-networking.md.txt#psc_connection_types), see [Set up multiple VPC networks for instances provisioned with automatically registered Private Service Connect connections](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-automatically-registered-psc-connection.md.txt).

For more information about multiple VPC network setups, see
[About multiple VPC networking](https://docs.cloud.google.com/memorystore/docs/cluster/about-multiple-vpc-networking.md.txt).

![A diagram that shows networking architecture. It has two customer VPC networks across two projects connected to a Private Service Connect connection, which is connected to the Memorystore service attachment.](https://docs.cloud.google.com/static/memorystore/img/mrc-multi-vpc.png)

## Summary of key steps

This section gives a summary list of the key steps in this tutorial for setting
up your Private Service Connect connections. First, you should
prepare to follow this tutorial by completing the steps in the
[Before you begin](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#before_you_begin) section.

> [!NOTE]
> **Note:** The sample commands on this page are [`gcloud CLI`](https://docs.cloud.google.com/sdk/gcloud/reference/memorystore) commands. To find instructions and examples of using Terraform to perform these tasks, see the [google_redis_cluster_user_created_connections](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/redis_cluster_user_created_connections) page.

### Key steps

1. [Step 1: Create an instance](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#step_1_create_an_instance)
2. [Step 2: Note the service attachment paths](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#step_2_note_the_service_attachment_paths)
3. [Step 3: Set up and register Private Service Connect connections for your first VPC network](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#step_3_set_up_and_register_connections_for_your_first_vpc_network)
4. [Step 4: Set up and register Private Service Connect connections for your second VPC network](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#step_4_set_up_and_register_connections_for_your_second_vpc_network)
5. [Step 5: Set up a client connection](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#step_5_set_up_a_client_connection)

Additionally, you can also:

- [Delete your Private Service Connect connections](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#delete_your_connections)
- [Delete your Memorystore for Redis Cluster instance](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#delete_your_memorystore_for_redis_cluster_instance)

## Before you begin

Before you begin, ensure that you have the following IAM roles
and Google Cloud resources.

> [!CAUTION]
> **Important** : To use multiple VPC networking with Memorystore for Redis Cluster, your cluster must run a maintenance version of at least `REDISCLUSTER_20251210_02_00`. If your cluster runs an older maintenance version, then you must perform a self-service update before you can add or use multiple connections. For more information about updating your cluster to a newer maintenance version, see [Self-service maintenance](https://docs.cloud.google.com/memorystore/docs/cluster/self-service-maintenance.md.txt).

### Required IAM roles

| Example resource ID | Resource type |
|---|---|
| [`roles/redis.admin`](https://docs.cloud.google.com/memorystore/docs/cluster/access-control.md.txt#predefined_roles) | Provides full control of a Memorystore for Redis Cluster instance and controls the instance over its lifecycle. |
| [`roles/servicedirectory.editor`](https://docs.cloud.google.com/service-directory/docs/access-control.md.txt) | Grants you permission to edit Service Directory resources. This role is needed for creating a Private Service Connect endpoint. |
| [`roles/compute.networkAdmin`](https://docs.cloud.google.com/compute/docs/access/iam.md.txt#compute.networkAdmin) | Grants full control over the VPC network that initiates a connection to a Memorystore instance. You can create and manage IP addresses, firewall rules, and [Private Service Connect endpoints](https://docs.cloud.google.com/vpc/docs/about-accessing-vpc-hosted-services-endpoints.md.txt). This role is needed for creating a Private Service Connect endpoint. If you use Private Service Connect to connect to a Memorystore instance from multiple VPC networks, then each network may have its own administrator. |

### Prerequisite resources

You need to create the following resources before you begin this tutorial. We
recommend creating the resources with the following IDs and locations, however
you can also choose your own IDs and locations. In this tutorial, you will use
the following resources to set up two Private Service Connect
connections in VPC network 1:

| Example resource ID | Resource type | Example full path | Description |
|---|---|---|---|
| `my-project-1` | Google Cloud project | n/a | Your Memorystore instance is located in this project |
| `my-network-1` | VPC network | `projects/my-project-1/global/networks/my-network-1` | In this tutorial, you set up 2 Private Service Connect connections in this network |
| `my-subnet-1` | VPC subnet | `projects/my-project-1/regions/us-central1/subnetworks/my-subnet-1 ` | In this tutorial, you reserve 2 IP addresses in this subnet |

In this tutorial, you will use the following resources to create two
Private Service Connect connections in VPC network 2:

| Example resource ID | Resource type | Example full path | Description |
|---|---|---|---|
| `my-project-2` | Google Cloud project | n/a | For this tutorial, this is the project where you create the second network and second subnetwork. However, the second network and subnet can be in the same project as the first network, if you choose. |
| `my-network-2` | VPC network | `projects/my-project-2/global/networks/my-network-2` | In this tutorial, you create 2 Private Service Connect endpoints in this network |
| `my-subnet-2` | VPC subnet | `projects/my-project-2/regions/us-central1/subnetworks/my-subnet-2 ` | In this tutorial, you reserve 2 IP addresses in this subnet |

### Enable APIs

Enable the following APIs needed for managing Compute Engine networking,
Memorystore for Redis Cluster, and Private Service Connect resources.

### gcloud

To enable the APIs in both project 1 and project 2, run the following
commands:

```
gcloud services enable --project=PROJECT_1_ID compute.googleapis.com
gcloud services enable --project=PROJECT_2_ID compute.googleapis.com
gcloud services enable --project=PROJECT_1_ID redis.googleapis.com
gcloud services enable --project=PROJECT_2_ID redis.googleapis.com
gcloud services enable --project=PROJECT_1_ID servicedirectory.googleapis.com
gcloud services enable --project=PROJECT_2_ID servicedirectory.googleapis.com
```

## Step 1: Create an instance

This guide shows you how to set up connectivity for a Memorystore
instance that has no [automatically registered Private Service Connect connections](https://docs.cloud.google.com/memorystore/docs/cluster/about-multiple-vpc-networking.md.txt#psc_connection_types).
It is acceptable to have a service connection policy, but a service connection
policy isn't required when following the process for user-registering
Private Service Connect connections.

To avoid automatically creating and registering
Private Service Connect connections, run the create command
without specifying a network, as seen in the following example.

### gcloud

To create an instance without auto-creating any
Private Service Connect connections, run the
`gcloud redis cluster create` command, without using the `--network`
parameter, as follows:

```
gcloud redis clusters create INSTANCE_ID \
--region=REGION_ID \
--project=PROJECT_1_ID \
--replica-count=REPLICA_COUNT \
--node-type=NODE_TYPE \
--shard-count=SHARD_COUNT
```

Replace the following:

- <var translate="no">INSTANCE_ID</var> is the ID of the Memorystore for Redis Cluster instance
  you're creating. Your instance ID must be 1 to 63 characters and use only
  lowercase letters, numbers, or hyphens. It must start with a lowercase letter
  and end with a lowercase letter or number.

- <var translate="no">REGION_ID</var> is the region where you want the instance placed.

- <var translate="no">PROJECT_1_ID</var> is the ID of project 1. This is the project where
  your Memorystore instance is located.

- <var translate="no">REPLICA_COUNT</var> is the number of replicas (per shard). Accepted
  values are `0`-`5`.

- <var translate="no">NODE_TYPE</var> is the [node type](https://docs.cloud.google.com/memorystore/docs/cluster/cluster-node-specification.md.txt#choose_a_node_type) that you want to use for the
  cluster.

  > [!CAUTION]
  > **Caution** : We recommend that you use the `redis-shared-core-nano` node type only for development or testing purposes because this node type has no SLA. If you run Memorystore for Redis Cluster in a production environment, then we recommend using another node type.

- <var translate="no">SHARD_COUNT</var> determines the number of shards in your instance.
  Shard count determines the total memory capacity for storing cluster data. To
  see more details about cluster specification, see [Cluster and node specification](https://docs.cloud.google.com/memorystore/docs/cluster/cluster-node-specification.md.txt).

For example:

```
gcloud redis clusters create my-instance \
--region=us-central1 \
--replica-count=2 \
--node-type=redis-highmem-medium \
--shard-count=8
```

## Step 2: Note the service attachment paths

After creating a Memorystore instance, make a note of the two
service attachment URIs for your Memorystore instance. You use
these service attachment URIs to set up Private Service Connect
connections.

### gcloud

To view summary information about an instance with
Private Service Connect enabled, look for the `pscServiceAttachments`
field. This field displays the two URIs that point to the service attachments
of the instance. To view this information, use the
`gcloud redis clusters describe` command:

```
gcloud redis clusters describe INSTANCE_ID --project=PROJECT_1_ID --region=REGION_ID
```

Replace the following:

- <var translate="no">INSTANCE_ID</var> is the name of your Memorystore instance.
- <var translate="no">PROJECT_1_ID</var> is the ID of project 1. This is the project where your Memorystore instance is located.
- <var translate="no">REGION_ID</var> is the ID of the region where your instance is located.

The following shows a sample output for this command:

```
gcloud redis clusters describe my-instance \
--project=my-project-1 --region=us-central1

...

pscServiceAttachments:
- connectionType: CONNECTION_TYPE_DISCOVERY
  serviceAttachment: projects/1048073346231/regions/us-central1/serviceAttachments/gcp-memorystore-auto-8d7d48ef-3ca3-4d-psc-sa
- serviceAttachment: projects/1048073346231/regions/us-central1/serviceAttachments/gcp-memorystore-auto-8d7d48ef-3ca3-4d-psc-sa-2
```

## Step 3: Set up and register Private Service Connect connections for your first VPC network

This section shows you how to set up the two connections required for your first
VPC network. You must repeat this process for every VPC for which you want to
set up connectivity. For example, later in this tutorial you will find these
steps repeated again, but for the new connections needed for the second VPC
network.

### Create the Private Service Connect endpoints for network 1

This section explains the actions you need to take to create 2
Private Service Connect endpoints in Network 1.

#### Reserve IP addresses for network 1

Next, reserve two IP addresses in network 1.

##### Reserve IP address 1

### gcloud

To reserve IP address 1, run the `gcloud compute addresses create` command:

```
gcloud compute addresses create IP_ADDRESS_1_ID \
--project=PROJECT_1_ID \
--addresses=IP_ADDRESS_1 \
--region=REGION_ID \
--subnet=projects/PROJECT_1_ID/regions/REGION_ID/subnetworks/SUBNET_1_ID \
--purpose=GCE_ENDPOINT
```

Replace the following:

- <var translate="no">IP_ADDRESS_1_ID</var> is the ID you give to your IP address.
- <var translate="no">PROJECT_1_ID</var> is the ID of project 1. This is the project where your Memorystore instance is located.
- <var translate="no">IP_ADDRESS_1</var> is an IP address of your choosing from within the `SUBNET_1_ID` range you reserved as a part of [Prerequisite resources](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#prerequisite_resources).
- <var translate="no">REGION_ID</var> is the region where your Memorystore instance is located.
- <var translate="no">SUBNET_1_ID</var> is the ID of the subnetwork you reserved on network one in project 1 as a part of [Prerequisite resources](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#prerequisite_resources).

For example:

```
gcloud compute addresses create my-ip-address-1 \
--project=my-project-1 \
--addresses=10.2.5.9 \
--region=us-central1 \
--subnet=projects/my-project-1/regions/us-central1/subnetworks/my-subnet-1 \
--purpose=GCE_ENDPOINT
```

##### Reserve IP address 2

### gcloud

To reserve IP address 2, run the `gcloud compute addresses create` command:

```
gcloud compute addresses create IP_ADDRESS_2_ID \
--project=PROJECT_1_ID \
--addresses=IP_ADDRESS_2 \
--region=REGION_ID \
--subnet=projects/PROJECT_1_ID/regions/REGION_ID/subnetworks/SUBNET_1_ID \
--purpose=GCE_ENDPOINT
```

Replace the following:

- <var translate="no">IP_ADDRESS_2_ID</var> is the ID you give to your IP address.
- <var translate="no">PROJECT_1_ID</var> is the ID of project 1. This is the project where your Memorystore instance is located.
- <var translate="no">IP_ADDRESS_2</var> is an IP address of your choosing from within the `SUBNET_1_ID` range you reserved as a part of [Prerequisite resources](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#prerequisite_resources).
- <var translate="no">REGION_ID</var> is the region where your Memorystore instance is located.
- <var translate="no">SUBNET_1_ID</var> is the ID of the subnetwork you reserved on network 1 in project 1 as a part of [Prerequisite resources](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#prerequisite_resources).

#### Add forwarding rules for network 1

Next, create forwarding rules that connect the IP addresses to the
Memorystore instance's service attachments.

##### Add forwarding rule 1 for IP 1

### gcloud

To add a forwarding rule for IP 1, run the `gcloud compute forwarding-rules create`
command:

```
gcloud compute forwarding-rules create FORWARDING_RULE_1_NAME \
--address=IP_ADDRESS_1_ID \
--network=projects/PROJECT_1_ID/global/networks/NETWORK_1_ID \
--region=REGION_ID \
--target-service-attachment=SERVICE_ATTACHMENT_1 \
--project=PROJECT_1_ID \
--allow-psc-global-access
```

Replace the following:

- <var translate="no">FORWARDING_RULE_1_NAME</var> is the name you give to the forwarding rule you are creating.
- <var translate="no">IP_ADDRESS_1_ID</var> is the ID of the IP address you reserved in the [Reserve IP addresses](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#reserve_ip_addresses_for_network_1) section.
- <var translate="no">NETWORK_1_ID</var> is the ID of your first network.
- <var translate="no">REGION_ID</var> is the region where your Memorystore instance is located.
- <var translate="no">SERVICE_ATTACHMENT_1</var> is the service attachment you noted in [Note the service attachment paths](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#step_2_note_the_service_attachment_paths) listed after the `CONNECTION_TYPE_DISCOVERY` field.
- <var translate="no">PROJECT_1_ID</var> is the ID of project 1. This is the project where your Memorystore instance is located.

By using the optional [--allow-psc-global-access](https://docs.cloud.google.com/sdk/gcloud/reference/compute/forwarding-rules/create.md.txt#--allow-psc-global-access) parameter, clients from all Memorystore for Redis Cluster supported regions can access this forwarding rule.

For example:

```
gcloud compute forwarding-rules create my-forwarding-rule-1 \
--address=my-ip-address-1 \
--network=projects/my-project-1/global/networks/my-network-1 \
--region=us-central1 \
--target-service-attachment=projects/1048073346231/regions/us-central1/serviceAttachments/gcp-memorystore-auto-a0583920-edef-42-psc-sa \
--project=my-project-1 \
--allow-psc-global-access
```

##### Add forwarding rule 2 for IP 2

### gcloud

To add a forwarding rule for IP 2, run the `gcloud compute forwarding-rules create`
command:

```
gcloud compute forwarding-rules create FORWARDING_RULE_2_NAME \
--address=IP_ADDRESS_2_ID \
--network=projects/PROJECT_1_ID/global/networks/NETWORK_1_ID \
--region=REGION_ID \
--target-service-attachment=SERVICE_ATTACHMENT_2 \
--project=PROJECT_1_ID \
--allow-psc-global-access
```

Replace the following:

- <var translate="no">FORWARDING_RULE_2_NAME</var> is the name you give to the forwarding rule you are creating.
- <var translate="no">IP_ADDRESS_2_ID</var> is the ID of the IP address you reserved in the [Reserve IP addresses](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#reserve_ip_addresses_for_network_1) section.
- <var translate="no">NETWORK_1_ID</var> is the ID of your first network.
- <var translate="no">REGION_ID</var> is the region where your Memorystore instance is located.
- <var translate="no">SERVICE_ATTACHMENT_2</var> is the second service attachment you noted in [Note the service attachment paths](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#step_2_note_the_service_attachment_paths).
- <var translate="no">PROJECT_1_ID</var> is the ID of project 1. This is the project where your Memorystore instance is located.

By using the optional [--allow-psc-global-access](https://docs.cloud.google.com/sdk/gcloud/reference/compute/forwarding-rules/create.md.txt#--allow-psc-global-access) parameter, clients from all Memorystore for Redis Cluster supported regions can access this forwarding rule.

For example:

```
gcloud compute forwarding-rules create my-forwarding-rule-2 \
--address=my-ip-address-2 \
--network=projects/my-project-1/global/networks/my-network-1 \
--region=us-central1 \
--target-service-attachment=projects/1048073346231/regions/us-central1/serviceAttachments/gcp-memorystore-auto-a0583920-edef-42-psc-sa-2 \
--project=my-project-1 \
--allow-psc-global-access
```

### Register Private Service Connect connections with your Memorystore instance for network 1

This section shows the steps to follow to register connections with your
Memorystore instance. First, you need to get the connection IDs
and project IDs of your forwarding rules.

Then, you will enable connectivity by registering the
Private Service Connect connection information with your
Memorystore instance.

#### Get the forwarding rule connection IDs and project IDs for network 1

Next, get the `pscConnectionId` value for each forwarding rule. Make a note of
the values.

##### Get Private Service Connect connection ID 1

### gcloud

To see the `pscConnectionId` value and other forwarding rule summary
information, run the `gcloud compute forwarding-rules describe` command:

```
gcloud compute forwarding-rules describe FORWARDING_RULE_1_NAME \
--project=PROJECT_1_ID \
--region=REGION_ID
```

Replace the following:

- <var translate="no">FORWARDING_RULE_1_NAME</var> is the name of your first forwarding rule.
- <var translate="no">PROJECT_1_ID</var> is the ID of the Google Cloud project that contains the forwarding rule.

The following example shows a sample output for this command:

```
gcloud compute forwarding-rules describe my-forwarding-rule-1 \
--project=my-project-1 \
--region=us-central1

...

pscConnectionId: '415109836469698'
```

##### Get Private Service Connect connection ID 2

### gcloud

To see the `pscConnectionId` value and other forwarding rule summary
information, run the `gcloud compute forwarding-rules describe` command:

```
gcloud compute forwarding-rules describe FORWARDING_RULE_2_NAME \
--project=PROJECT_1_ID \
--region=REGION_ID
```

Replace the following:

- <var translate="no">FORWARDING_RULE_2_NAME</var> is the name of your second forwarding rule.
- <var translate="no">PROJECT_1_ID</var> is the ID of the Google Cloud project that contains the forwarding rule.

#### Register Private Service Connect connection information for VPC network 1

### gcloud

To register each connection, you'll provide the
Private Service Connect connection ID, IP address, network
path, forwarding rule path/URI, and the target service attachment. Do this by
running the `gcloud redis clusters add-cluster-endpoints` command:

```
gcloud redis clusters add-cluster-endpoints INSTANCE_ID \
--region=REGION_ID \
--project=PROJECT_1_ID \
--cluster-endpoint='["psc-connection":[{"psc-connection-id":"PSC_CONNECTION_1_ID","address":"IP_ADDRESS_1","network":"projects/PROJECT_1_ID/global/networks/NETWORK_1_ID","forwarding-rule":"projects/PROJECT_1_ID/regions/REGION_ID/forwardingRules/FORWARDING_RULE_1_NAME","service-attachment":"SERVICE_ATTACHMENT_1"},{"psc-connection-id":"PSC_CONNECTION_2_ID","address":"IP_ADDRESS_2","network":"projects/PROJECT_1_ID/global/networks/NETWORK_1_ID","forwarding-rule":"projects/PROJECT_1_ID/regions/REGION_ID/forwardingRules/FORWARDING_RULE_2_NAME","service-attachment":"SERVICE_ATTACHMENT_2"}]]'
```

Replace the following:

- <var translate="no">INSTANCE_ID</var> is the ID of your Memorystore for Redis Cluster instance.
- <var translate="no">REGION_ID</var> is the ID of the region where your Memorystore instance is located.
- <var translate="no">PROJECT_1_ID</var> is the ID of project 1. This is the project where your Memorystore instance is located.
- <var translate="no">PSC_CONNECTION_1_ID</var> is the first Private Service Connect connection ID that you noted in the [Getting forwarding rule connection IDs](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#get_the_forwarding_rule_connection_ids_and_project_ids_for_network_1) section.
- <var translate="no">IP_ADDRESS_1</var> is the address of the first IP address you reserved.
- <var translate="no">NETWORK_1_ID</var> is the ID of Network 1.
- <var translate="no">FORWARDING_RULE_1_NAME</var> is the name of the first forwarding rule you created.
- <var translate="no">SERVICE_ATTACHMENT_1</var> is your first service attachment that `FORWARDING_RULE_1_NAME` is connected with.
- <var translate="no">PSC_CONNECTION_2_ID</var> is the second Private Service Connect connection ID you noted when [Getting forwarding rule connection IDs](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#get_the_forwarding_rule_connection_ids_and_project_ids_for_network_1).
- <var translate="no">IP_ADDRESS_2</var> is the address of the second IP address you reserved.
- <var translate="no">FORWARDING_RULE_2_NAME</var> is the name of the second forwarding rule you created.
- <var translate="no">SERVICE_ATTACHMENT_2</var> is your second service attachment that `FORWARDING_RULE_2_NAME` is connected with.

For example:

```
gcloud redis clusters add-cluster-endpoints my-instance \
--region=us-central-1 \
--project=my-project1 \
--cluster-endpoint='["psc-connection":[{"psc-connection-id":"41510983646969883","address":"10.2.5.9","network":"projects/my-project-1/global/networks/my-network-1","forwarding-rule":"projects/1048073346231/regions/us-central1/forwardingRules/my-forwarding-rule-1","service-attachment":"projects/1048073346231/regions/us-central1/serviceAttachments/gcp-memorystore-auto-8d7d48ef-3ca3-4d-psc-sa"},{"psc-connection-id":"41510983646969234","address":"10.2.5.11","network":"projects/my-project-1/global/networks/my-network-1","forwarding-rule":"projects/my-project-1/regions/us-central1/forwardingRules/my-forwarding-rule-2","service-attachment":"projects/1048073346231/regions/us-central1/serviceAttachments/gcp-memorystore-auto-8d7d48ef-3ca3-4d-psc-sa-2"}]]'
```

## Step 4: Set up and register Private Service Connect connections for your second VPC network

This section shows you how to set up the two connections required for your
second VPC network.

### Create the Private Service Connect endpoints for network 2

This section explains the actions you need to take to create 2 endpoints in
Network 2.

#### Reserve IP addresses for network 2

Next, reserve 2 IP addresses in network 2.

##### Reserve IP address 3

### gcloud

To reserve IP address 3, run the `gcloud compute addresses create` command:

```
gcloud compute addresses create IP_ADDRESS_3_ID \
--project=PROJECT_2_ID \
--addresses=IP_ADDRESS_3 \
--region=REGION_ID \
--subnet=projects/PROJECT_2_ID/regions/REGION_ID/subnetworks/SUBNET_2_ID \
--purpose=GCE_ENDPOINT
```

Replace the following:

- <var translate="no">IP_ADDRESS_3_ID</var> is the ID you give to your IP address.
- <var translate="no">PROJECT_2_ID</var> is the ID of project 2. This is the project where you create the second VPC network and subnetwork.
- <var translate="no">IP_ADDRESS_3</var> is an IP address of your choosing from within the `SUBNET_2_ID` range you reserved as a part of [Prerequisite resources](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#prerequisite_resources).
- <var translate="no">REGION_ID</var> is the region where your Memorystore instance is located.
- <var translate="no">SUBNET_2_ID</var> is the ID of the subnetwork you reserved on network 2 in project 2 as a part of [Prerequisite resources](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#prerequisite_resources).

##### Reserve IP address 4

### gcloud

To reserve IP address 4, run the `gcloud compute addresses create` command:

```
gcloud compute addresses create IP_ADDRESS_4_ID \
--project=PROJECT_2_ID \
--addresses=IP_ADDRESS_4 \
--region=REGION_ID \
--subnet=projects/PROJECT_2_ID/regions/REGION_ID/subnetworks/SUBNET_2_ID \
--purpose=GCE_ENDPOINT
```

Replace the following:

- <var translate="no">IP_ADDRESS_4_ID</var> is the ID you give to your IP address.
- <var translate="no">PROJECT_2_ID</var> is the ID of project 2. This is the project where you create the second VPC network and subnetwork.
- <var translate="no">IP_ADDRESS_4</var> is an IP address of your choosing from within the `SUBNET_2_ID` range you reserved as a part of [Prerequisite resources](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#prerequisite_resources).
- <var translate="no">REGION_ID</var> is the region where your Memorystore instance is located.
- <var translate="no">SUBNET_2_ID</var> is the ID of the subnetwork you reserved on network 2 in project 2 as a part of [Prerequisite resources](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#prerequisite_resources).

#### Add forwarding rules for network 2

Next, create forwarding rules that connect the IP addresses to the
Memorystore instance's service attachments.

##### Add forwarding rule 3 for IP 3

### gcloud

To add a forwarding rule for IP 3, run the `gcloud compute forwarding-rules create`
command:

```
gcloud compute forwarding-rules create FORWARDING_RULE_3_NAME \
--address=IP_ADDRESS_3_ID \
--network=projects/PROJECT_2_ID/global/networks/NETWORK_2_ID \
--region=REGION_ID \
--target-service-attachment=SERVICE_ATTACHMENT_1 \
--project=PROJECT_2_ID \
--allow-psc-global-access
```

Replace the following:

- <var translate="no">FORWARDING_RULE_3_NAME</var> is the name you give to the forwarding rule you are creating.
- <var translate="no">IP_ADDRESS_3_ID</var> is the ID of the IP address you reserved in the [Reserve IP addresses](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#reserve_ip_addresses_for_network_2) section.
- <var translate="no">NETWORK_2_ID</var> is the ID of your second network.
- <var translate="no">REGION_ID</var> is the region where your Memorystore instance is located.
- <var translate="no">SERVICE_ATTACHMENT_1</var> is the first service attachment you noted in [Note the service attachment paths](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#step_2_note_the_service_attachment_paths).
- <var translate="no">PROJECT_2_ID</var> is your second project.

By using the optional [--allow-psc-global-access](https://docs.cloud.google.com/sdk/gcloud/reference/compute/forwarding-rules/create.md.txt#--allow-psc-global-access) parameter, clients from all Memorystore for Redis Cluster supported regions can access this forwarding rule.

For example:

```
gcloud compute forwarding-rules create my-forwarding-rule-3 \
--address=my-ip-address-3 \
--network=projects/my-project-2/global/networks/my-network-2 \
--region=us-central1 \
--target-service-attachment=projects/1048073346231/regions/us-central1/serviceAttachments/gcp-memorystore-auto-a0583920-edef-42-psc-sa \
--project=my-project-2 \
--allow-psc-global-access
```

##### Add forwarding rule 4 for IP 4

### gcloud

To add a forwarding rule for IP 4, run the `gcloud compute forwarding-rules create`
command:

```
gcloud compute forwarding-rules create FORWARDING_RULE_4_NAME \
--address=IP_ADDRESS_4_ID \
--network=projects/PROJECT_2_ID/global/networks/NETWORK_2_ID \
--region=REGION_ID \
--target-service-attachment=SERVICE_ATTACHMENT_2 \
--project=PROJECT_2_ID \
--allow-psc-global-access
```

Replace the following:

- <var translate="no">FORWARDING_RULE_4_NAME</var> is the name you give to the forwarding rule you are creating.
- <var translate="no">IP_ADDRESS_4_ID</var> is the ID of the IP address you reserved in the [Reserve IP addresses](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#reserve_ip_addresses_for_network_2) section.
- <var translate="no">NETWORK_2_ID</var> is the ID of your second network.
- <var translate="no">REGION_ID</var> is the region where your Memorystore instance is located.
- <var translate="no">SERVICE_ATTACHMENT_2</var> is the second service attachment you noted in [Note the service attachment paths](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#step_2_note_the_service_attachment_paths).
- <var translate="no">PROJECT_2_ID</var> is your second project.

By using the optional [--allow-psc-global-access](https://docs.cloud.google.com/sdk/gcloud/reference/compute/forwarding-rules/create.md.txt#--allow-psc-global-access) parameter, clients from all Memorystore for Redis Cluster supported regions can access this forwarding rule.

For example:

```
gcloud compute forwarding-rules create my-forwarding-rule-4 \
--address=my-ip-address-4 \
--network=projects/my-project-2/global/networks/my-network-2 \
--region=us-central1 \
--target-service-attachment=projects/1048073346231/regions/us-central1/serviceAttachments/gcp-memorystore-auto-a0583920-edef-42-psc-sa-2 \
--project=my-project-2 \
--allow-psc-global-access
```

### Register Private Service Connect connections with your Memorystore instance for network 2

This section shows the steps to follow to register connections with your
Memorystore instance. First, you need to get the connection IDs
and project IDs of your forwarding rules.

Then, you will enable connectivity by registering the
Private Service Connect connection information with your
Memorystore instance.

#### Get the forwarding rule connection IDs and project IDs for network 2

Next, get the `pscConnectionId` value for each forwarding rule. Make a note of
the values.

##### Get Private Service Connect connection ID 3

### gcloud

To see the `pscConnectionId` value and other forwarding rule summary
information, run the `gcloud compute forwarding-rules describe` command:

```
gcloud compute forwarding-rules describe FORWARDING_RULE_3_NAME \
--project=PROJECT_2_ID \
--region=REGION_ID
```

Replace the following:

- <var translate="no">FORWARDING_RULE_3_NAME</var> is the name of your third forwarding rule.
- <var translate="no">PROJECT_2_ID</var> is the ID of the Google Cloud project that contains the forwarding rule.

The following example shows a sample output for this command:

```
gcloud compute forwarding-rules describe my-forwarding-rule-3 \
--project=my-project-2 \
--region=us-central1

...

pscConnectionId: '94710983646969729'
```

##### Get Private Service Connect connection ID 4

### gcloud

To see the `pscConnectionId` value and other forwarding rule summary
information, run the `gcloud compute forwarding-rules describe` command:

```
gcloud compute forwarding-rules describe FORWARDING_RULE_4_NAME \
--project=PROJECT_2_ID \
--region=REGION_ID
```

Replace the following:

- <var translate="no">FORWARDING_RULE_4_NAME</var> is the name of your fourth forwarding rule.
- <var translate="no">PROJECT_2_ID</var> is the ID of the Google Cloud project that contains the forwarding rule.

#### Register Private Service Connect connection information for VPC network 2

### gcloud

To register each connection, you'll provide the
Private Service Connect connection ID, IP address, network
path, forwarding rule path/URI, and the target service attachment. Do this by
running the `gcloud redis clusters add-cluster-endpoints` command:

```
gcloud redis clusters add-cluster-endpoints INSTANCE_ID \
--region=REGION_ID \
--project=PROJECT_1_ID \
--cluster-endpoint='["psc-connection":[{"psc-connection-id":"PSC_CONNECTION_3_ID","address":"IP_ADDRESS_3","network":"projects/PROJECT_2_ID/global/networks/NETWORK_2_ID","forwarding-rule":"projects/PROJECT_2_ID/regions/REGION_ID/forwardingRules/FORWARDING_RULE_3_NAME","service-attachment":"SERVICE_ATTACHMENT_1"},{"psc-connection-id":"PSC_CONNECTION_4_ID","address":"IP_ADDRESS_4","network":"projects/PROJECT_2_ID/global/networks/NETWORK_2_ID","forwarding-rule":"projects/PROJECT_2_ID/regions/REGION_ID/forwardingRules/FORWARDING_RULE_4_NAME","service-attachment":"SERVICE_ATTACHMENT_2"}]]'
```

Replace the following:

- <var translate="no">INSTANCE_ID</var> is the ID of your Memorystore for Redis Cluster instance.
- <var translate="no">REGION_ID</var> is the ID of the region where your Memorystore instance is located.
- <var translate="no">PROJECT_1_ID</var> is the ID of project 1. This is the project where your Memorystore instance is located.
- <var translate="no">PROJECT_2_ID</var> is the ID of project 2. This is the project where you create the second VPC network and subnetwork.
- <var translate="no">PSC_CONNECTION_3_ID</var> is the Private Service Connect connection 3 you noted when [Getting forwarding rule connection IDs for network 2](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#get_the_forwarding_rule_connection_ids_and_project_ids_for_network_2).
- <var translate="no">IP_ADDRESS_3</var> is the address of the third IP address you reserved.
- <var translate="no">NETWORK_2_ID</var> is the ID of Network 2.
- <var translate="no">FORWARDING_RULE_3_NAME</var> is the name of the third forwarding rule you created.
- <var translate="no">SERVICE_ATTACHMENT_1</var> is your first service attachment that `FORWARDING_RULE_3_NAME` is connected with.
- <var translate="no">PSC_CONNECTION_4_ID</var> is the Private Service Connect connection 4 you noted when [Getting forwarding rule connection ID for network 2](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#get_the_forwarding_rule_connection_ids_and_project_ids_for_network_2).
- <var translate="no">IP_ADDRESS_4</var> is the address of the fourth IP address you reserved.
- <var translate="no">FORWARDING_RULE_4_NAME</var> is the name of the fourth forwarding rule you created.
- <var translate="no">SERVICE_ATTACHMENT_2</var> is your second service attachment that `FORWARDING_RULE_4_NAME` is connected with.

For example:

```
gcloud redis clusters add-cluster-endpoints my-instance \
--region=us-central-1 \
--project=my-project-1 \
--cluster-endpoint='[psc-connection:[{"psc-connection-id":"94710983646969729","address":"10.142.0.10","network":"projects/my-project-2/global/networks/my-network-2","forwarding-rule":"projects/my-project-2/regions/us-central1/forwardingRules/my-forwarding-rule-3","service-attachment":"projects/1048073346231/regions/us-central1/serviceAttachments/gcp-memorystore-auto-8d7d48ef-3ca3-4d-psc-sa"},{"psc-connection-id":"86510983646969993","address":"10.142.0.12","network":"projects/my-project-2/global/networks/my-network-2","forwarding-rule":"projects/my-project-2/regions/us-central1/forwardingRules/my-forwarding-rule-4","service-attachment":"projects/1048073346231/regions/us-central1/serviceAttachments/gcp-memorystore-auto-8d7d48ef-3ca3-4d-psc-sa-2"}]]'
```

## Step 5: Set up a client connection

This section explains how to configure your client for connectivity for the
networks in this guide.

### Make a note of the Private Service Connect connection endpoint information

Next, make a note of two IP addresses: one for each network you set up in this
tutorial. Each network you set up for Memorystore has a discovery
connection endpoint.

### gcloud

To view Private Service Connect connection endpoint information
for your networks, run the `gcloud redis clusters describe` command:

```
gcloud redis clusters describe INSTANCE_ID \
--region=REGION_ID \
--project=PROJECT_1_ID
```

The output contains a list of `clusterEndpoints`. For each `clusterEndpoint`,
there are two user-registered Private Service Connect
connections.

Make a note of the IP addresses that correspond with the
Private Service Connect connections that have the
`CONNECTION_TYPE_DISCOVERY` type. For these connections,
Memorystore for Redis Cluster adds a `port` field.

For this tutorial, there's one `CONNECTION_TYPE_DISCOVERY` type for each of
the two networks that you set up.

For example, here is a piece of sample output from the `gcloud redis clusters describe`
command that contains the IP address you should write down:

    clusterEndpoints:
    - connections:
      - pscConnection:
          address: 10.x.x.x
          connectionType: CONNECTION_TYPE_DISCOVERY
          forwardingRule: projects/my-project-1/regions/us-east1/forwardingRules/fw3
          network: projects/my-project-1/global/networks/default
          projectId: my-project-1
          pscConnectionId: '44476954917601283'
          pscConnectionStatus: PSC_CONNECTION_STATUS_ACTIVE
          serviceAttachment: projects/503459599638/regions/us-east1/serviceAttachments/gcp-memorystore-auto-7312b29e-00b3-4b-psc-sa
      - pscConnection:
          address: 10.x.x.x
          forwardingRule: projects/my-project-1/regions/us-east1/forwardingRules/fw4
          network: projects/my-project-1/global/networks/default
          projectId: my-project-1
          pscConnectionId: '44476954917601284'
          pscConnectionStatus: PSC_CONNECTION_STATUS_ACTIVE
          serviceAttachment: projects/503459599638/regions/us-east1/serviceAttachments/gcp-memorystore-auto-7312b29e-00b3-4b-psc-sa-2

To get the discovery IP address in the endpoints list, look for the
`CONNECTION_TYPE_DISCOVERY` connection type.

### Configure your client

Next, configure your client as follows:

- Configure client connections in network 1 using the discovery IP in network 1.
  This is the IP address you noted in the previous step. For the example given in
  this tutorial, the value is `10.2.5.09`.

- Configure client connections in network 2 using the discovery IP in network 2.
  This is the IP address you noted in the previous step. For the example given in
  this tutorial, the value is `10.142.0.10`.

For instructions on connecting to a Memorystore instance, see
[Connect from a Compute Engine VM using redis-cli](https://docs.cloud.google.com/memorystore/docs/cluster/connect-cluster-instance.md.txt#connect_from_a_compute_engine_vm_using_redis_cli).

### Allow ports on your firewall

If you don't allow the correct ports on your firewall, then your cluster might
encounter connection errors because the firewall might block the ports that
Memorystore for Redis Cluster uses.

For all of your cluster's Private Service Connect endpoints, you must
allow TCP port 6379, as well as TCP ports 11000 through 13047. For more
information, see [Troubleshoot issues](https://docs.cloud.google.com/memorystore/docs/cluster/troubleshoot-issues.md.txt#connection_error_caused_by_firewall_rules).

## Delete your Private Service Connect connections

Before you can [Delete your Memorystore instance](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#delete_your_memorystore_for_redis_cluster_instance),
you must delete all Private Service Connect connections
associated with the instance. To do this, you must delete the forwarding rules
and deregister the endpoints that you set up in this tutorial. This section
guides you through deleting all of the forwarding rules first, then
deregistering the endpoints. However, if you choose, you can delete forwarding
rules and deregister endpoints for one network at a time.

Also, you can optionally delete the reserved IP addresses to release them for
future use if you choose.

### Delete forwarding rules

This section gives instructions on deleting the forwarding rules you created
previously in this tutorial.

#### Delete forwarding rule 1

### gcloud

To delete a forwarding rule, run the [`gcloud compute forwarding-rules delete`](https://docs.cloud.google.com/sdk/gcloud/reference/compute/forwarding-rules/delete.md.txt) command:

```
gcloud compute forwarding-rules delete FORWARDING_RULE_1_NAME \
--region=REGION_ID \
--project=PROJECT_1_ID
```

Replace the following:

- <var translate="no">FORWARDING_RULE_1_NAME</var> is the name of your first forwarding rule.
- <var translate="no">PROJECT_1_ID</var> is the ID of project 1. This is the project where your Memorystore instance is located.

#### Delete forwarding rule 2

### gcloud

To delete a forwarding rule, run the [`gcloud compute forwarding-rules delete`](https://docs.cloud.google.com/sdk/gcloud/reference/compute/forwarding-rules/delete.md.txt) command:

```
gcloud compute forwarding-rules delete FORWARDING_RULE_2_NAME \
--region=REGION_ID \
--project=PROJECT_1_ID
```

Replace the following:

- <var translate="no">FORWARDING_RULE_2_NAME</var> is the name of your second forwarding rule.
- <var translate="no">PROJECT_1_ID</var> is the ID of project 1. This is the project where your Memorystore instance is located.

#### Delete forwarding rule 3

### gcloud

To delete a forwarding rule, run the [`gcloud compute forwarding-rules delete`](https://docs.cloud.google.com/sdk/gcloud/reference/compute/forwarding-rules/delete.md.txt) command:

```
gcloud compute forwarding-rules delete FORWARDING_RULE_3_NAME \
--region=REGION_ID \
--project=PROJECT_2_ID
```

Replace the following:

- <var translate="no">FORWARDING_RULE_3_NAME</var> is the name of your third forwarding rule.
- <var translate="no">PROJECT_2_ID</var> is the ID of project 2. This is the project where you create the second VPC network and subnetwork.

#### Delete forwarding rule 4

### gcloud

To delete a forwarding rule, run the [`gcloud compute forwarding-rules delete`](https://docs.cloud.google.com/sdk/gcloud/reference/compute/forwarding-rules/delete.md.txt) command:

```
gcloud compute forwarding-rules delete FORWARDING_RULE_4_NAME \
--region=REGION_ID \
--project=PROJECT_2_ID
```

Replace the following:

- <var translate="no">FORWARDING_RULE_4_NAME</var> is the name of your fourth forwarding rule.
- <var translate="no">PROJECT_2_ID</var> is the ID of project 2. This is the project where you create the second VPC network and subnetwork.

### Deregister your Private Service Connect endpoints

This section provides instructions for deregistering the
Private Service Connect endpoints that you
[registered earlier in this tutorial](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#register_psc_connection_information_for_vpc_network_1).

#### Deregister endpoints for VPC networks 1 and 2

### gcloud

To deregister the endpoint information with the Memorystore
instance, run the `gcloud redis clusters remove-cluster-endpoints` command.

```
gcloud redis clusters remove-cluster-endpoints INSTANCE_ID \
--region=REGION_ID \
--project=PROJECT_1_ID \
--cluster-endpoint='["psc-connection":[{"psc-connection-id":"PSC_CONNECTION_1_ID"},{"psc-connection-id":"PSC_CONNECTION_2_ID"}]]' \
--cluster-endpoint='["psc-connection":[{"psc-connection-id":"PSC_CONNECTION_3_ID"},{"psc-connection-id":"PSC_CONNECTION_4_ID"}]]'
```

Replace the following:

- <var translate="no">INSTANCE_ID</var> is the ID of the instance for which you are deregistering endpoints.
- <var translate="no">PROJECT_1_ID</var> is the ID of project 1. This is the project where your Memorystore instance is located.
- <var translate="no">REGION_ID</var> is the ID of the region where your Memorystore instance is located.
- <var translate="no">PSC_CONNECTION_1_ID</var> is the first Private Service Connect connection ID you noted when [Getting forwarding rule connection IDs](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#get_the_forwarding_rule_connection_ids_and_project_ids_for_network_1).
- <var translate="no">PSC_CONNECTION_2_ID</var> is the second Private Service Connect connection ID you noted when [Getting forwarding rule connection IDs](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#get_the_forwarding_rule_connection_ids_and_project_ids_for_network_1).
- <var translate="no">PSC_CONNECTION_3_ID</var> is the third Private Service Connect connection ID you noted when [Getting forwarding rule connection IDs](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#get_the_forwarding_rule_connection_ids_and_project_ids_for_network_2).
- <var translate="no">PSC_CONNECTION_4_ID</var> is the fourth Private Service Connect connection ID you noted when [Getting forwarding rule connection IDs](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#get_the_forwarding_rule_connection_ids_and_project_ids_for_network_2).

The preceding command deregisters all connections created in this tutorial. If
you want to only deregister one of the connections, only specify the
connection IDs of the connections you want to remove.

## Delete your Memorystore for Redis Cluster instance

Before you can delete your Memorystore instance, you must
[Deregister your Private Service Connect endpoints](https://docs.cloud.google.com/memorystore/docs/cluster/multiple-vpcs-user-registered-psc-connection.md.txt#deregister_your_private_service_connect_endpoints).

### gcloud

To delete your Memorystore for Redis Cluster instance, run the `gcloud redis clusters delete`
command:

```
gcloud redis clusters delete INSTANCE_ID \
--region=REGION_ID \
--project=PROJECT_1_ID
```

Replace the following:

- <var translate="no">INSTANCE_ID</var> is the ID of your instance.
- <var translate="no">REGION_ID</var> is the ID of the region where your Memorystore instance is located.
- <var translate="no">PROJECT_1_ID</var> is the ID of project 1. This is the project where your Memorystore instance is located.