Postgres RDS Proxy stopped working at 5am

0

At around 05:00 RDS Proxy for Postgres suddenly stopped functioning after working seamlessly since June. Doing a describe on the CLI against the RDS Proxy target it said it had failed due to an internal error. Wondering if anyone else has seen similar in eu-west-1 this morning?

We tried destroying the proxy and recreating it, and while the console and CLI show the proxy target as available, it doesn't work. We can see in Wireshark and application logs that the Proxy is returning an 08000 error "Timed-out waiting to acquire database connect". Occasionally if you spam the proxy enough you will get a connection through. The RDS proxy is in the same security group as the database itself, and for now we have the applications bypassing the RDS Proxy and just going straight to the databases as a workaround and that's fine.

Also worth mentioning that other accounts provisioned in the same way are working okay.

已提問 2 年前檢視次數 290 次
1 個回答
1

Please check the Postgres utilization during that period also check for any long running transactions which might cause database to stop accepting connections. 08000 is postgres specific error.

AWS
已回答 1 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南