Re:Ask HN: Has anyone else seen TCP connection issues in AWS...
by choxi on Friday August 14, 2020 @01:06PM
(#24160425)
From the comments:
> Isn’t us-east-1 exactly that?
We've come full circle
Re:Ask HN: Has anyone else seen TCP connection issues in AWS...
by BillinghamJ on Friday August 14, 2020 @01:18PM
(#24160564)
It always has been - us-east-1 is the biggest region by far, so scale problems tend to arise there first.
Re:Ask HN: Has anyone else seen TCP connection issues in AWS...
by kjaftaedi on Friday August 14, 2020 @01:34PM
(#24160762)
All updates and patching start with us-east-1.
The main reason it has the most issues is because it's the guinea pig for production update deployments.
Re:Ask HN: Has anyone else seen TCP connection issues in AWS...
by whoevercares on Friday August 14, 2020 @01:39PM
(#24160841)
Hmm that’s not true, nowadays most new things will start with small regions, typically us-east-2
Re:Ask HN: Has anyone else seen TCP connection issues in AWS...
by arsh on Friday August 14, 2020 @04:02PM
(#24162572)
+1
Re:Ask HN: Has anyone else seen TCP connection issues in AWS...
by Matthias247 on Saturday August 15, 2020 @12:34AM
(#24165968)
That's a repeated wrong assumption. In general there is no unified rollout plan within AWS. Each service can use a different method.
Re:Ask HN: Has anyone else seen TCP connection issues in AWS...
by drpebcak on Saturday August 15, 2020 @01:46AM
(#24166298)
I think it has more to do with the fact that it’s the oldest region, and they support some odd things there that do not exist in other regions.
"I want to have an AWS region where everything breaks with high frequency" https://news.ycombinator.com/item?id=24103746