Scan and fix security issues in your CloudFormation files (current IaC)
PreviousConfigure your integration to find security issues in your CloudFormation files (current IaC)NextScan Kubernetes configuration files
Last updated
Last updated
More information
Snyk privacy policy© 2024 Snyk Limited | All product and company names and logos are trademarks of their respective owners.
This page applies to current IaC only.
Snyk scans CloudFormation code for misconfigurations and security issues. After configuration files are scanned, Snyk reports on any misconfigurations based on the settings that administrators implement and makes recommendations for fixes accordingly.
An administrator integrates the Organization with a preferred Git repository and enables the detection of configuration files as described in Configure your integration to find security issues in your CloudFormation files.
The Snyk account and CloudFormation files are in JSON and YAML formats.
Log in to the account and navigate to the relevant Group and Organization.
If you imported your repositories for testing before the infrastructure as code feature was enabled by your administrator, from the Add project screen, re-import that repository in order to detect the CloudFormation code:
Every time a repository is scanned, every CloudFormation file is imported as a separate Project, grouped together per repository, similar to the example shown.
If you re-imported the repository in order to import the CloudFormation files, then Snyk imports and re-tests the already imported application manifest files, displaying the test time as "now".
Click a Project link to view the scan results and details for the CloudFormation code:
