Performance efficiency pillar in AWS - Mini Project: Build & Apply

Implementing AWS Performance Efficiency Pillar Basics

📖 Scenario: You are working as a cloud engineer for a small e-commerce startup. The company wants to ensure their AWS infrastructure is designed to be efficient and scalable as their user base grows. You will create a simple AWS CloudFormation template to set up an EC2 Auto Scaling group with a load balancer to distribute traffic efficiently.

🎯 Goal: Build a CloudFormation template that defines an EC2 Auto Scaling group with a launch configuration and an Application Load Balancer. This setup will help the application handle varying traffic loads efficiently, demonstrating the Performance Efficiency pillar of AWS Well-Architected Framework.

📋 What You'll Learn

Create a Launch Configuration named MyLaunchConfig with instance type t3.micro and Amazon Linux 2 AMI.

Create an Auto Scaling Group named MyAutoScalingGroup using MyLaunchConfig with minimum size 1 and maximum size 3.

Create an Application Load Balancer named MyLoadBalancer with a listener on port 80.

Attach the Auto Scaling Group to the Load Balancer target group.

💡 Why This Matters

🌍 Real World

This project models a common real-world scenario where applications need to handle changing traffic efficiently using AWS Auto Scaling and Load Balancing.

💼 Career

Understanding how to implement scalable infrastructure on AWS is essential for cloud engineers and architects to ensure performance efficiency in production environments.

1

Create the Launch Configuration

Write the CloudFormation YAML code to create a Launch Configuration named MyLaunchConfig with instance type t3.micro and Amazon Linux 2 AMI. Use the parameter AmiId for the AMI ID.

AWS

# Your code here to create MyLaunchConfig launch configuration

Hint

The Launch Configuration defines the EC2 instance settings for the Auto Scaling Group.

2

Create the Auto Scaling Group

Add CloudFormation YAML code to create an Auto Scaling Group named MyAutoScalingGroup that uses the MyLaunchConfig launch configuration. Set the minimum size to 1 and maximum size to 3. Use MyTargetGroup as the target group for the load balancer.

AWS

Resources:
  MyLaunchConfig:
    Type: AWS::AutoScaling::LaunchConfiguration
    Properties:
      ImageId: !Ref AmiId
      InstanceType: t3.micro

# Your code here to create MyAutoScalingGroup

Hint

The Auto Scaling Group manages the number of EC2 instances based on demand.

3

Create the Application Load Balancer and Target Group

Add CloudFormation YAML code to create an Application Load Balancer named MyLoadBalancer with a listener on port 80. Also create a Target Group named MyTargetGroup for the Auto Scaling Group to register instances.

AWS

Resources:
  MyLaunchConfig:
    Type: AWS::AutoScaling::LaunchConfiguration
    Properties:
      ImageId: !Ref AmiId
      InstanceType: t3.micro

  MyAutoScalingGroup:
    Type: AWS::AutoScaling::AutoScalingGroup
    Properties:
      LaunchConfigurationName: !Ref MyLaunchConfig
      MinSize: 1
      MaxSize: 3
      TargetGroupARNs:
        - !Ref MyTargetGroup
      VPCZoneIdentifier:
        - subnet-12345678
        - subnet-87654321

# Your code here to create MyLoadBalancer and MyTargetGroup

Hint

The Load Balancer distributes incoming traffic to the instances in the Auto Scaling Group.

4

Add Parameters and Outputs

Add a CloudFormation parameter named AmiId of type AWS::SSM::Parameter::Value to allow dynamic AMI selection. Also add an output named LoadBalancerDNS that outputs the DNS name of MyLoadBalancer.

AWS

Resources:
  MyLaunchConfig:
    Type: AWS::AutoScaling::LaunchConfiguration
    Properties:
      ImageId: !Ref AmiId
      InstanceType: t3.micro

  MyAutoScalingGroup:
    Type: AWS::AutoScaling::AutoScalingGroup
    Properties:
      LaunchConfigurationName: !Ref MyLaunchConfig
      MinSize: 1
      MaxSize: 3
      TargetGroupARNs:
        - !Ref MyTargetGroup
      VPCZoneIdentifier:
        - subnet-12345678
        - subnet-87654321

  MyLoadBalancer:
    Type: AWS::ElasticLoadBalancingV2::LoadBalancer
    Properties:
      Name: MyLoadBalancer
      Subnets:
        - subnet-12345678
        - subnet-87654321
      Scheme: internet-facing

  MyTargetGroup:
    Type: AWS::ElasticLoadBalancingV2::TargetGroup
    Properties:
      Name: MyTargetGroup
      Port: 80
      Protocol: HTTP
      VpcId: vpc-12345678

  MyListener:
    Type: AWS::ElasticLoadBalancingV2::Listener
    Properties:
      LoadBalancerArn: !Ref MyLoadBalancer
      Port: 80
      Protocol: HTTP
      DefaultActions:
        - Type: forward
          TargetGroupArn: !Ref MyTargetGroup

