Organizations using AWS CloudFormation StackSets for multi-account deployments often struggle with monitoring and logging. When issues arise, like a critical security baseline failing across multiple accounts, teams face the cumbersome task of logging into each account to diagnose the problem. This manual process not only consumes a lot of time but also complicates incident response and proactive monitoring. The article presents a solution that centralizes CloudFormation logs from various accounts into one management account, streamlining the monitoring process. The proposed architecture includes four main components. First, it sets up a management account with an event bus and log group. Next, target accounts are configured to forward CloudFormation events to this central account using StackSets. The actual resource deployments across accounts generate the events for monitoring. Finally, the solution provides dashboards and queries to help teams gain insights into their deployments. This centralized approach allows administrators to view consolidated logs and set alerts from one location. For implementation, the article outlines two CloudFormation templates. The first template creates the logging infrastructure in the management account, including an event bus with cross-account permissions and a CloudWatch Log Group. The second template deploys common resources to all accounts, enabling automatic logging of CloudFormation events. Step-by-step instructions are provided for deploying these templates using both the AWS CLI and the AWS Console, ensuring that the setup is consistent across all member accounts.