That's strange because all AWS servers have an SSD configured as the boot disk.
I guess it wasn't clear that
alladdresses.loyce.club:20319 doesn't run at AWS. It uses HDD.
And it's doing that for the entire 31GB of addresses, and the algorithm sort uses needs an O(n log(n)) space, which I calculate to be 310GB for your data.
It takes many hours while keeping server load low, but it really isn't a problem.
If someone has enough RAM to experiment, I'd love to see the result of this (on the 31 GB file):