Trouble connecting to RDS PostgreSQL Aurora instance in the same VPC

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

Error ‘connection not available’ encountered when trying to connect to RDS PostgreSQL Aurora instance in the same VPC, while plsql connects successfully from the EC2 shell.


Question

help. I cannot connect to my RDS PostgreSQL Aurora instance in the same VPC even though plsql connects without issues from the ec2 shell

airbyte-bootloader error “connection not available”

airbyte-bootloader  | org.jooq.exception.DataAccessException: Error getting connection from data source HikariDataSource (HikariPool-2)```
```# this is working without issues:

psql --host=${DATABASE_HOST} --port=${DATABASE_PORT} --username=${DATABASE_USER} --password --dbname=airbyte```

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1715278743870969) if you want to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["rds-postgresql-aurora", "vpc", "connection-issue", "airbyte-bootloader", "psql"]
</sub>
2

What does the format of your JDBC URL look like in your config? Is this Docker or Kubernetes/Helm?

3

resolved, I overlooked the step where you need to adjust the DATABASE_URL env variable in the .env file that is used by docker-compose

4

You should have known that would happen right after posting . . . feels like it’s always that way for me :joy:

5

if I write it down, the answers come immediately. No matter how much time I spent debugging on my own. lol

6

Time for a <https://en.wikipedia.org/wiki/Rubber_duck_debugging|rubber duck>