EC2 Instance has 5 times more latency than AWS console

0

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?

1 Answer
1

created a bunch of instances (m2.micro) .... I also added two different subnets to VPC configuration (ap-northeast-1-wl1-kix-wlz-1, ap-northeast-1-wl1-nrt-wlz-1) .... "Instance launch failed. The requested configuration is currently not supported.

Those are Wavelength Zones, which are optimised for 5G and reside with the telco's infrastructure (in the case of the Tokyo region this is KDDI) https://aws.amazon.com/wavelength/

There is a limited availability of compute instances available, so if you are trying to stand up an m2.micro EC2 instance using a CloudFormation template (that works fine in other zones) then you will get that error https://aws.amazon.com/wavelength/features/#Choice_of_compute_instances

profile picture
EXPERT
Steve_M
answered 7 months ago
profile pictureAWS
EXPERT
reviewed 7 months ago
profile picture
EXPERT
reviewed 7 months ago
  • 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

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions