Why AWS Well-Architected matters - See It in Action

Why AWS Well-Architected Matters

📖 Scenario: You are starting a new cloud project and want to make sure your setup is strong, safe, and efficient. AWS Well-Architected Framework helps you check your cloud design against best practices.

🎯 Goal: Build a simple AWS infrastructure setup and apply AWS Well-Architected principles step-by-step to understand why it matters for your cloud project.

📋 What You'll Learn

Create a basic AWS resource dictionary with exact resource names and types

Add a configuration variable to track compliance status

Use a loop to check each resource against Well-Architected best practices

Add a final summary status showing if the setup meets AWS Well-Architected standards

💡 Why This Matters

🌍 Real World

AWS Well-Architected Framework helps cloud architects build secure, reliable, and efficient cloud systems by following best practices.

💼 Career

Understanding and applying AWS Well-Architected principles is essential for cloud engineers and architects to ensure high-quality cloud infrastructure.

1

Create AWS Resources Dictionary

Create a dictionary called aws_resources with these exact entries: 'EC2Instance': 't2.micro', 'S3Bucket': 'my-app-data', 'RDSInstance': 'db.t3.micro'

AWS

# Create the aws_resources dictionary with the specified entries
# Your code here

Hint

Use curly braces to create a dictionary with keys and values exactly as shown.

2

Add Compliance Status Variable

Add a variable called compliance_status and set it to True to track if all resources meet AWS Well-Architected standards.

AWS

aws_resources = {
    'EC2Instance': 't2.micro',
    'S3Bucket': 'my-app-data',
    'RDSInstance': 'db.t3.micro'
}
# Add compliance_status variable here
# Your code here

Hint

Set compliance_status to True to start assuming all resources comply.

3

Check Resources Against Best Practices

Use a for loop with variables resource and type to iterate over aws_resources.items(). Inside the loop, if type is 't2.micro', set compliance_status to False because this instance type is not recommended for production.

AWS

aws_resources = {
    'EC2Instance': 't2.micro',
    'S3Bucket': 'my-app-data',
    'RDSInstance': 'db.t3.micro'
}
compliance_status = True
# Add for loop to check resource types
# Your code here

Hint

Use for resource, type in aws_resources.items(): and check if type == 't2.micro'.

4

Add Final Compliance Summary

Add a variable called final_summary and set it to 'Compliant' if compliance_status is True, otherwise set it to 'Non-Compliant'.

AWS

aws_resources = {
    'EC2Instance': 't2.micro',
    'S3Bucket': 'my-app-data',
    'RDSInstance': 'db.t3.micro'
}
compliance_status = True
for resource, type in aws_resources.items():
    if type == 't2.micro':
        compliance_status = False
# Add final_summary variable here
# Your code here

Hint

Use a conditional expression to set final_summary based on compliance_status.

Practice

1. What is the main purpose of the AWS Well-Architected Framework?

easy

A. To provide free cloud storage for users

B. To create custom AWS services automatically

C. To replace all manual cloud management tasks

D. To help build better cloud systems by focusing on key areas

Solution

1. Step 1: Understand the AWS Well-Architected Framework goal

   The framework is designed to guide users in building reliable and efficient cloud systems.

2. Step 2: Compare options to the framework's purpose

   Only To help build better cloud systems by focusing on key areas correctly states the framework's main goal of focusing on key areas to improve cloud systems.

3. Final Answer:

   To help build better cloud systems by focusing on key areas -> Option D

4. Quick Check:

   AWS Well-Architected Framework = Build better systems [OK]

Hint: Focus on the framework's goal to improve cloud systems [OK]

Common Mistakes:

• Thinking it provides free storage
• Believing it automates all tasks
• Assuming it creates services automatically

2. Which of the following is a correct statement about the AWS Well-Architected Framework?

easy

A. It focuses on six key pillars to improve cloud projects

B. It guarantees zero downtime for all AWS services

C. It is only useful for large companies with complex systems

D. It replaces the need for security best practices

Solution

1. Step 1: Recall the framework's focus areas

   The AWS Well-Architected Framework focuses on six key pillars to guide cloud design.

2. Step 2: Evaluate each option

   It focuses on six key pillars to improve cloud projects correctly states the framework's focus. Options B, C, and D are incorrect because the framework does not guarantee zero downtime, is useful for all sizes, and does not replace security practices.

3. Final Answer:

   It focuses on six key pillars to improve cloud projects -> Option A

4. Quick Check:

   Six key pillars = Framework focus [OK]

Hint: Remember the framework's six key pillars [OK]

Common Mistakes:

• Assuming it guarantees zero downtime
• Thinking it's only for big companies
• Believing it replaces security rules

3. Consider this statement: "Using AWS Well-Architected Framework helps save time and money." What is the most likely reason for this?

medium

A. It helps identify and fix design issues early

B. It replaces the need for cloud monitoring tools

C. It provides unlimited free AWS credits

D. It automates all cloud tasks without user input

Solution

1. Step 1: Understand how the framework saves resources

   The framework helps find design problems early, avoiding costly fixes later.

2. Step 2: Analyze each option

   It helps identify and fix design issues early correctly explains the saving of time and money by early issue detection. Options A, B, and C are incorrect because the framework does not automate all tasks, replace monitoring tools, or provide free credits.

3. Final Answer:

   It helps identify and fix design issues early -> Option A

4. Quick Check:

   Early issue detection = Save time and money [OK]

Hint: Early fixes save time and money [OK]

Common Mistakes:

• Thinking it automates everything
• Believing it gives free credits
• Assuming it replaces monitoring

4. A team claims they do not need the AWS Well-Architected Framework because their cloud system is small and simple. What is the main issue with this thinking?

medium

A. The framework is only for large systems, so their claim is correct

B. Small systems do not benefit from any cloud best practices

C. All cloud systems benefit from the framework regardless of size

D. The framework is only for security, not system design

Solution

1. Step 1: Understand the framework's applicability

   The AWS Well-Architected Framework is designed to help all cloud systems, big or small.

2. Step 2: Evaluate the team's claim

   The claim is incorrect because even small systems benefit from best practices. All cloud systems benefit from the framework regardless of size correctly states this. Options A, B, and D are false.

3. Final Answer:

   All cloud systems benefit from the framework regardless of size -> Option C

4. Quick Check:

   Framework helps all sizes = True [OK]

Hint: Framework helps all cloud sizes [OK]

Common Mistakes:

• Believing it's only for large systems
• Ignoring best practices for small systems
• Thinking it's only about security

5. A company wants to improve their cloud system using the AWS Well-Architected Framework. Which of these steps should they take first?

hard

A. Immediately migrate all data to a new AWS region

B. Review their system against the six key pillars of the framework

C. Disable all monitoring to reduce costs

D. Replace their cloud team with automated tools

Solution

1. Step 1: Identify the correct first step in using the framework

   The framework's first step is to review the system against its six key pillars to find improvement areas.

2. Step 2: Analyze the other options

   Options B, C, and D are incorrect because migrating data immediately, disabling monitoring, or replacing the team are not recommended first steps.

3. Final Answer:

   Review their system against the six key pillars of the framework -> Option B

4. Quick Check:

   Start with framework review = Correct first step [OK]

Hint: Start by reviewing system with framework pillars [OK]

Common Mistakes:

• Jumping to migration without review
• Disabling monitoring to save money
• Replacing team with automation immediately