# Your code here to add AmiId parameter and LoadBalancerDNS output

Hint

Parameters allow dynamic input. Outputs show important information after deployment.

Practice

1. What is the main goal of the AWS Performance Efficiency pillar?

easy

A. To make sure your system runs fast and adapts to changes

B. To secure your data from unauthorized access

C. To reduce the cost of your cloud resources

D. To organize your cloud resources in a neat way

Solution

1. Step 1: Understand the purpose of the Performance Efficiency pillar

   This pillar focuses on how well your system performs and adapts to changes in demand. Only To make sure your system runs fast and adapts to changes talks about running fast and adapting, which matches the pillar's goal.

2. Final Answer:

   To make sure your system runs fast and adapts to changes -> Option A

3. Quick Check:

   Performance Efficiency = Fast and adaptable system [OK]

Hint: Performance means speed and adaptability [OK]

Common Mistakes:

• Confusing performance with security
• Thinking cost reduction is the main goal
• Mixing organization with performance

2. Which AWS service helps automatically adjust the number of servers to meet demand?

easy

A. Amazon S3

B. Amazon RDS

C. AWS IAM

D. AWS Auto Scaling

Solution

1. Step 1: Identify the service that adjusts server count automatically

   AWS Auto Scaling changes the number of servers based on demand. Eliminate unrelated services: Amazon S3 stores files, Amazon RDS manages databases, and AWS IAM controls access, so they don't adjust server numbers.

2. Final Answer:

   AWS Auto Scaling -> Option D

3. Quick Check:

   Auto Scaling = Adjust servers automatically [OK]

Hint: Auto Scaling means automatic server adjustment [OK]

Common Mistakes:

• Choosing storage or database services instead
• Confusing IAM with scaling
• Not knowing what Auto Scaling does

3. Given this AWS setup: An application uses an Elastic Load Balancer (ELB) with Auto Scaling enabled. What happens when user traffic suddenly doubles?

medium

A. The application crashes due to overload

B. The ELB rejects extra traffic to keep servers stable

C. Auto Scaling adds more servers and ELB distributes traffic evenly

D. Auto Scaling removes servers to save costs

Solution

1. Step 1: Understand ELB and Auto Scaling roles

   ELB spreads traffic across servers; Auto Scaling adds servers when demand rises. Auto Scaling will add servers to handle more users, and ELB will balance the load.

2. Final Answer:

   Auto Scaling adds more servers and ELB distributes traffic evenly -> Option C

3. Quick Check:

   More traffic = More servers + balanced load [OK]

Hint: More traffic triggers Auto Scaling and ELB balances load [OK]

Common Mistakes:

• Thinking ELB rejects traffic
• Assuming the app crashes immediately
• Believing Auto Scaling removes servers on high load

4. You set up Auto Scaling but notice your application still slows down under heavy load. What is a likely cause?

medium

A. Auto Scaling is not configured with proper scaling policies

B. You used an Elastic Load Balancer correctly

C. Your database is too fast

D. You enabled monitoring and alerts

Solution

1. Step 1: Check Auto Scaling configuration

   If scaling policies are missing or incorrect, Auto Scaling won't add servers when needed. Using ELB correctly helps performance, a fast database is good, and monitoring helps detect issues, so they are not causes.

2. Final Answer:

   Auto Scaling is not configured with proper scaling policies -> Option A

3. Quick Check:

   Wrong scaling policies cause slow response [OK]

Hint: Check scaling policies if Auto Scaling fails [OK]

Common Mistakes:

• Blaming ELB when it's set up right
• Thinking a fast database causes slowdowns
• Ignoring the importance of scaling policies

5. You want to improve performance for a web app with unpredictable traffic spikes. Which combination best follows the Performance Efficiency pillar?

hard

A. Use fixed-size servers and manual traffic routing

B. Use Auto Scaling with Elastic Load Balancer and fast SSD storage

C. Use a single large server and no monitoring

D. Use slow storage but increase server size manually

Solution

1. Step 1: Identify best practices for unpredictable traffic

   Auto Scaling adjusts servers automatically, ELB balances traffic, and fast SSD storage speeds data access. Use Auto Scaling with Elastic Load Balancer and fast SSD storage uses all these features, while others rely on manual or slow methods.

2. Final Answer:

   Use Auto Scaling with Elastic Load Balancer and fast SSD storage -> Option B

3. Quick Check:

   Auto Scaling + ELB + fast storage = best performance [OK]

Hint: Combine Auto Scaling, ELB, and fast storage for spikes [OK]

Common Mistakes:

• Choosing fixed or manual scaling
• Ignoring load balancing
• Using slow storage for performance