the best tutorial for Global accelerator I have found so far . just wondering, won't I be achieving the same functionality using the Geolocation routing policy offered under R53?
the thing that we need to understand is that, with global accelerators u dont need to cache the request ip. cause u will be using the end point that is static. the rest is route 53 where if in case there is a update then the propagation will take more time.
Hi , If I create only one EC2 instance in N.Virginia and access it from Mumbai Region.How the global accelerator would give benefit.Also could u pls explain what is the Amazon global network? Thanks for the nice explanation in vedios.
hey thanks for the content, I have great question. Im running a VPN on my ec2 and created a global accelerator. But my ec2 still using default IP how I can chance global accelretaor IP ?
what if I delete the global accelerator directly without removing endpoints and all? by the way, I really appreciate your work. the visual explanation makes it easy to understand.
If you created an accelerator as a test or if you're no longer using an accelerator, you can delete it. On the console, disable the accelerator, and then you can delete it. You don't have to remove listeners and endpoint groups from the accelerator. When you delete an accelerator, you lose the static IP addresses that are assigned to the accelerator, so you can no longer route traffic by using them
I think that would depend on ur requirement. Route 53 does way more tasks related to dns based routing. But global accelerator can come in handy when there is a specific use case
A small question. We have Latency based routing policy in Route53. So if we have that policy enabled, do we still need to have Global Accelerator to increasing performance?
the thing that we need to understand is that, with global accelerators u dont need to cache the request ip. cause u will be using the end point that is static. the rest is route 53 where if in case there is a update then the propagation will take more time.
![[#2024MAMA] ROSÉ (로제), Bruno Mars - APT. | Mnet 241122 방송](http://i.ytimg.com/vi/dgGqD28J6aQ/mqdefault.jpg)
Love the background music. activates the brain :)
the best tutorial for Global accelerator I have found so far . just wondering, won't I be achieving the same functionality using the Geolocation routing policy offered under R53?
the thing that we need to understand is that, with global accelerators u dont need to cache the request ip. cause u will be using the end point that is static.
the rest is route 53 where if in case there is a update then the propagation will take more time.
Perfect Demo!!
Always wait for the next tutorial
Thank You soooooo muchhhhhh!
I needed these
What IP you will whitelist in target ec2 instance..... Global IP or user public IP?????
Hi ,
If I create only one EC2 instance in N.Virginia and access it from Mumbai Region.How the global accelerator would give benefit.Also could u pls explain what is the Amazon global network?
Thanks for the nice explanation in vedios.
Please watch the global accelerator video explaining about that. It's on the channel
hey thanks for the content, I have great question. Im running a VPN on my ec2 and created a global accelerator. But my ec2 still using default IP how I can chance global accelretaor IP ?
what if I delete the global accelerator directly without removing endpoints and all?
by the way, I really appreciate your work. the visual explanation makes it easy to understand.
If you created an accelerator as a test or if you're no longer using an accelerator, you can delete it. On the console, disable the accelerator, and then you can delete it. You don't have to remove listeners and endpoint groups from the accelerator.
When you delete an accelerator, you lose the static IP addresses that are assigned to the accelerator, so you can no longer route traffic by using them
@@Pythoholic Thank you 😊👍
Thanks for the video. Nice demos. when we use global accelerator then there is no need to use the route 53?
I think that would depend on ur requirement. Route 53 does way more tasks related to dns based routing.
But global accelerator can come in handy when there is a specific use case
A small question. We have Latency based routing policy in Route53. So if we have that policy enabled, do we still need to have Global Accelerator to increasing performance?
the thing that we need to understand is that, with global accelerators u dont need to cache the request ip. cause u will be using the end point that is static.
the rest is route 53 where if in case there is a update then the propagation will take more time.
Thanks
Fantastic !!.
Great demo 😊
@pytholic Where can I find the script, and link to download the files?
User data
Please visit pythoholic github it’s available there
@@Pythoholic where can I find the link please
github.com/Pythoholic/pythoholic_demo_aws