- Newest
- Most votes
- Most comments
Hello, dependency health check is not a best practices as it can flag your task as irresponsive even in case of an other problem on the database. cf https://aws.amazon.com/builders-library/implementing-health-checks/
Does you code has a fallback on the local socket in case of connection error on the url of the DB ? There are several factors that can make connection to fail on the DB: the number of allowed connections, or the network bandwith that are different dependent of the instance size : https://aws.amazon.com/rds/instance-types/
Hi,
Thank you for contacting us.
Based on the error message we could see that there is some local database dependency in the application due to which it it trying to connect to the database in localhost rather than RDS. If there are no other congestion noted from the container side, please check from the application point to understand more on this.
Thank you.
Relevant content
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago