Connecting Through AWS VPC Endpoint

Hevo provides you with the option of connecting to your Source or Destination database on AWS, such as Amazon RDS or Amazon Aurora, via an AWS VPC endpoint. This option is available only under a business plan.

Note: An AWS VPC endpoint connection is feasible only between VPCs in the same region.

As seen in the image below, to establish a connection between the Hevo platform and your database through an AWS private link using VPC endpoint services, Hevo:

• Creates an intermediate VPC or uses an existing one.

• Creates an endpoint in the intermediate VPC to connect to your VPC endpoint service.

• Communicates with your database through your VPC endpoint service, routing the network traffic via the AWS private link.

The following image illustrates the steps for connecting your Source or Destination database using an AWS VPC endpoint. The steps are also described in detail in the sections below.

---

Initiate VPC Endpoint Connection Request

To create an endpoint in Hevo’s VPC for connecting to your VPC endpoint service, you must contact Hevo Support with the following details obtained from your AWS account:

• Endpoint Service name: The name assigned to the VPC endpoint service created for your database instance. For example, com.amazonaws.vpce.us-east-1.vpce-svc-0ab1abc2ae1c12345a.

• Availability Zone (AZ): The location within your AWS region where the endpoint service is created. For example, us-east-1a in the AWS region, us-east-1.

• Port: The port number on which your endpoint service listens for connections. For example, 3306 for MySQL (Aurora or RDS) databases.

Based on these details, Hevo Support creates a VPC endpoint and provides you with the following information:

• Amazon Resource Name (ARN) for AWS Principals: The AWS account ID (AWS principal) to which you must grant access to your VPC endpoint service. You need to add the ARN as an allowed principal in your VPC endpoint service. For example, arn:aws:iam::112233445566:root, where 112233445566 is the AWS account ID.

• Domain Name System (DNS) Name: The name assigned by AWS to the VPC endpoint created by Hevo. For example, vpce-01e415dzazcc27acd-jq0m02b5.vpce-svc-0ab1abc2ae1c12345a.us-east-1.vpce.amazonaws.com. You must specify the DNS name as the database host while configuring your Source or Destination in Hevo.

• Classless Inter-Domain Routing (CIDR) Range: The IP address range of Hevo’s network in CIDR format. For example, 10.0.0.0/28. You must add this IP address range to your database security group.

---

Accept the VPC Endpoint Connection Request

1. Log in to your Amazon VPC console.

2. At the top right corner of the page, click the region selector to select your region from the drop-down. For example, Asia Pacific (Singapore).

   

3. In the left navigation pane, under Virtual private cloud, click Endpoint services.

   

4. On the Endpoint services page, do the following:

   1. Select the check box next to the Service ID of your VPC endpoint service and then click Endpoint connections.

      

   2. In the Endpoint Connections panel, click the Endpoint ID whose Owner matches the account ID in the ARN obtained in Step 1 above. For example, if the ARN is arn:aws:iam::112233445566:root, the Endpoint ID is the one whose Owner is 112233445566.

   3. Click Actions, and from the drop-down, select Accept endpoint connection request.

      

   4. In the pop-up dialog that appears, enter accept in the confirmation box and click Accept.

      

---

Grant the ARN access to your VPC Endpoint Service

To direct network traffic from Hevo to the database via your VPC endpoint service, you must allow the ARN received in Step 1 to connect to your endpoint service. For this, perform the following steps:

1. Log in to your Amazon VPC console.

2. In the navigation pane, under Virtual private cloud, click Endpoint services.

   

3. On the Endpoint services page, select the check box next to the Service ID of your VPC endpoint service and select the Allow principals tab.

4. In the panel that appears, click Allow principals.

   

5. On the page that opens, do the following:

   

   1. In the Principals to add section, specify the ARN in the following format: arn:aws:iam::<account_ID>:root. Replace the placeholder value with the AWS account ID obtained in Step 1 above. If you need to specify additional ARNs, click Add principal.

   2. Click Allow principals.

---

Add Hevo IP Address Range to your Database Security Group

To allow inbound traffic to your database instance from Hevo, add Hevo’s IP address range to your database’s security group. For this, perform the following steps:

1. Log in to your Amazon VPC console.

2. In the left navigation pane, under Security, click Security groups.

   

3. On the Security Groups page, select the check box next to the Security group ID associated with your database and click Actions.

4. From the Actions drop-down, select Edit inbound rules.

   

5. On the Edit inbound rules page, do the following:

   

   1. Click Add rule.

   2. In the Type column, select the type of your database instance from the drop-down. For example, MYSQL/Aurora.

   3. The Port range column is pre-filled with the port number of your database instance. For example, 3306 for a MySQL/Aurora database.

      Note: This column is non-editable.

   4. In the Source column, select Custom from the drop-down and enter Hevo’s IP address range obtained in Step 1 above.

   5. Click Save rules.

Once you perform the steps above, you can configure your database as a Source or Destination in Hevo. You need to specify the DNS name obtained in Step 1 as your Database Host.

---

Revision History