Using the AWS Organization API with Postman

Photo by Mathyas Kurmann on Unsplash

I’ve been implementing AWS Control Tower and as I began migrating accounts from our legacy organization to a new one, I wanted to capture meta data with each account. As I was capturing information in Confluence like account alias, account number, and root email I wanted to see what information I could extract from the organizations api. I’ve had an opportunity to interact with other AWS api using postman for IAM, EC2, and route53.

Service URL

On of the things that was challenge for me initially was figuring out the service URL. This page defines Service URL’s and names.

Regional endpoints

Most Amazon Web Services offer a Regional endpoint that you can use to make your requests. The general syntax of a Regional endpoint is as follows.

protocol://service-code.region-code.amazonaws.com

For example, https://dynamodb.us-west-2.amazonaws.com is the endpoint for the Amazon DynamoDB service in the US West (Oregon) Region.

The definition above is important. The service-code is what’s used in Authorization section. The field Service Name will be populated with this value. For the organizations api, it’s a global resource and the endpoint is defined in the us-east-1 region.

Endpoint to call When…