Bug Report: Elastic Beanstalk Creates Load Balancer for Single Instance

Hello,

I attempted to create a worker environment on Elastic Beanstalk. I wanted to set up a single instance with a private IP. Since it's a single instance, it doesn't offer load balancer options.

Private IP

Instance Options:

However, despite selecting a single instance, a load balancer is still being created. The load balancer visibility (private or public) is being chosen automatically.

After setting the environment type to Load Balanced and changing the Load Balancer network settings visibility to private, if we switch back to a single instance, the load balancer remains private.

After setting up the Load Balancer and making its visibility private, we then switch the instance type back to single instance.

Now it has private load balancer:

This is somewhat confusing from a usability perspective. I discovered this issue while trying to create a worker environment. I didn't need a load balancer and configured a single instance with a private IP. Later, I noticed a public IP on the EC2 instance and found that a load balancer had been created. Upon checking the configurations, I observed the behavior described above.