News for hackers. Stuff that matters.
Re:Slack Incident Resolved – Degraded service affecting mult... by arpinum on Tuesday August 25, 2020 @07:33AM (#24270244)
The letters are different per-account.
Re:Slack Incident Resolved – Degraded service affecting mult... by dkarp on Tuesday August 25, 2020 @07:41AM (#24270319)
thanks, first time seeing that
Re:Slack Incident Resolved – Degraded service affecting mult... by surfer7837 on Tuesday August 25, 2020 @08:08AM (#24270498)
It's so the load is evenly distributed across AZs because I bet most people just select -az-1.
Re:Slack Incident Resolved – Degraded service affecting mult... by tedk-42 on Tuesday August 25, 2020 @08:52AM (#24270786)
As another commenters mentioned, the AZ letter different per account.
Re:Slack Incident Resolved – Degraded service affecting mult... by asymptotic on Tuesday August 25, 2020 @10:42AM (#24271817)
https://docs.aws.amazon.com/ram/latest/userguide/working-wit...

“To identify the location of your resources relative to your accounts, you must use the AZ ID, which is a unique and consistent identifier for an Availability Zone. For example, use1-az1 is an AZ ID for the us-east-1 Region and it is the same location in every AWS account”

So each separate AWS account will have a different AZ name that maps to use1-az1, but use1-az1 is a region-wide constant.