Automating tagging for resources created by AWS Service Catalog

This article is about automating the process of tagging AWS resources created through AWS Service Catalog with account-level tags. It provides a solution to ensure consistent tagging across multiple AWS accounts by propagating account tags to resources provisioned from Service Catalog portfolios.

Specifically, the article covers:

• Benefits of tagging resources with account tags, including simplified tagging, reduced maintenance, reliable operations, and improved user experience.
• Prerequisites for implementing the solution, such as necessary AWS accounts, permissions, and Service Catalog usage.
• Overview of the solution's architecture, involving EventBridge rules, Lambda functions, and cross-account access to retrieve account tags.
• Detailed walkthrough of deploying the solution using CloudFormation templates in the Management account and delegated administrator accounts.
• Understanding the functionality of the Lambda functions for tag association and cost allocation tag status updates.
• Steps to clean up and remove all resources created by the solution.