News for hackers. Stuff that matters.
Re:AWS data center latencies, visualized by dopp0 on Thursday October 24, 2024 @06:53PM (#41940647)
why 443? are you assuming ssl here? serious question, I'm not sure. But if it is, wouldn't it be hard to disregard the weight of SSL in the metric?
Re:AWS data center latencies, visualized by semiquaver on Thursday October 24, 2024 @11:47PM (#41942050)
The code closes the connection immediately after opening a plain TCP socket, so no SSL work is done. Presumably 443 is just a convenient port to use.
Re:AWS data center latencies, visualized by nullindividual on Friday October 25, 2024 @12:15PM (#41946692)
tcp/443 is likely an open port on the target service (Dynamodb based on the domain name). TLS is not involved.

ICMP ECHO would be a bad choice as it is deprioritized by routers[0].

While usage of tcp itself might add some amount of overhead to the connection time, it is also a more realistic measure as most of the services we use leverage tcp.

[0] https://archive.nanog.org/sites/default/files/traceroute-201...

Re:AWS data center latencies, visualized by quie on Friday October 25, 2024 @07:30PM (#41951013)
The script connects to well known 'dynamodb.' + region_name + '.amazonaws.com' server that expects HTTPS