fieldnotes

Pathfinding updates to Organizations API methods

2026-04-02

What’s this one all about then ?

This week AWS sneaked out a change to the AWS Organizations API, and its got a bigger benefit than you might think if you have never worked with Organizations via automation.

Account and organizational unit (OU) objects now include path information in API responses. Account APIs (such as DescribeAccount and ListAccounts) and OU APIs (such as DescribeOrganizationalUnit) return a path field showing where entities exist within an organization.

Pathfinding in Organizations

The simple version: all methods on the Organizations API now support a path, because the path field has been added to Account and OrganizationalUnit objects in AWS Organizations API responses.

It’s on every method on this API, which makes complete sense, because path is a property for any/all actions on the Organizations API.

The more complex version: Organizations has always supported an N-level hierarchy for managing and grouping AWS Accounts within an Organization and organization Units (OUs) within an Organziation. But until now, you’ve never been able to use the hierarchical path as the means to navigate or automate these actions. If you’re using the Organizations UI, it probably feels like a natural thing to do to expand and collapse the Organization hierarchy, and the UI has hidden the requirement to traverse paths.

But if you work with Organizations programmatically, you’ve not had the ability to do the equivalent of Unix’s cd .. (or cd ../../../../), let alone being able to do that using regular expressions which match certain path contents before taking actions like applying policies or moving things around.

The new path method now supports regular expressions to enumerate and navigate paths:

The wrap up

Its great to see Organizations API get these new methods added in, in our view some of these older APIs have not had enough attention with the rapid growth of AWS services.

Back to awyspr fieldnotes index