aws-org-strategy

Name: aws-org-strategy
Availability: InStock
Author: jason-c-dev

Plan AWS organization structures, OUs, and workload placement across accounts.

1|Updated Jan 29, 2026

Search Tags:#aws #governance #guardrails #organizations #multi-account #landing-zone #ou

Ready to run

npx skills add https://github.com/jason-c-dev/aws-coworker-enterprise --skill aws-org-strategy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aws-org-strategy
Source: https://github.com/jason-c-dev/aws-coworker-enterprise/tree/main/skills/org/aws-org-strategy
Command: npx skills add https://github.com/jason-c-dev/aws-coworker-enterprise --skill aws-org-strategy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codifies and guides multi-account AWS organization strategies, covering OU structures, landing zone patterns, workload placement rules, and governance considerations to standardize enterprise-scale deployments.

Core Features & Use Cases

Organization patterns (Single Account, Multi-Account Basic, Multi-Account with OUs, Control Tower)
Account types and governance guidelines (Management, Security/Audit, Log Archive, Shared Services, Workloads, Sandbox)
OU policies and guardrails with example SCPs and policy recommendations
Workload placement decision framework, CIDR planning, and provisioning considerations
Migration paths, templates, and customization guidance for different organizational scales

Quick Start

Customize the organization structure by updating templates, documenting your OU layout, account provisioning process, and tagging standards.

Frequently Asked Questions about aws-org-strategy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I structure a multi-account AWS organization for enterprise scale?▼

To structure a multi-account AWS organization, you should group accounts into Organizational Units (OUs) based on functional boundaries like Security, Log Archive, Shared Services, and Workloads, applying Service Control Policies (SCPs) to enforce governance guardrails across the hierarchy.

What is the best way to decide workload placement across multiple AWS accounts?▼

Workload placement across multiple AWS accounts is determined by a decision framework evaluating isolation requirements, data sensitivity, and network CIDR planning to ensure proper separation of duties, billing isolation, and blast radius containment within your landing zone.

How do I implement guardrails and SCPs in an AWS landing zone?▼

Implement guardrails in an AWS landing zone by attaching Service Control Policies (SCPs) to specific Organizational Units (OUs), enforcing preventative controls that restrict account actions and standardize security compliance across the organizational hierarchy.

When do I need a multi-account AWS strategy instead of a single account?▼

You need a multi-account AWS strategy instead of a single account when you require strict isolation of workloads, isolated billing for different business units, or distinct security perimeters to minimize blast radius and simplify governance at enterprise scale.

Can I use AWS Control Tower patterns for multi-account governance?▼

Yes, you can use AWS Control Tower patterns for multi-account governance to automate the provisioning of landing zones, enforce baseline guardrails, and manage accounts through pre-configured Organizational Units and organizational-level policies.

How do I document account provisioning and tagging conventions for AWS Organizations?▼

Document account provisioning and tagging conventions for AWS Organizations by updating the strategy templates to define your OU layout, specify account creation workflows, and standardize tag keys for cost allocation and resource tracking.