At 2020-03-17 12:52:40 UTC-0700, a warning occurred:
Environment health has transitioned from Ok to Degraded. 1 instance online is below Auto Scaling group desired capacity 2. Auto Scaling activity failed 42 seconds ago with error: There is no ACTIVE Load Balancer named 'awseb-e-2-AWSEBLoa-Q8OUAZWKIJD8'. Validating load balancer configuration failed. At 2020-03-17T19:51:23Z a monitor alarm awseb-e-2hskntpzpt-stack-AWSEBCloudwatchAlarmHigh-9D8FOVHO5L31 in state ALARM triggered policy awseb-e-2hskntpzpt-stack-AWSEBAutoScalingScaleUpPolicy-9SAFEXSFPA9C changing the desired capacity from 1 to 2. At 2020-03-17T19:51:48Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 1 to 2.
Since then it has been trying to do environment updates, with the warning, e.g.:
2020-03-17 17:28:36 UTC-0700
LoadBalancer awseb-e-2-AWSEBLoa-Q8OUAZWKIJD8 could not be found.
As far as I'm aware, nothing has been touched with the setup for this website in Elastic Beanstalk, but all of a sudden there's a missing loadbalancer.
Any tips on how I can investigate and rectify this?
AWS OFFICIALAktualisiert vor 2 Jahren