CloudPulse provides (near) real-time visibility into the status of AWS CloudFormation Template (CFT) deployments, making it easier to monitor and troubleshoot your infrastructure automation.
Accessing CloudPulse
In order to see CloudPulse in the navigation, users must have project level browse or manage cloud rules permission where a CFT is deployed. If you have permission, CloudPulse is accessible under the Cloud Management section in the main navigation.
Permissions
CloudPulse checks project level permissions to display CFT data. In order to see data in CloudPulse, users can be granted permission in a few different ways:
- Project level Browse/ Manage Cloud Rules permissions enables you to display data on a per-project basis.
- OU level Browse / Manage descendant project cloud rules enables you to display CFT information for specific branches of the Org Char.
- Global permissions like Global Browse / Manage Project Cloud Rules or Global Browse CloudPulse will enable users to see status’ for all CFTs in the system.
- The System-Managed Roles: Admin, Power User, Read-Only Auditor, Security Compliance User, and User grant users the ability to browse the status of all CFTs in the system.
- The System-Managed Roles: Admin and Security Compliance User grant users the ability to browse and manage (take action) for all CFTs in the system.
CFT Status Definitions
CFTs are display as being in of the the following status’:
- Failed: CFT was applied, but a rollback occurred.
- In Progress: CFT has been applied in AWS and waiting for resources to deploy.
- Pending: The CFT is in queue to be applied in AWS.
- Completed: CFT was created in AWS successfully.
How Status is Determined
- Per Region: Each region reports its own CFT status.
- Per Account: An account’s status is determined by the statuses of its regions.
- Per CFT: A CFT’s overall status is determined by the statuses of its accounts and regions.
Priority Order of Statuses
Statuses are evaluated in the following order of severity:
Failed → In Progress → Pending → Completed
- If any region within an account has Failed, the account shows as Failed (even if other regions succeeded).
- If there are no failures, but any region is In Progress, the account shows as In Progress.
- If there are no failures or in-progress deployments, but any region is Pending, the account shows as Pending.
- Only if all regions are Completed does the account show as Completed.
In summary, the displayed status “bubbles up” from the regions to the account, and from the account to the CFT, with Failed taking highest priority and Completed the lowest.
View CFT Status Per Account Per Region
To view the status per account and per region, click the “View Details” button on the CFT row. A drawer will display which lists out each account that the CFT is applied to and their status’.
Actions
For users with the Global Manage CloudPulse or Manage Project Cloud Rules permissions, they can take action on failed CFTs. Users can either reattempt or delete and reattempt CFT deployment for all associated accounts, for a single account, or for a single region.
Users with cloud access roles linked to their account can quickly open stack event logs in the AWS console for a specific region to view more details.