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?
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...
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.
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.
@@taiwobabalola4755 1.I assume we can make it work without NAT GW as well right? 2.And AWS does not offer SNAT concept like Azure where LB Public IP can be used for private instances to access internet?
@@aditya-garg it shouldn't work without a NAT Gateway, no. Your private instances have no direct route to the internet (i.e your load balancer). The route table they use specifices that 0.0.0.0 (internet traffic) goes to the NAT gateway, and the ELB (behind the scene) knows that to route traffic to those instances, it has to be sent to the address of the NAT gateway. IMO this video should at least mention this concept, because this step IS happening, but you don't get to see it
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?
I do not think NAT GW is required here, it was created because its a mandatory attribute to create the VPC thru Wizard. You can try deleting it and try reaching your servers via ELB DNS
First u need to understand what is ur requirment 1) you want ur servers to be private or public 2) do you want to load balance your traffic -> if u want ur servers to be public and you want a fix DNS use Elastic IP -> if u want Private servers and fix DNS and load balance -> use the Application Load balancer as ur using Elastic IP, i think ur scenario is that instance should be internet exposed
Once the health checks have passed for the target groups, you can use the Load balancer DNS as the ELB is hosted on a public subnet, it is always accessible. In case of 502 error, check back with the target groups again.
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.
You will need to add the 2 instances to the alb and make sure they both live in a new security group as they are in different regions, normally u add listeners for different rules.
First Thing in your scenario i can see -> that ur ec2 are in diff AZ's and u want to load balance so first thing u need to check is -> which az's ur Ec2 are if ur ec2 is in 2 az, like A and B zone u need to configure ur ELB where u also need to put ur load balancer on the Same AZ in which ur ec2 presents That would work
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
Apologies for any confusion caused! This re:Post article gives instructions on how to connect a public-facing load balancer to EC2 instances: go.aws/44KfIoP. Feel free to use these other resources if this wasn't quite it: go.aws/get-help. ^LG
