This is the first load balancer that AWS introduced which has it is missing some features like the latest load balancers provide. A Classic Load Balancer still has a purpose for EC2 Classic instances.
Per AWS, “Elastic Load Balancing automatically distributes your incoming traffic across multiple targets, such as EC2 instances, containers, and IP addresses, in one or more Availability Zones. It monitors the health of its registered targets, and routes traffic only to the healthy targets. Elastic Load Balancing scales your load balancer as your incoming traffic changes over time. It can automatically scale to the vast majority of workloads.”
**As easy as this may look, it is only as easy as how much time you put into designing the requirements and layout
How to deploy classic load balancer:
Create load balancers
What port will our CLB listen onto
Here is where you will provide a LB name, the VPC It will be created in and the protocols used.
Unless you have an existing SG for your load balancers you will need to create a new one
The example above will allow anyone from anywhere to access the LB from the outside
Use http protocol on port 80 on this path
Can remove the ping path of /index.html and it would still work
Now you have the ability to add your EC2 instances or they can be added later
Review and create
Confirm the creation of the LB
Wait for it to become in service
You can take the DNS name of the LB and put it into a web browser and you should get the expected output from your web servers behind the classic LB
Proof that the instance is responding through the LB
Setting up a classic load balancer manually in AWS has a lot of steps but is easy once you have done it a couple of times. Once again, if you design everything up front and know all the requirements then this will move along easily. Once again, I hope y’all found this helpful.