可用区与区域的 Amazon S3 冗余

Amazon S3 redundancy over Availability Zones vs. over Regions

https://aws.amazon.com/blogs/storage/architecting-for-high-availability-on-amazon-s3/#:~:text=Amazon%20S3%20maintains%20redundancy%20even%20within%20one%20of,can%20still%20access%20their%20data%20with%20no%20downtime 声明如下:

Amazon S3 storage classes replicate their data on more than three Availability Zone (except for S3 One Zone-Infrequent Access).

这篇文章有什么意义 https://aws.amazon.com/blogs/startups/large-scale-disaster-recovery-using-aws-regions/ 陈述:

S3 snapshots: We rely on the cross s3 sync and this works like a charm. We are able to copy the data from our primary to the DR region within a matter of few minutes.

后者现在看来是多余的,而且是 2017 年的,所以它可能已经过时了?还是我们也应该将 Amazon S3 副本放置在多个区域上?我认为没有必要,因为一个区域内的可用区在物理上彼此分离。我错过了什么?

S3 存储桶是区域特定的。创建新存储桶时,您需要 select 该存储桶的目标区域。

出于 DR 原因,您可以在另一个区域保留备份。如果主要区域以影响整个区域的方式出现故障,那么您可以在备份区域中进行恢复。

您的 DR 策略将取决于您的用例,以及您在区域范围内发生故障时将服务恢复正常的需求。

例如,假设您依靠 ec2/ebs 来运营您的服务,而这些服务在整个区域范围内中断了 5 个小时。为了恢复您的服务,您需要移动到资源可用的区域。假设您需要 S3 数据进行操作处理,您会希望在目标恢复区域中准备好该数据。

存储在一个区域的多个AZ中并不能保证整个区域的安全failure.This适用于所有区域服务。您分享的文章确实提到了这一点,所以它不是无关紧要的。

The service that runs in HA is handled by hosts running in different availability zones but in the same geographical region. This approach, however, does not guarantee that our business will be up and running in case the entire region goes down