|
|
|
|
|
by alblue
1657 days ago
|
|
The most annoying aspect of this for us was that the AWS Organizations API only has a single endpoint, in us-east-1. https://docs.aws.amazon.com/general/latest/gr/ao.html As a result, even if you weren’t using that region but you were using the API you were hosed for 6+ hours, And the status page never acknowledged that it was out of action. We had the following Terraform in our production pipeline: data “aws_organizations_organization” “current” {} As a result, all of our deployments to our EU regions were borked. Of course, we couldn’t raise a support case because the support system was also down, and despite escalating to our TAM weren’t able to get the status page to reflect reality. My concern is that the Organizations API specifically will be brushed under the carpet and we will still have a single point of failure in a region which we never intend to use. |
|