Skip to main content
Beta Cloudeval can review supported AWS CloudFormation JSON and YAML as static infrastructure-as-code. This does not connect to a live AWS account and does not provide Azure/AWS feature parity.

​
Why it matters

Use this workflow to identify applicable template risks before deployment, generate architecture context, and carry evidence into GitHub or CLI review. Unsupported or unavailable evaluation areas must remain Not assessed rather than appearing to pass.

​
Quick example

Start with the public AWS CloudFormation review example.

​
Supported workflow

1

Choose a supported template source

Use CloudFormation JSON or YAML from a local workspace or GitHub-linked project.
2

Confirm the project boundary

For repositories with multiple or nested templates, commit .cloudeval/config.yaml and identify the intended roots and entry templates.
3

Run the review

Use the CLI locally or the GitHub Action in CI. Keep the ref, commit, and source root with the review artifact.
4

Inspect applicability

Review findings, evidence, unsupported resources, and every Not assessed area before making a merge decision.

​
Coverage boundary

Do not describe this workflow as live AWS assessment, full CNAPP coverage, or provider parity. The evidence is limited to the supplied source and supported static evaluation paths.
Last modified on September 1, 2026