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.

답변함 일 년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