Implement Infrastructure Tagging
Apply consistent resource tagging across all infrastructure in new accounts.
- Standard tags for all resources:
Name- Resource identifierEnvironment- prod, nonprod, toolingComponent- Portal, Astrata Accounting, Event Manager, etc. (align with Jira Component field)Purpose- (when helpful distinction needed)Client- (when resource is client-specific)- Enforce tagging via IaC templates/modules
- Configure tag-based cost allocation reports
- Set up tag compliance monitoring
- Document tagging standards for team reference
Open questions:
- Should tagging be enforced via AWS Organizations SCPs?
- Are there additional tags needed for compliance or audit?