How do I connect a public-facing load balancer to EC2 instances that have private IP addresses?

preview_player
Показать описание
Hannah, shows you how to connect a public-facing load balancer to EC2 instances that have private IP addresses.
Рекомендации по теме
Комментарии
Автор

It would have helped if there was a visual that shows the architecture diagram at the end.

avadhanam
Автор

Why was a Classic LB used? Can this be done with an Application or Network LB? I understand that the steps may be different, but is the end result possible with the other two ELB types?

sysadmin-e
Автор

I have followed the exact same process, however, the status of the instance is showing out-of-service on Loadbalancer
waited for 10 min still the same.

rakeshpandey
Автор

How do we connect to the EC2 server now since we do not have an public DNS, is it through ELB DNS ?? Can you please tell ?

deepakpaliwal
Автор

Suppose in a given scenario an EC2 instance is linked with an Elastic IP address and is obviously exposed to the internet. If i create an ELB, do I need to get rid of the Elastic IP and link that EC2 instance with the ELB? Can ELB be employed in this scenario without removing the Elastic IP address?

liausdhfsdgfgf
Автор

Thank you so much.. It helped a lot for me.

bezawadaashok
Автор

If you want to see architectural diagram pause the video at 0:59 and if wondering why NAT "NAT Gateway enables internet connection to your private subnet", try this without the wizard.. that's where learning starts, still is there is a architectural diagram from the begining and step by step establishment tracking would be more helpfull. thank you i still cant understand why we choose default SG for EC2 instance and later why we are connecting it to ALB why dont we choose ALB connected SG from the first it self .. any one please help...

rishiyyogi
Автор

Why was the NAT Gateway need for this example? Was it only for patching and updating the EC2s? Thanks for the help in Advance!

uDubRiceBoy
Автор

Not directly related to this video, but if an (external) App or Network LB is created, is there an internal IP address or FQDN we can reference? The goal is to be able to use the same ELB for both external and internal users without the internal users having to go out to the external interface of the ELB.

sysadmin-e
Автор

What's happen when we use two EC2 instances each one in different AZ. Does the ELB works in this setup?

gustavoalvarezgomez
Автор

It's sad that best practices on AWS are so damn expensive.

SteepVisions
Автор

I was able to follow your instructions

BengaliStrings
Автор

Excellent. Really It helped me.
Can I create two more subnets in another zone? For pubic-subnet 10.0.2.0/24 and for the private 10.0.3.0/24 and launch the instances in the private subnet? will that work? I tried. But didn't.

damodaragottipalli
Автор

Disappointed to see the wizard being used. We fail to learn many important concepts.

regulardev
Автор

Your voice is like sadie adler from rdr2😅

johnsamuels
Автор

Worst presentation ever! things confused: 1) what is the role of NAT for this task 2) how the security group is described in rules 3) Route Table is not mentioned

haipingwang