Secure Database Connection (AWS)
This document explains the steps required to securely access your AWS RDS instance and load data into the Qrvey Business Analytics platform.
Prerequisites
- Qrvey's Business Analytics platform (v5.0+) is deployed in your AWS account.
- An RDS instance is accessible via a security group.
VPC Peering Steps
Background
VPC Peering is necessary if your RDS instance is in a different VPC, account, or region.
- Ensure the VPC your database resides in has a different IPv4 CIDR range than the VPC configured for Qrvey. You can view the IPv4 CIDR range in the VPC Console of your AWS account. Note this IPv4 CIDR range for later use. The IP range must not overlap with
172.31.0.0/16
. - In the left panel, select Peering Connections:
- a. Click Create Peering Connection.
- b. For VPC (Requester), select the VPC your database resides in.
- c. For VPC (Accepter), select the default VPC where Qrvey is installed.
- d. Confirm by clicking Create Peering Connection.
- Modify the routing table(s) for your database VPC:
- a. For each routing table with the same VPC ID, follow these steps:
- i. Select Routes.
- ii. Click Edit routes.
- iii. Click Add route.
- iv. Set Destination to
172.31.0.0/16
and Target to the Peering Connection created in step 2. - v. Click Save routes.
- a. For each routing table with the same VPC ID, follow these steps:
- Modify the routing table(s) for the default VPC where Qrvey is installed:
- a. For each routing table with the same VPC ID, follow these steps:
- i. Select Routes.
- ii. Click Edit routes.
- iii. Click Add route.
- iv. Set Destination to the IPv4 CIDR range noted in step 1, and Target to the Peering Connection created in step 2.
- v. Click Save routes.
- a. For each routing table with the same VPC ID, follow these steps:
- Add a new inbound rule to the RDS security group to allow traffic from the Qrvey Account CIDR.
- Enable DNS resolution for VPC peering on both the Requester and Accepter sides.
You can now follow the steps to connect Qrvey to your RDS instance.