Improve Cost Visibility and Observability with AWS Cost Categories

Hierarchical Structures and Programmatic Implementation

Cloud cost optimization isn’t just about lowering bills, it’s about understanding where costs are happening and why. As cloud environments grow in scale and complexity, teams need reporting structures that reflect the organizational hierarchy and automation to maintain consistent cost visibility across all environments.

Why Hierarchical Cost Categories Matter?

AWS Cost Categories let you define custom groupings of AWS costs beyond basic AWS billing dimensions to reflect business-specific structures. A hierarchical setup lets you model parent-child relationships among categories (for example, Departments, Teams, Business Units), so cost visibility aligns with how your organization operates.

Example Structure:

• Department
• SecOps
• Resilience Engineering
• InfoSec Operations
• App Foundry
• Compute
• Network
• GenAI
• Storage

Instead of flat cost lists, this logical hierarchy shows related spend roll-ups and drilldowns across teams and departments.

Setting Up Hierarchical Cost Categories

To implement a multi-level hierarchy:

• Create child categories – e.g., “SecOps” and “App Foundry,” with rules that determine which services or accounts belong under each value.
• Create a parent category – e.g., “Department,” and map the child categories under it by using the Cost Category dimension.
• Save changes and allow up to 24 hours for AWS to fully apply and reflect this structure in tools like AWS Cost Explorer.

Once applied, you’ll see spend mapped against these business-aligned categories in cost dashboards and reports.

Hierarchical cost categories provide consistent classification and reporting across a wide range of AWS cost tools, including Cost Explorer, AWS Budgets, AWS Billing Conductor, and Cost & Usage Reports.

Programmatic Management with APIs and JSON

Instead of manually creating Cost Categories through the console, you can automate creation and updates using:

AWS CLI or SDK

You invoke the CreateCostCategoryDefinition API with:

• A unique category name
• A rule version (typically CostCategoryExpression.v1)
• A set of rules that define how costs are mapped

Sample CLI snippet:

The resulting category behaves identically to one created via the AWS Console.

JSON Editor

Instead of CLI, AWS also supports a JSON rule editor that lets you define or edit Cost Categories directly using structured JSON, enabling repeatable and version-controlled implementations.

Cleanup: Removing Test or Legacy Categories

If you created Cost Categories for experimentation or have categories that are no longer useful:

• Go to the AWS Cost Categories console
• Choose the category you want to delete
• Confirm deletion

Notes:

• Cost Categories are a free, non-billing feature
• Deletion can not be undone
• Historical reports won’t include deleted categories after they are removed
• It may take up to 24 hours for delete operations to finish processing

Conclusion

Hierarchical cost categories combined with programmatic creation offer:

• Scalable cost management for complex enterprise environments
• Business-aligned reporting at multiple levels
• Automation that supports consistent governance
• Deeper cost observability for teams, departments, and projects

By applying these techniques, organizations can dramatically improve financial governance and ensure cost transparency aligns with real business structures.

Drop a query if you have any questions regarding AWS Cost Categories and we will get back to you quickly.

About CloudThat