Skip to main content

Access VeloDB Cloud from Your VPC on AWS

Before you begin, read Access VeloDB Cloud from your VPC for the connection direction, ownership model, and network-control scope. This procedure applies to SaaS warehouses and uses AWS PrivateLink to create an interface endpoint in your virtual private cloud (VPC).

Make sure that you can create VPC endpoints, select subnets and security groups, and configure private DNS in the AWS account that contains the client applications.

  1. Log in to the VeloDB Cloud console. In the upper-left corner, select the warehouse that you want to use, then click Connection in the left navigation pane. Select Private Endpoint > Access VeloDB from Your VPC, and then click Set up Connection.

  2. Click Set up one or more endpoints to open the AWS VPC console and create an endpoint.

  3. In the AWS VPC console, switch to the AWS Region that matches the warehouse region. AWS PrivateLink is region-scoped. On Endpoints, click Create endpoint to open the form.

    private link create endpoint on aws

    Note:

    Log in to AWS with a principal that is allowed to access the VeloDB Cloud endpoint service. Otherwise, service-name verification fails.

  4. Fill in the endpoint form:

    private link create endpoint on aws01

    private link create endpoint on aws02

    ParameterDescription
    Name tagOptional. Tag with key Name and a value of your choice.
    Service categoryRequired. Select Endpoint services that use NLBs and GWLBs.
    Service nameRequired. Copy the Endpoint Service Name from the Supporting Information section of the VeloDB Cloud console, paste it here, and click Verify service.
    VPCRequired. The VPC to create the endpoint in.
    SubnetsRequired. Select one or more suitable subnets in Availability Zones supported by the VeloDB Cloud endpoint service.
    Security groupsRequired. The rules must allow the protocol and port used by the warehouse and the source IP of your application.
    TagsOptional.

    After completing the form, click Create endpoint to submit it.

  5. Wait for the endpoint status to change from Pending to Available. If the endpoint service requires approval, it remains pending until VeloDB Cloud accepts the connection. The connection is ready only after the status is Available.

    private link create endpoint on aws pending

  6. Return to VeloDB Cloud. If the Set up Connection dialog is closed, open Connection > Private Endpoint > Access VeloDB from Your VPC, and then click Set up Connection. Under Endpoint Information, enter the Endpoint ID. Optionally enter a Description, and then click Save.

  7. Refresh the page, then open Connection > Private Endpoint > Access VeloDB from Your VPC. Locate the row by its Endpoint ID, and verify the Endpoint DNS Name.

  8. In the endpoint row, select the connection option for your client, and then copy the connection details from the dialog.

  1. Configure your client with the copied connection details.

After the endpoint is ready, use Connection Methods to connect an application.

See also​

On This Page