The following is a list of prerequisites for configuring the Couchbase DB connector with an Egress Private Service Connect endpoint:
In Confluent Cloud, one of the following cluster types is set up with the specified network resource:
A Dedicated cluster with a Confluent Cloud network
For the steps to create a Confluent Cloud network, see Create a Confluent Cloud network. The Connection type of the network must be Private Service Connect.
In the Network management page or tab of the desired Confluent Cloud environment, click the Confluent Cloud network you want to add the Private Service Connect endpoint to. The Connection Type of the network should be Private Service Connect.
Click Create endpoint in the Egress connections tab.
Click the service you want to connect to, specifically, Couchbase. Select Other if you do not see the specific service.
Follow the steps below to specify the following field values:
Service: Name of service connecting to Couchbase.
Endpoint Name: Name of the Private Service Connect endpoint.
Repeat the steps 2-5 to create a second endpoint for the Bootstrap Service attachment. Add _bootstrap as a suffix in the endpoint name to easily differentiate between the two endpoints.
Note
The GCP Project ID is the same for both endpoints. You only need to add it to Couchbase Capella once in the next step.
In the Network management page or tab of the desired Confluent Cloud environment, click the For serverless products tab.
Click the gateway to which you want to add the Private Service Connect endpoint.
In the Access points tab, click Add access point.
Click the service you want to connect to, specifically, Couchbase. Select Other if you do not see the specific service.
Specific services are listed based on the cloud provider for the gateway.
Follow the steps below to specify the following field values:
Access point name: Name of the Private Service Connect endpoint.
Create an endpoint with high availability: Check the box if you wish to deploy an endpoint with high availability.
Endpoints deployed with high availability have network interfaces deployed in multiple availability zones.
Repeat the steps 3-6 to create a second access point for the Bootstrap Service attachment. Add _bootstrap as a suffix in the access point name to easily differentiate between the two endpoints.
Note
The GCP Project ID is the same for both endpoints. You only need to add it to Couchbase Capella once in the next step.
Step 3. Configure the Couchbase Capella private endpoint
To complete the connection, you must authorize the Confluent Cloud project within the Couchbase Capella console. #. In the Couchbase Capella console, go to the previously created Couchbase private endpoint screen.
When the Private Service Connect endpoint status transitions to Ready, in the Egress connections tab, click Create record on the associated Private Service Connect endpoint.
Repeat these steps to create a DNS record for the second (bootstrap) endpoint, using the corresponding bootstrap DNS name from Couchbase Capella.
In the Network Management tab of your environment, click the For serverless products tab, and click the Confluent Cloud gateway you want to add the DNS record to.
The final step is to configure the connector using the DNS endpoints you established. #. Specify the authentication details for Couchbase.
For the Couchbase Seed Node, specify the Private Endpoint DNS name you retrieved in Step 3. Configure the Couchbase Capella private endpoint and prepend it with the prefix couchbases:// and append ?network=external at the end of the connection string (for example, couchbases://<private-endpoint-dns>?network=external).
Follow the steps to create the source connector in Confluent Cloud.
After the connector is provisioned, contact Confluent Support and provide the Connector Unique ID to enable the network=external parameter in the backend. The connector begins processing data once this backend configuration is complete.
