Sadly there is no multi-region Cognito. Would love to hear if anyone has a strategy for that.
Architectures for Mitigating AWS Outages
11–17 of 17 posts
Re: Architectures for Mitigating AWS Outages
#12Poor man's architecture for mitigating outages: Avoid us-east-1 (N Virginia). It unequivocally is the fail-whale of AWS regions. Every service there seems to have abnormally high usage numbers and absurd amount of scale to deal with. As James Hamilton would like to remind us, at such scale, even rare events are frequent [0]. The curse of being the default region, I suppose? us-east-2 (Ohio) and eu-west-1 (Dublin) are…
It's my understanding that they roll out changes there first, historically. New features land there first. Etc. US-EAST-1 IS the canary.
This is a repeated wrong statement.
Every AWS service can decide their deployment strategy on their own - there is no mandate on which region gets updates first. And starting in smaller regions is recommended.
Re: Architectures for Mitigating AWS Outages
#13Poor man's architecture for mitigating outages: Avoid us-east-1 (N Virginia). It unequivocally is the fail-whale of AWS regions. Every service there seems to have abnormally high usage numbers and absurd amount of scale to deal with. As James Hamilton would like to remind us, at such scale, even rare events are frequent [0]. The curse of being the default region, I suppose? us-east-2 (Ohio) and eu-west-1 (Dublin) are…
I can recall a number of outages on us west 1/2 so not sure the argument applies maybe us east 1 failure is just more visible when it happens... the latest incident didn’t impact all of us east 1 - really just people using kensis right?
Re: Architectures for Mitigating AWS Outages
#14Poor man's architecture for mitigating outages: Avoid us-east-1 (N Virginia). It unequivocally is the fail-whale of AWS regions. Every service there seems to have abnormally high usage numbers and absurd amount of scale to deal with. As James Hamilton would like to remind us, at such scale, even rare events are frequent [0]. The curse of being the default region, I suppose? us-east-2 (Ohio) and eu-west-1 (Dublin) are…
I can recall a number of outages on us west 1/2 so not sure the argument applies maybe us east 1 failure is just more visible when it happens... the latest incident didn’t impact all of us east 1 - really just people using kensis right?
Well, yes, but services like SNS and S3 use kinesis, so if you used either of those...
Re: Architectures for Mitigating AWS Outages
#15Sadly there is no multi-region Cognito. Would love to hear if anyone has a strategy for that.
Unfortunately if you use Cognito for authentication you're currently SoL, as many of us learned the hard way last week.
Region rollover is not possible with Cognito. I believe you could backup the user pool to a different region, but users would still need to reset their passwords which would open another can of worms when you switch back to the original pool.
Re: Architectures for Mitigating AWS Outages
#16As an SRE, we accept that different regions will fail every now and then. So how to mitigate them is the big question.
I think having a database replicated to 2 regions and load balance all traffic to both region has a big impact on performance and read after write consistency The solution is what the last option suggests; the second region is prepared as a fallback solution only and not as a live solution. This way, you accept that you will still have some downtime and maybe some data loss too whenever a failover takes places. But this is much better than going down for hours, and is much better than having 2 regions in Active-Active mode where your system will suffer from performance and data consistency So accept you will have failures, work on the better solution. The perfect solution does not exist. There is no 100%
Re: Architectures for Mitigating AWS Outages
#17Poor man's architecture for mitigating outages: Avoid us-east-1 (N Virginia). It unequivocally is the fail-whale of AWS regions. Every service there seems to have abnormally high usage numbers and absurd amount of scale to deal with. As James Hamilton would like to remind us, at such scale, even rare events are frequent [0]. The curse of being the default region, I suppose? us-east-2 (Ohio) and eu-west-1 (Dublin) are…
I can recall a number of outages on us west 1/2 so not sure the argument applies maybe us east 1 failure is just more visible when it happens... the latest incident didn’t impact all of us east 1 - really just people using kensis right?
No one should use us-west-1 unless they have a good reason to: It's more expensive, only two AZs for new customers, frequent capacity issues, and slow to get new services. us-west-2 should almost always be preferred, as it's a flagship region and only a couple light-milliseconds away.
As a user of us-west-2, I've found it to be very reliable. I can only remember a couple minor issues off the top of my head. The region hasn't even made the leaderboard. [1] ;)
Every time us-east-1 goes haywire, I can kick my feet up and relax as the world burns.