[ AWS 8 ] Configuring Elastic Load Balancer ELB



In this video, I will show you how to configure an Elastic Load Balancer in AWS to share the load between multiple AWS EC2 instances.

Elastic Load Balancing
https://aws.amazon.com/elasticloadbalancing/

Hope you enjoyed this video. Please share it with your friends and make sure to subscribe to this channel. For any questions/issues/feedback, please leave me a comment and I will get back to you at the earliest I can.

Thanks for watching this video.

If you wish to support me:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=F8FN37PAD629Y&source=url

source

8 thoughts on “[ AWS 8 ] Configuring Elastic Load Balancer ELB”
  1. Hello, Can you give me the way to use Path in Listener ALB ? Because I want to attach some AutoScalling with Target Group behind the ALB with Path, but it still fail. Thanks before….

  2. @Just me & open source: can we create load balancer using cli, perform route 53 using cli mode.
    What task in aws we can perform using CLI or what we can do only using aws portal

  3. Hello Venkat. Once again, thanks for all the work you've been doing by sharing everything you've been learning. I'm specially fond of the Learn Kubernetes playlist.
    I'm not sure if you figured this by now since this video is a few months old, but you don't need a public IP on your backend servers, even with internet-facing load balancers.
    When you deploy a LBaaS, it automatically deploys an instance in each availability zone you choose to provide connectivity between the load balancers and the backend servers.
    Of course that if you deploy a instance without a public IP, you need other means to access it in order to manage it, which usually includes a VPN.

  4. Hi venkat can you make the videos on route 53 that will be very helpful for the users

  5. Hi, why are the other videos from the playlist private? Are you going to release them to a future date? Thanks for the videos.

  6. Hi Venkat,
    thanks for video. i tried below scenario….
    I havecreated two ec2 machines. added 2 machines to target group. i am able to access app in two different machines using curl with DNS name.

  7. It's was good one. But I need to ask you one question.
    In our organisation they are using EIPs for each and every instance, is that good practice?
    And my idea is having a load balancer and navigating the traffic using a DNS name will be useful thing like what we did in k8s ingress?

Leave a Reply

Your email address will not be published.

Captcha loading...