Prevent non-compliant CloudFormation templates from entering your infrastructure
Last updated: 14 January 2020
Relevant users
| Technical Team member |  |
| DevOps Team member | |
| Security Analyst | |
| Security Engineer | |
| Compliance Manager | |
| Project Manager | |
| Security Team Management | |
| Consultant | |
Examples
- I have a new CloudFormation template and I want to ensure that it follows cloud infrastructure best practises.
- I have an updated CloudFormation template and I want to ensure that changes it would make are compliant with my organisation’s governance policy.
Cloud Conformity Solution
Step 1. If you haven’t already, Setup Template Scanner for your organisation.
Step 2. Scan your CloudFormation template by:
The Template Scanner API can be used on a case by case basis, or it can be integrated into your CI/CD deployment process for automated governance.
Template Scanner will check your AWS resources for compliance against Cloud Conformity’s rule set, and Checks will be displayed as Passed or Failed.
Step 3. Review and remediate failed checks to meet your organisation’s governance requirements
Step 4. Repeat steps 2 and 3 until your organisation’s governance requirements have been met
Step 5.