Amazon Web Services 503 error

Question

We have been trouble shooting a 503 error stating servers are at capacity.

we have removed the potential problems after monitoring the time stamp of the occurence. Everything tests healthy in our dashboard, we stopped instances and restarted them, as well as creating new instances to see if that would help. It is not a big website so we are nowhere near capacity..

Sorry On to the question...Has anybody run into this problem and how did they go about trouble shooting beyond what we have already done.

Thanks,

Answer 1

Found the answer...When we created our new AMI in AWS for our new Instance. We had an AMI that had the same image and no code deployment. So the two AMI's cancelled eachother out and our load balancer just stopped and didn't serv up anything else...

We had to Terminate the AMI, stop and restart the app instances and the and most importantly had to go to code deployment and re deploy the code.

Hope this helps somebody else down the road.