Here's a count of AZs based on the AZ IDs: Format: `region (launch year): count` us-east-1 (2006): 6 ap-northeast-1 (2011): 4 ap-northeast-2 (2016

Here's a count of AZs based on the AZ IDs: Format: `region (launch year): count` us-east-1 (2006): 6 ap-northeast-1 (2011): 4 ap-northeast-2 (2016): 4 us-west-2 (2009): 4 af-south-1 (2020): 3 ap-east-1 (2019): 3 ap-northeast-3 (2018): 3 ap-south-1 (2016): 3 ap-southeast-1 (2010): 3 ap-southeast-2 (2012): 3 ap-southeast-3 (2021): 3 ca-central-1 (2016): 3 cn-north-1 (2013): 3 cn-northwest-1 (2017): 3 eu-central-1 (2014): 3 eu-north-1 (2018): 3 eu-south-1 (2020): 3 eu-west-1 (2007): 3 eu-west-2 (2016): 3 eu-west-3 (2014): 3 me-south-1 (2019): 3 sa-east-1 (2011): 3 us-east-2 (2016): 3 us-gov-east-1 (2019): 3 us-gov-west-1 (2011): 3 us-west-1 (2011): 3 (As reported by SSM's `/aws/service/global-infrastructure/availability-zones/` endpoint) EDIT: Some curiosities of note: - apne1-az3: In the list, but some things, like NAT Gateway, aren't available; seems like most (all?) people can't provision new instances there. - cac1-az3: Not in list; jumps from az2 to az4. Supposedly launched for internal use back when cac1 only had 2 public AZs because S3 and some other services require 3 AZs for redundancy. - cnn1-az3: Not in list; jumps from az2 to az4. Same reason as cac1-az3?