Sorry for asking too many questions, If load balancer is a regional service.. how does it work if i want to launch global business with load balancer ?
00:10:00 When you say long-lived connection as No for Application Load Balancer.. is it HTTP Keep-alive header ? If so, Most of the web applications are hosted via Application Load Balancer.. Then how do they achieve keep-alive thing ?
http ( ref. keep-alive-header) is a Application layer OSI Layer 7 protocol. ALBs/Web-Servers deal with it. tcp ( ref. long lived tcp connection) is a transport layer OSI layer 4 protocol. NLBs handle this.
00:07:34 Thank You, If Application Load Balancer doesn’t provide static IP address, There is always need a to use Network Load Balancer along with Application Load Balancer for most web services to have that static IP Address assign to DNS, right ?
Static IP/Network Load Balancer not needed for that. Note that ALBs come with a dns name of the form: [..elb.amazonaws.com]. In your DNS service you can create a CNAME record to route queries to your load balancer. If you are using Route 53, then you can create a hosted zone and an alias resource record set pointing to your ALB.
But some organizations like to explicitly put ip addresses in allow list of their firewall. In such cases NLB --> ALB or Global accelerator will be needed to provide the static ip. Is it the correct statement?
Please share your feedback, and questions if any below.
Sorry for asking too many questions, If load balancer is a regional service.. how does it work if i want to launch global business with load balancer ?
Global Accelerator, Route 53, CloudFront - are global services and can help you manage traffic flow across regions.
Can we use route 53 with global accelerator?
Sure. Create an A or CNAME record in Route 53 that points to the Global Accelerator’s DNS name or IP addresses.
00:10:00 When you say long-lived connection as No for Application Load Balancer.. is it HTTP Keep-alive header ? If so, Most of the web applications are hosted via Application Load Balancer.. Then how do they achieve keep-alive thing ?
http ( ref. keep-alive-header) is a Application layer OSI Layer 7 protocol. ALBs/Web-Servers deal with it.
tcp ( ref. long lived tcp connection) is a transport layer OSI layer 4 protocol. NLBs handle this.
00:07:34 Thank You, If Application Load Balancer doesn’t provide static IP address, There is always need a to use Network Load Balancer along with Application Load Balancer for most web services to have that static IP Address assign to DNS, right ?
Static IP/Network Load Balancer not needed for that.
Note that ALBs come with a dns name of the form: [..elb.amazonaws.com].
In your DNS service you can create a CNAME record to route queries to your load balancer.
If you are using Route 53, then you can create a hosted zone and an alias resource record set pointing to your ALB.
@@ArchitectureBytes Thank You !!
But some organizations like to explicitly put ip addresses in allow list of their firewall. In such cases NLB --> ALB or Global accelerator will be needed to provide the static ip. Is it the correct statement?