This guide outlines the steps to expose your GCP services to Quix using GCP Private Service Connect. By setting up a Private Service Connect endpoint, Quix can securely connect to your service without requiring public internet access. Click here for GCP documentation.

What Quix Will Provide

Once we receive your details, Quix will provide:

• The GCP Region your private compute is located in and you will expose to
• The Project ID you can pre-approve

Steps to Expose Your Service

1. Publish Service with Private Service Connect

1. Go to GCP Console → Private Service Connect → Publish Service
2. Select Type and fill details
3. Select the GCP Region Quix provided.
4. Configure the connection preferences:
   1. Enable Accept connections for selected projects
   2. Under Accepted Projects enter the Project ID Quix provided
   3. Set a maximum number of connections to 1
5. Under Advanced Configuration set the domain name you wish to access this service at
6. Add Service
7. Share the following details with Quix:
   • Target Service URI (e.g., projects/your-project-id/regions/us-central1/serviceAttachments/your-service)
   • Required Ports for communication with Quix. If no specific ports are provided, we will assume unrestricted access.

2. Quix Requests a Private Service Connect Endpoint

1. Quix will create a Private Service Connect Endpoint in our GCP project using the Target Service URI you provided.
2. If you pre-approved the Project ID Quix provided (step 1.4.a), there is nothing to do. Otherwise you will receive a connection request in your GCP Console to approve.
   1. Go to GCP Console → Private Service Connect → Connected endpoints.
   2. Select the pending endpoint.
   3. Select project
   4. Accept Project

4. Validate the Connection

Once the connection is established, please provide Quix with an address that we can use to verify connectivity. We will test the connection to ensure proper routing and accessibility.

Support