News for hackers. Stuff that matters.
Re:Ask HN: Has anyone else seen TCP connection issues in AWS... by toast0 on Friday August 14, 2020 @02:49PM (#24161747)
> Perhaps you could also explain why this change would get made?

I'm not related to Amazon/AWS (I'm not even a customer of AWS), but if it were my decision, I would want the mappings to be the same for everyone, because customer specific mappings makes it harder for customers to coordinate.

Ex: if I'm your customer and we're both on AWS and want to have the best experience between servers, I'd like to put my VMs that talk to yours in the availability zones you're in.

If I want to have the highest availability talking to your servers, again, I want to be in the same zones as you --- or at least if I'm in -1a and you're in -1b, I should expect to need to go to a different geo from time to time if only one AZ has an incident.

This is a lot harder if some of the identifiers mean different things.

Re: balancing. Thehre's usually ways to influence people. Default choices in the console, asking big customers to put new VMs in other zones or rebalance, spot prices, etc. I've been a big enough customer to see that at other hosting. If the top 10 customers control 50% of the VMs (made up statistic, but I was a #1 customer controlling 50% of a DCs traffic, so plausible), you only need to have a few conversations to get things moving.

There are no comments on this comment yet.