AWS Organizations API - us-east-1 for all API and CLI calls

Question

From https://docs.aws.amazon.com/organizations/latest/APIReference/Welcome.html (and related docs, such as https://awscli.amazonaws.com/v2/documentation/api/latest/reference/organizations/index.html#cli-aws-organizations)
> For the current release of Organizations, specify the us-east-1 region for all Amazon Web Services API and CLI calls made from the commercial Amazon Web Services Regions outside of China.

While https://docs.aws.amazon.com/general/latest/gr/ao.html lists various endpoints.

Is the us-east-1 region still required for api access, as the documentation states?

Answer

Has there been any thought to allowing the AmazonOrganizationsClient object in the AWS SDK for .NET (or maybe any SDK) to allow for instantiation without providing a region? Right now if you create and AmazonOrganizationsClient object without a region an exception is thrown. Would it not make sense for the SDK to default to us-east-1 if no region is provided in the constructor?

Answer

Because AWS Organizations is a global service, there is a single global endpoint for all of the AWS Regions in each partition.  Yes the page here https://docs.aws.amazon.com/general/latest/gr/ao.html that you referenced lists various regions but if you notice, the endpoints are all the same (us-east-1) regardless of the region.  for example:

```

US West (N. California) 	us-west-1

organizations.us-east-1.amazonaws.com

organizations-fips.us-east-1.amazonaws.com

organizations.us-east-1.amazonaws.com
```

AWS Organizations API - us-east-1 for all API and CLI calls

Relevant content