Create a VPC Endpoint

Preventing the exposure of your traffic outside your VPC and its associated services entails creating endpoints to serve as authorized traffic destinations. This effectively creates an elastic network interface within your subnet where each endpoint’s private IP address serves as entry points for traffic bound to a specific service, such as Dremio. For additional information, see VPC endpoints.

To create a VPC endpoint for Dremio, perform the following steps:

1. Navigate to Virtual Private Cloud > Endpoints.
2. Click Create Endpoint.
3. Under the Service category section, click Find service by name.
4. Enter the Service name, as provided in the table below.
5. Click Verify to ensure the service name is found.
   • If you encounter an issue with the connection, check to ensure the service name is correct. Additionally, make sure your AWS console is in the matching region as the Service name (e.g., US West (Oregon) for us-west-2)
6. Select the desired subnets to support with this endpoint. It is okay if all subnets are selected as over-provisioning won’t prevent access–otherwise select the subnet(s) being used to connect to Dremio.
7. Disable Enable DNS name, unless your organization is specifically configured to use an AWS DNS Private Hosted Zone. If you are unsure, we recommend disabling “Enable DNS name”.
8. Under the Security group section, select or search for the security group you created previously.
9. Click Create Endpoint.

Obtaining the Endpoint ID

Once the endpoint has been created, you’ll need to obtain the Endpoint ID, which is used within Dremio Cloud service to fully configure the route traffic will follow.

To locate your Endpoint ID, perform the following steps:

1. From VPC > Endpoints, locate the endpoint that you created from the list shown. After creating the endpoint, the status for the endpoint may initially display as pending, and may take several minutes to complete. When complete, it will display as available.
2. Click the Subnets tab at the bottom of the screen and verify all associated subnets are fully provisioned and have IPv4 addresses assigned.
3. Copy the Endpoint ID for the endpoint, this is needed later within Dremio Cloud to complete the service’s configuration.

Return to the Cloud setup process with the Endpoint ID. If you are currently configuring a manual installation of Dremio, use this in the Cloud Connection step.

Regional Service Names

Refer to the below chart for the service name that matches the AWS region that you are deploying Dremio Cloud.