Overview

This guide outlines the steps to securely connect your AWS VPC to Quix services using AWS PrivateLink. Quix will provide the necessary details, and you will need to configure your AWS environment accordingly. Click here for AWS documentation.

If you’re looking for exposing services to Quix via AWS PrivateLink, click the following page:

Expose your services via AWS PrivateLink

What You Need to Provide to Quix

Before Quix can set up the service endpoint, please provide the following details:

• Your AWS Account ID (e.g., 123456789012)
• The AWS Region where you want to deploy the endpoint

What Quix Will Provide

Once we receive your details, Quix will provide:

• Service Endpoint Name (e.g., com.amazonaws.vpce.eu-central-1.vpce-svc-05eabcde006fb1a28)
• Entry for private DNS Zone (e.g., *.aws-regi-0.app.quix.io)
• Required Ports for communication (22, 80, 443, private Kafka ports)
• Quix’s AWS Account ID, and Region, in case you need to establish a PrivateLink connection ****in the opposite direction to expose your own services to Quix. (See page above)

Steps to Connect

1. Create a VPC Endpoint

1. Go to AWS Console → VPC → Endpoints → Create Endpoint.
2. Select Endpoint Services that use NLBs and GWLBs
3. Under Service settings enter the Service Endpoint Name provided by Quix.
4. Select the VPC where the Quix service should be accessible.