HackerNews中文版

今天，AWS 似乎在 eu-west-2（伦敦）地区上线了一个新的可用区（AZ），但没有大张旗鼓，甚至没有告知其支持人员。这个新可用区似乎是 eu-west-2d。目前还没有 AWS 文档反映这一变化。想在此提醒使用该区域的各位，以防万一——在一个客户现场，这导致了 Terraform 失败等一系列广泛的问题。根据您的代码库，资源可能会被意外地销毁和重新创建。您可能会争论这是否应该引起问题，因为这是云环境等等，但我只是想尝试为其他人节省几个小时的困惑。 aws ec2 describe-availability-zones --region eu-west-2 --all-availability-zones --query 'AvailabilityZones[].[ZoneName,ZoneID,ZoneTYpe,State,OptInStatus,Messages]' [ [ "eu-west-2a", null, null, "available", "opt-in-not-required", [] ], [ "eu-west-2b", null, null, "available", "opt-in-not-required", [] ], [ "eu-west-2c", null, null, "available", "opt-in-not-required", [] ], [ "eu-west-2d", null, null, "available", "opt-in-not-required", [] ],

查看原文

It seems as though AWS have brought a new AZ online in eu-west-2 (London) today with very little fanfare or indeed without telling their support staff. It appears as eu-west-2d. No AWS docs yet reflect this change.<p>Wanted to give anyone who uses this region a heads up just in case - at a client site it has caused a widespread bunch of issues as a result of Terraform failures etc. Depending on your codebase resources might be torn down and recreated unexpectedly. You can argue the case for whether this should cause you issues or not given this is the cloud etc but I just wanted to try and save someone else some hours of head scratching.<p>aws ec2 describe-availability-zones --region eu-west-2 --all-availability-zones --query 'AvailabilityZones[].[ZoneName,ZoneID,ZoneTYpe,State,OptInStatus,Messages]' [ [ "eu-west-2a", null, null, "available", "opt-in-not-required", [] ], [ "eu-west-2b", null, null, "available", "opt-in-not-required", [] ], [ "eu-west-2c", null, null, "available", "opt-in-not-required", [] ], [ "eu-west-2d", null, null, "available", "opt-in-not-required", [] ],

AWS 在 eu-west-2 新增可用区 - 注意意外结果