EC2 instance was terminated, with new instance running, appears to be a problem with DB

0

For some reason, out of nowhere AWS autoscale decided to shut down our EC2 instance and a new one was launched, but now, even if our Backend is up and running on an ECS cluster container and the DB is running on RDS, there seems like our DB is unreachable, meaning on my website/application appears that the DB is offline. I have admin privileges, but I did not setup AWS, I just suppose to 'maintain' it and although im not completely clueless I'm not expert in the field. I'm unable to figure out what causing our issue. Security groups, and VPC are all setup correctly, havent touched it, all that got sorted automatically with the new autoscale group/template launch. If anyone could direct me or suggest some basic troubleshooting options(even though I feel like i checked most of them but still) that would help, would be much appreciated. Thanks, Csaba

1 回答
0
已接受的回答

Okay if ever someone to run into such, the problem was that at EC2 Load Balancing/Target Groups were not associated with the new instance.

已回答 1 年前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则