Naming Conventions¶

TagOps Naming Conventions let you define how resource names should be built and validated across your AWS footprint. You create rules from reusable blocks (for example environment, project, or service short names), pick a case style (PascalCase, snake_case, kebab-case, and others), and define the order of segments in each name. Rules can be attached to accounts so TagOps can evaluate existing resources against your standards.

Compliance views show which resources match or violate the active rules. You can acknowledge exceptions where needed, recalculate compliance after changes, and use the console flows to align names with your policies.

For step-by-step setup, rule types, blocks, structure, and operations in the UI, see the Naming Conventions user guide.

Video walkthrough¶

The following video walks through TagOps naming conventions end to end. If the player does not appear, watch on YouTube.