Studio Project workflows for AWS Organizations accounts, organizational units, and policies
AWS Organizations is AWS's account-management service for centrally governing multiple AWS accounts — creating and closing accounts, grouping them into organizational units, attaching service control and other policies, managing invitations between accounts, registering delegated administrators, and tagging organizational resources.
This project provides the OpenAPI spec for automating against the AWS Organizations API via an Integration Model.
| Asset | Description |
|---|---|
| OpenAPIs/ | AWS Organizations API OpenAPI spec — -latest plus the full dated spec |
| Studio Projects/AWS Organizations | 25 workflows covering common CRUD automation |
| Requirement | Version |
|---|---|
| Itential Platform | 6.x |
| AWS Organizations API | 2016-11-28 |
| AWS Organizations Integration Model | Required to build automation against the OpenAPI spec |
Import the OpenAPI spec from OpenAPIs/ as an Integration Model in Admin > Integrations, then create an integration pointing at the AWS Organizations endpoint for your region (e.g. organizations.us-east-1.amazonaws.com).
Authentication uses AWS Signature Version 4, signed with an AWS access key ID and secret access key, sent in the Authorization header:
Authorization: AWS4-HMAC-SHA256 Credential=<access-key-id>/<date>/<region>/organizations/aws4_request, ... Generate an access key ID and secret access key for an IAM principal with the appropriate Organizations permissions in the AWS IAM console under Security credentials. Note that most Organizations API calls must be made from (or on behalf of) the organization's management account or a registered delegated administrator account.
The instance's authentication/server properties should look like this once configured:
{
"authentication": {
"hmac": {
"accessKeyId": "<your-aws-access-key-id>",
"secretAccessKey": "<your-aws-secret-access-key>",
"sessionToken": ""
}
},
"server": {
"protocol": "https",
"host": "organizations.us-east-1.amazonaws.com",
"base_path": ""
}
} | Spec | Version | Operations | Description |
|---|---|---|---|
aws_organizations-latest.json | latest (curated) | 55 | Actively-maintained spec, all operations are genuine CRUD/provisioning actions — see breakdown below |
aws_organizations-2016-11-28.json | 2016-11-28 | 55 | Full spec |
aws_organizations-latest.jsonActively-maintained spec (x-vendor-api-version: 2016-11-28, 55 operations, all POST against the single AWS Query-protocol endpoint with an X-Amz-Target action header). Every operation is a genuine CRUD or provisioning action on an Organizations business resource (account, OU, policy, handshake, delegated administrator, service access, resource policy, or tag) — there is no separate health/heartbeat/metrics, self-introspection/version-info, or "about" surface to exclude, so nothing was removed.
Operations included, by category:
CreateAccount/CreateGovCloudAccount job)aws_organizations-2016-11-28.jsonFull spec for AWS Organizations API version 2016-11-28 (55 operations) — the entire upstream API surface as AWS defines it. See aws_organizations-latest.json above for the curated subset if you just need common CRUD automation.
Backed by the AWS Organizations:latest Integration Model (see aws_organizations-latest.json above). The project contains 25 workflows organized into 5 folders, one atomic workflow per API operation, covering the common-CRUD subset of the curated spec. This is an AWS JSON/Query-protocol API — every operation is a POST distinguished by a required X-Amz-Target header, which each workflow exposes as an input alongside the request body.
| Folder | Workflows | Scope |
|---|---|---|
| Organization | Create, Describe, Delete Organization, List Roots | Organization lifecycle |
| Accounts | Create, Describe, List, Move, Close Account | Account management |
| Organizational Units | Create, Describe, Update, Delete Organizational Unit, List Organizational Units For Parent, List Children | OU hierarchy management |
| Policies | Create, Describe, Update, Delete, List Policy, Attach, Detach Policy | Policy management |
| Tags | List, Tag, Untag Resource | Tagging management |
| Dependency | Notes |
|---|---|
AWS Organizations:latest Integration Model | Import from aws_organizations-latest.json before importing the project |
AWS Organizations integration instance | Create in Admin > Integrations with the connection properties above. Workflows are wired to an integration instance named AWS Organizations — update the adapter_id value in each workflow task if yours is named differently |