AWS RDS Database - How to connect

To connect DI to an existing or new Amazon RDS Database, you will have to take several steps.

1. Make sure your Database's "Public accessibility" is set to "Yes" (Click on your RDS Instance -> On the main page, under the "Connectivity& security" tab)
2. Whitelisting our static IP

   1. Click on your VPC security group (as visible above) and click "Edit inbound rules" under the "Actions" dropdown in the top-right corner:
   2. Click "Add rule"
   3. As Type, select "PostgreSQL", enter the port of your DB-Instance (for PostgreSQL usually 5432), and add our static IP + /32 in the "Source" search. If you don't have our static IP yet, please contact us and we will provide it. The IP should look like this: 00.000.00.00/32

   4. If you want, enter something like "Static IP Locoia" into the description, so you'll be able to find and edit this rule easily.

   5. Click "Save rules".

3. If you have outgoing rules set up on your VPC, you might need to repeat this process under the "edit outbound rules" option. By default, your VPC should allow all outgoing traffic.

4. At this point, try connecting to the database in DI. Most likely, you won't have to do anything else.

5. If you still encounter issues connecting to your DB instance, try checking your VPC settings:

   1. On the same screen as in step 1, under "Networking", click onto the name of your VPC instance:
   2. In the overview, click on the ID of your VPC:
   3. On the next screen, under the "Details" tab, click on the "Main Network ACL":
   4. Just like in step 2, use the "Action" drop-down in the top right corner to check your inbound and outbound rules. By default, they should look like this: The "Allow" rule needs to be located above the "Deny" rule in order to work. If you have stricter rules set up, white-label our IP similar to step 2.
6. You should now be able to connect to your database instance! In case you are still experiencing issues, try connecting to your database through a different tool (such as pgAdmin) from a whitelisted IP to ensure your database is exposed as intended. If you are unable to connect, please discuss with your sysadmin, as your organization might enforce even stricter rules on RDS. If you are able to connect from a 3rd-party tool, but can't connect from DI, please contact us so we can investigate the issue.