How to Evaluate the "Well-Architectedness" of Your Proposed Solution
Once you have visually mapped out your application in Application Composer and generated your template, you must validate it against the AWS Well-Architected Framework. Because Application Composer generates structured templates, evaluating your design becomes an automated, structured process:
Step 1: Use the Template to Run an Official AWS Well-Architected Review
For your certification preparation, understand that the official approach is to use the AWS Well-Architected Tool in the AWS Console.
Open the AWS Well-Architected Tool in your AWS sandbox account.
Define a new "Workload" and upload or describe the architectural choices generated by your Application Composer canvas.
Walk through the core questionnaire across the 6 pillars (Security, Reliability, Performance Efficiency, Cost Optimization, Operational Excellence, and Sustainability). The tool will flag any High-Risk Issues (HRIs) in your proposal.
Step 2: Validate the Generated Code Against Best-Practice Linters
Because Application Composer gives you a CloudFormation/SAM file, you can run automated, free scanners directly against your design file before deploying it. This tests the Security and Operational Excellence pillars:
Use cfn-nag or Checkov: These are free static analysis tools. If you run them against the code file generated by Application Composer, they will immediately read your design choices and warn you if you missed something (e.g., "Warning: CloudFront distribution missing a Web Application Firewall (WAF)").
Step 3: Check Your Boundaries and Integrations on the Canvas
While looking at your canvas, check your architectural decisions against these common Well-Architected exam patterns:
No comments:
Post a Comment