kata-aws-design

To design an AWS architecture with cost estimation, you select AWS services, map data flows, and generate Mermaid diagrams alongside IaC scaffolding and ADRs. This approach ensures Well-Architected pillar coverage, explicit risk analysis, and decomposed monthly cost estimation under budget constraints.

A Well-Architected AWS architecture design document includes service-by-service justification, a Mermaid diagram, IaC scaffolding skeletons, mandatory cost estimation, risk and alternatives analysis, and ADRs for structural decisions across the six Well-Architected pillars.

Yes, you can generate IaC scaffolding skeletons and Mermaid diagrams for an AWS workload automatically. This process maps data flows and selects AWS services while providing service-by-service justification and architecture documentation covering requirements, components, and operations.

AWS architecture design requires explicit alternatives review and ADR generation for structural decisions. This ensures that service selection is justified against the six Well-Architected pillars and that architectural choices are documented for operational reliability and performance.

To estimate monthly AWS costs under budget constraints, you perform a decomposed monthly cost estimation during architecture design. This requires service-by-service justification and mapping expected traffic, SLA targets, and compliance constraints to produce a production-ready AWS blueprint.

Automated AWS architecture design for production workloads requires mandatory cost estimation and explicit risk analysis to mitigate limitations. It relies on provided workflow steps to generate ADRs and IaC scaffolding, ensuring structural decisions meet Well-Architected standards.