When creating a new EBS environment and selecting Load Balancer, the "Classic" option is disabled, not possible to select (which is fine as that old load balancer is a sin to exist nowadays). However when you create an EBS as Single Instance, and then later you turn on load balancing, it results in an environment with a Classic Load Balancer, and this cannot be changed. Even if you revert back to Single Instance, and then try to re-enable load balancing, the "type" is still stuck on Classic and the whole type selection is disabled.
There are two bugs in here to begin with:
-
- that the deafult is the classic type if you take the path of first being single instance and then load balanced order.
-
- not having the option to select the load balancer type for an EBS single instance environment, when enabling load balancing later on (really, there is no logical reason to not have this disabled, since we are not talking about "changing" the type here, rather creating a new one (as the environment at this point is configured for single instance)
FYI the load balancer migration doesn't have to do anything with this, since the issue is not creating a new type of load balancer, but rather making the EBS environment understand that it now should have a new type of load balancer (stating this on purpose since the forum is full with questions about how to migrate from classic to new types, but my bug report is about the wrong behavior of the management console and the EBS product itself)
AWS OFFICIALUpdated a year ago
