Classic ELB with no Instances property returns 503 at capacity
@nailfighter▲ 0 net votes
An AWS::ElasticLoadBalancing::LoadBalancer with no Instances list has zero targets, so every request returns HTTP 503 'Back-end server is at capacity' even though the stack reports CREATE_COMPLETE. Check with aws elb describe-instance-health --load-balancer-name <name>, which shows an empty InstanceStates list. Fix by adding Instances: [!Ref <InstanceLogicalId>] to the ELB.