How acloudguru-resources/course-certified-solutions-architect-associate works
Main Components
• Labs/Demos: Represent each lab (e.g., “creating-a-static-website-using-amazon-s3”, “creating-an-auto-scaling-group-and-app-load-balancer-aws”, “scaling-ec2-using-sqs”, etc.) as separate modules.
• AWS Services: For each lab, extract the AWS services being demonstrated:
• Static Website Lab: Amazon S3 for hosting static assets.
• Auto Scaling & Load Balancing Lab: EC2 (compute), Auto Scaling Groups, and Elastic Load Balancing.
• EC2 Instance Lab: EC2 and possibly related network components.
• CloudFormation Lab: CloudFormation stacks represented by template files (JSON, YAML) that define infrastructure.
• SQS Lab: Simple Queue Service (SQS) along with sample Python scripts for sending/receiving messages.
• Common Architectural Patterns: Note that many labs showcase fundamental AWS architectural patterns such as stateless vs. stateful design (e.g., using S3 for static hosting) and infrastructure as code (using CloudFormation).
Relationships and Interactions
• How CloudFormation templates are used to provision these resources.
• In the SQS lab, highlight the flow between the EC2 instances (or other compute nodes) and SQS for message-based scaling.
• Dependency and Control Flow: Clearly mark dependencies such as CloudFormation templates triggering configuration or setup of EC2 resources, and how the demos rely on these setups.
Architectural Patterns & Design Principles
• Infrastructure as Code: Emphasize the use of CloudFormation templates to standardize deployments (seen in labs/getting_started_with_cfn).
• Scalability & Resilience: Showcase auto scaling groups and load balancers that indicate principles for building resilient systems.
• Decoupling: With SQS in one lab, show how decoupling of system components is achieved for scalability and fault tolerance.
Incorporate Relevant Technologies
• AWS Components: S3, EC2, Auto Scaling, Elastic Load Balancing, CloudFormation, SQS.
• Programming/Scripting: Python scripts used for sending and receiving messages (as in labs/scaling-ec2-using-sqs) can be noted.
• Configuration Files: JSON and YAML files (from the CloudFormation lab) highlight infrastructure-as-code practices.
Suggested Elements
• Use clear, unambiguous labels for each component (e.g., “Amazon S3 (Static Website Hosting)”, “Auto Scaling Group”, “Elastic Load Balancer”, “EC2 Instances”, “CloudFormation Template”, “SQS Queue”).
• Data flow from the client to the ELB, then to EC2 instances.
• The setup flow from CloudFormation templates to AWS resource provisioning.
• Interaction between EC2 and SQS for scaling events.
• Rectangles for compute/service instances (EC2, S3, SQS).
• Annotations or legends to clarify which parts of the architecture are being demonstrated in each lab.