I'm relatively new to backend development and AWS, so sorry if my question sounds basic. I'm running a Node.js and Express backend using the `pg` Pool to connect to AWS RDS PostgreSQL. I've set it up with SSL using the AWS CA bundle (`global-bundle.pem`), and all the credentials and configurations are correct since `pgAdmin` connects without any problems. I'm developing in WSL2.
Here's my connection setup:
```javascript
const pool = new Pool({
host: process.env.DB_HOST,
port: process.env.DB_PORT,
user: process.env.DB_USER,
password: process.env.DB_PASSWORD,
database: process.env.DB_DATABASE,
ssl: {
rejectUnauthorized: true,
ca: fs.readFileSync('src/config/certs/global-bundle.pem').toString(),
},
});
```
What I'm experiencing are random connection timeouts that occur every now and then, but then it will connect just fine. This issue happens regardless of whether I use `nodemon` or `node server.js`, and sometimes the RDS instance logs this message: `pgsqlCopyEdit LOG: could not receive data from client: Connection reset by peer`. I thought the SSL might be causing it, which is why I included it.
So, I'm asking:
- What could be the main issue here, considering my credentials and security groups are set correctly?
- Am I trying to connect too quickly after the process starts?
- How can I make the connection more reliable?
Any help would be appreciated!
2 Answers
You mentioned your RDS instance is public, so check if your IP is being blocked or if the inbound rules are too restrictive for the RDS connections. Also, consider adjusting your connection pool settings; tweaking the max pool size and idle timeout may improve stability. Lastly, ensure you're using the latest version of the `pg` library, as newer versions often contain valuable bug fixes.
It sounds like there could be a few issues at play. First, verify if your Node.js application is trying to connect to the database before it's fully initialized. You might want to introduce a delay before your first connection attempt to see if that helps. Secondly, check your security groups; occasionally the connection resets can be linked to timeout issues with the firewall settings. You might want to tweak those timeout settings and see if it makes a difference.
Thanks for the tips! I'll try adding a connection delay and revisiting the security group settings to see if that resolves the issue.
I did update my `pg` library recently, but I’ll take a look at the connection pool settings. Appreciate the advice!