AWS Global Accelerator | Concept | Demo with AWS ALB

[@mogomotsiseiphemo1681]

At 16:00 you propose an architecture that includes Route53 for multi-region support. Is it not better to use the endpoint groups feature from AWS Global Accelerator? Can we even do that? When I configured it, it seemed like you could have an endpoint group per region, and multiple endpoints(instances, alb) per endpoint group.

[@lalitsehgal9929]

Very gd explanation

[@Cloud4DevOps]

Thanks for liking

[@suriya650]

What's the diff b/w the Global accelerator and Cloudfront for dynamic content(caching disabled) ? Let's say i have dynamic web application deployed in EC2 and it has global user. Which service should i use to reduce the network latency?

[@Cloud4DevOps]

CloudFront uses Edge Locations to cache content while Global Accelerator uses Edge Locations to find an optimal pathway to the nearest regional endpoint. CloudFront is designed to handle HTTP protocol meanwhile Global Accelerator is best used for both HTTP and non-HTTP protocols such as TCP and UDP. Cloudfront is CDN network just like Akamai which provides you the low latency response using edge location for static content.. For dynamic content check AWS doc :- aws.amazon.com/cloudfront/dynamic-content/

[@4abdoulaye]

GA optimize network trafic and routing via tcp or udp. Meant for TCP or UDP traffic! Major difference from CloudFront (meant for content caching).

[@MrDoublethumb]

Nice session!

[@Cloud4DevOps]

Glad you enjoyed it

[@nilaymohit]

Hi, On what basis we choose Endpoint Group Region? Suppose My ALB is in ap-south-1 region.

[@Cloud4DevOps]

So as you might know endpoint group routes requests to one or more registered endpoints. When you add a listener, you specify the endpoint groups for Global Accelerator to direct traffic to, endpoint group, and all the endpoints in it, must be in one AWS Region. Hope this clear your doubts.

[@ravindraravi7435]

Thank you ^^

[@traveldiary4558]

can map these ips to my godaddy domain a record? if yes then should i use one of the two IPs or should i use both IPs in two a record?

[@Cloud4DevOps]

To be honest i have never tried for that particular use case. Yes you can try it out..

[@traveldiary4558]

@@Cloud4DevOps thanks for your reply, lets try

[@scetamit2555]

How is this different from Geolocation Routing Policy in Route53?

[@Cloud4DevOps]

Sorry for the late reply...In generic way Geolocation Routing Policy is basically use to route the traffic based on the geographic location from where the DNS query is originated. This policy allows to send the traffic to resources in the same region from where the request was originated i.e. it allows to have site affinity based on the location of the users .. Whereas with AWS Global Accelerator, you don’t have to rely on the IP address caching settings of client devices. Change propagation takes a matter of seconds, which reduces your application downtime. Secondly, with Global Accelerator, you get static IP addresses that provide a fixed entry point to your applications. This lets you easily move your endpoints between Availability Zones or between AWS Regions, without having to update the DNS configuration or client-facing applications.

[@AnemUday]

Hi, Thanks for this video. I am curious to know, can't we assign elastic IP address to a ELB cascade to Route 53? If Global accelerator do reduce latency, then how it is different from CloudFront? CloudFront also do the samething, right?

[@Cloud4DevOps]

Thanks for placing the query !!! So you cannot assign static IP to AWS ALB [application load balancer] although you can use AWS NLB for static IP to route your request to EC2 instances to get the content. In terms of AWS Global Accelerator and Amazon CloudFront.. CloudFront improves performance for both cacheable content (such as images and videos) and dynamic content (such as API acceleration and dynamic site delivery). Global Accelerator improves performance for a wide range of applications over TCP or UDP by proxying packets at the edge to applications running in one or more AWS Regions. Global Accelerator is a good fit for non-HTTP use cases, such as gaming (UDP), IoT (MQTT), or Voice over IP, as well as for HTTP use cases that specifically require static IP addresses or deterministic, fast regional failover. if you are bind to you use public AWS ALB for better Layer 7 functionality and you want static IP then best fit is Global Accelerator with multi region support [ Best for DR].. I hope that clarifies your query.

[@veronicaluceriano2101]

Does aws global accelerator can be connect to api gateway?

[@Cloud4DevOps]

As far as i remember answer is no..

[@veronicaluceriano2101]

Thank you. I did some research and the answer is no. :)

[@swaroopkishan5031]

what do mean by whitelisting the ip address??

[@Cloud4DevOps]

So whenever you work with client environment , most of customers ask us to provide the Load Balancer IP address so that they can whitelist the IP address on their firewall to allow traffic and perform certain number of operation between client and hosted environment. So AWS ALB by default doesn't support static public IP address as ALB IP address is dynamic in nature which change as per load increase in background. If you want to have static IP address then one of getting this is Global Accelerator. I hope that suffice your query.

[@FidoTheGoldenRetriever]

Let’s say my server is in Mumbai, India and my target audience are Indians. Should I use this Accelerator and will I get any performance benefits?

[@Cloud4DevOps]

It will benefit you , i would suggest you go for cloudfront as CDN which will cost you less .. Until unless you dont find better use case of accelerator like getting static IP and multi region support dont use it as it will cost you more as compared to other services..