Feature Request: Account-level configuration store in AWS Organizations

Question

Today, AWS Organizations allows attaching up to 50 tags (256 characters each) to an account. While useful for basic metadata, this is too limited for real-world scenarios where teams need to store richer, structured configuration tightly coupled to an account.

**The problem**
As organizations grow, teams need to associate structured metadata with accounts beyond simple tags. Examples include:
- Allowed regions list
- Compliance profiles (e.g. PCI-DSS, HIPAA)
- Budget thresholds
- Team contacts and escalation paths
- Feature flags per account

Today, workarounds involve maintaining a separate DynamoDB table or SSM parameters with naming conventions like /org/accounts/{accountId}/config, but these are disconnected from the account lifecycle — they don't get cleaned up when accounts are closed, and they require custom automation to stay in sync.

**The ask**
A native account-level configuration store in AWS Organizations, similar to SSM Parameter Store, that is:

- Tightly coupled to the account lifecycle (created/deleted with the account)
- Accessible via the Organizations API
- Supports JSON or YAML values up to at least 8KB
- Respects SCPs and Organizations policies for access control
- Readable by the account itself via a cross-account mechanism

**Prior art**
This is similar to how Kubernetes annotations work alongside labels — labels (tags) for selection/filtering, annotations for richer metadata.

**Impact**
This would simplify account vending pipelines, reduce custom automation, and make account metadata a first-class citizen in AWS Organizations.

re:Post Agent · Answer

Thank you for this detailed feature request. I can see how this would address real operational challenges in managing account metadata at scale.

Currently, AWS Organizations provides account management capabilities including tags for basic metadata, organizational units for logical grouping, and policies for governance. The 50-tag limit you mentioned is indeed a constraint when teams need to store richer, structured configuration data.

Your observation about existing workarounds is accurate. Organizations today do use external storage solutions like DynamoDB or Systems Manager Parameter Store with naming conventions to store account-specific configuration. As you noted, these approaches require custom automation to maintain synchronization with the account lifecycle, particularly around account closure events. AWS Organizations has recently introduced more granular account state information (including states like PENDING_CLOSURE and CLOSED) to help track account lifecycle, but this doesn't solve the configuration storage challenge you're describing.

The concept you're proposing—a native configuration store tightly coupled to account lifecycle, accessible via Organizations APIs, supporting structured data formats, and respecting existing policy controls—would indeed represent a significant enhancement to how account metadata is managed. Your comparison to Kubernetes' distinction between labels and annotations is apt: tags serve well for filtering and selection, while a separate configuration mechanism could handle richer metadata needs.

For submitting this feature request formally, I'd recommend using the AWS Support Center to provide this feedback directly to the AWS Organizations product team. They actively review customer feature requests and use them to inform the service roadmap. When submitting, including the specific use cases you've outlined (compliance profiles, budget thresholds, team contacts, feature flags) along with the operational pain points of current workarounds will help the team understand the business value.  
**Sources**  
[AWS Organizations launches account state information for granular account lifecycle management | AWS Cloud Operations Blog](https://aws.amazon.com/blogs/mt/updates-to-account-status-information-in-aws-organizations/)  
[Community | Manage Security and Costs Across the Enterprise With AWS Organizations](https://community.aws/tutorials/practical-cloud-guide/manage-security-and-costs-across-the-enterprise-with-aws-organizations)

Feature Request: Account-level configuration store in AWS Organizations

Add your answer

Relevant content