I have latency (ping) dependent application, so I moved from random hoster name to amazon, because it also hosts my "target" website. When I resolve "target" website name I'm getting
ec2-ip_address.ap-northeast-1.compute.amazonaws.com
So I chose ap-northeast-1 region, created a bunch of instances (m2.micro) with different subnets (ap-northeast-1a, 1c, 1d) to find greatest location.
Later on I also added two different subnets to VPC configuration (ap-northeast-1-wl1-kix-wlz-1, ap-northeast-1-wl1-nrt-wlz-1), retested everything and tried to use them also in EC2 instance but faced "Instance launch failed. The requested configuration is currently not supported. Please check the documentation for supported configurations." without specifying what exactly is wrong or unsupported.
Testing technique:
Plain python requests.get() with measuring request start and responce recieve time. Without any additional load on the system
Numbers:
Previous hosting, 2 core vps, ubuntu 22.04, no OS optimizations:
website1.com 0.04753
website2.com 0.14008
EC2 Instance m2.micro (any subnet), ubuntu 22.04, no OS optimizations:
website1.com 0.09059 - 2x slower than previous hosting
website2.com 0.13937 - same as previous hosting
Numbers were exactly the same between ap-northeast-1a, 1c, 1d
AWS CloudShell:
website1.com 0.01976 - 4-5 times lower latency than any of EC2 instances while also 2-3x faster than previous hosting!
website2.com 0.06534 - 2-3 times lower latency than any of EC2 instances while aslo 2-3x faster than previuos hosting!
So the question is how do I get AWS CloudShell latencies on my EC2 instance?
Thank you! Will try to setup these again!
With your answer I managed to connect to the wavelength zones, but in there, numbers were even worse: wavelength zones: website1.com 0.112351 website2.com 0.257855 aws cloudshell: website1.com 0.027503 website2.com 0.105059