> I have deployed five AWS m8g.12xlarge instances. Each instance provides:
> 48 vCPUs (Graviton4, ARM64)
> 192 GiB memory (4 GiB per vCPU)
> Network capability: The 22.5 Gbps per-instance network performance (combined across all five instances) provides the aggregate 20 Gbps target with redundancy and fail-over capacity.
Oh wow. Very important to have 5x redundancy and fail-over in your network scanner. Especially before the code has landed. Did it implement A/B upgrades and canarying too to avoid downtime?
Sounds like the default k8s setup every startup deploys to not fail it single digit number of users. It learned from the best
All on the same zone, of course, to avoid high-latency links.
At least it was considerate enough to cap traffic to any single IP at 5000 Mbps :).
Typical DN42 interconnects are 1Gbps with unspecified bandwidth caps. It's not made to carry serious traffic at all. For a real ISP, 5000 Mbps these days is nothing unless it's all concentrated on the same last mile - the smallest links they use are usually now 10Gbps. But DN42 isn't the real internet.
When I read the AWS infrastructure the agent setup I about fell out of my chair laughing.
I think the owner wanted 100 Gbps of scan traffic or had set a specific scan-rate target, which determined that bit rate, so the LLM (correctly) predicted it needed all of those to hit the target.
I mean you can get that for like 300 p/m at hetzner
100Gbps? I don't think so? I'd expect a thousand a month for the adapter and connection, and then around $1.50/TB as per their standard price (including currency conversion and VAT), which is to say, $1.00 per minute of saturated usage.