aws-architect

To design an AWS architecture using the Well-Architected Framework, describe your environment and constraints. The process starts with targeted discovery questions, then evaluates pillars like Security, Reliability, and Cost Optimization to propose services with explicit trade-offs.

The best way to review an existing AWS architecture for cost and resilience is to assess it against Well-Architected pillars. This evaluates your current service configurations, identifies trade-offs, and provides implementation notes for optimization.

Yes, a security review is mandatory when modifying AWS infrastructure as code. Any proposed IaC changes must trigger a security review pass, using the iac-reviewer subagent or security-review skill to validate configurations before implementation.

Yes, you can evaluate AWS service trade-offs when planning a multi-tier web application. The architecture proposal specifies exact AWS services and configurations while outlining explicit trade-offs across Operational Excellence, Performance, and Sustainability pillars.

The discovery process for new AWS infrastructure planning begins with 3 to 5 high-signal questions about your environment. It progressively follows up based on your answers to ensure the resulting architecture design matches your specific constraints.