kata-aws-review

Perform a systematic AWS architecture review by checking Terraform, CDK, or CloudFormation changes against the Well-Architected Framework pillars, mapping findings to defined reference controls, and consolidating results into a severity-structured Markdown report with an ordered improvement plan.

Yes, an AWS architecture review can integrate optional static tooling such as tfsec, cdk-nag, and infracost to gather evidence, which is then consolidated with manual checks into a single structured Markdown report for the team.

Yes, the AWS architecture review process supports CloudFormation changes in pull requests alongside Terraform and CDK, evaluating Security, IaC, Cost, Reliability, Performance, and Operational Excellence pillars to produce PR-ready outputs.

Prioritize AWS Infrastructure-as-Code remediation by generating a consolidated report that classifies findings by severity and maps them to Well-Architected Framework references, resulting in an ordered improvement plan for follow-up iterations.

You can evaluate existing AWS workload inventories without active pull requests, as the architecture review process applies to both IaC changes and existing workload documentation by gathering context and mapping findings to recognized guidance.

The AWS IaC review requires sufficient context gathering from architecture documents or codebases to map findings to Lexis and Well-Architected references, meaning incomplete infrastructure context may limit the evidence-backed severity classification of the final report.