Operational excellence pillar in AWS - Mini Project: Build & Apply

Implementing AWS Operational Excellence Pillar Basics

📖 Scenario: You are working as a cloud engineer for a small company that wants to improve its AWS environment's operational excellence. Your task is to create a simple AWS CloudFormation template that sets up basic monitoring and alerting to help the company detect and respond to issues quickly.

🎯 Goal: Build a CloudFormation template that defines a CloudWatch Alarm monitoring CPU utilization of an EC2 instance and a SNS Topic for alert notifications. This setup helps the company follow the AWS Operational Excellence pillar by improving monitoring and incident response.

📋 What You'll Learn

Create a CloudFormation template with an EC2 instance resource.

Add a CloudWatch Alarm that triggers when CPU utilization exceeds 70%.

Create an SNS Topic for alarm notifications.

Subscribe an email endpoint to the SNS Topic.

💡 Why This Matters

🌍 Real World

Monitoring and alerting are essential for running reliable cloud applications. This project shows how to set up basic monitoring and notifications in AWS to detect and respond to issues quickly.

💼 Career

Cloud engineers and DevOps professionals use CloudFormation templates to automate infrastructure setup. Understanding how to implement monitoring and alerting aligns with operational excellence best practices required in many cloud roles.

1

Create the EC2 Instance Resource

Create a CloudFormation template with a resource named MyEC2Instance of type AWS::EC2::Instance. Set the ImageId property to ami-0abcdef1234567890 and InstanceType to t2.micro.

AWS

# Define the EC2 instance resource
# Your code here

Hint

Use the Resources section to define the EC2 instance with the exact name and properties.

2

Add SNS Topic for Notifications

Add a resource named AlarmNotificationTopic of type AWS::SNS::Topic to the CloudFormation template.

AWS

Resources:
  MyEC2Instance:
    Type: AWS::EC2::Instance
    Properties:
      ImageId: ami-0abcdef1234567890
      InstanceType: t2.micro

# Add SNS Topic resource below
# Your code here

Hint

Define the SNS Topic resource under Resources with the exact name AlarmNotificationTopic.

3

Create CloudWatch Alarm for CPU Utilization

Add a resource named HighCPUAlarm of type AWS::CloudWatch::Alarm. Configure it to monitor the CPUUtilization metric of the EC2 instance MyEC2Instance. Set the alarm to trigger when CPU utilization is greater than 70% for 5 minutes (evaluation periods 1, period 300 seconds). Set the AlarmActions to notify the AlarmNotificationTopic.

AWS

Resources:
  MyEC2Instance:
    Type: AWS::EC2::Instance
    Properties:
      ImageId: ami-0abcdef1234567890
      InstanceType: t2.micro
  AlarmNotificationTopic:
    Type: AWS::SNS::Topic

# Add CloudWatch Alarm resource below
# Your code here

Hint

Use Dimensions with InstanceId set to !Ref MyEC2Instance to link the alarm to the EC2 instance.

4

Subscribe Email Endpoint to SNS Topic

Add a resource named EmailSubscription of type AWS::SNS::Subscription. Set the Protocol to email, the Endpoint to [e-mail], and the TopicArn to reference AlarmNotificationTopic.

AWS

Resources:
  MyEC2Instance:
    Type: AWS::EC2::Instance
    Properties:
      ImageId: ami-0abcdef1234567890
      InstanceType: t2.micro
  AlarmNotificationTopic:
    Type: AWS::SNS::Topic
  HighCPUAlarm:
    Type: AWS::CloudWatch::Alarm
    Properties:
      AlarmDescription: "Alarm when CPU exceeds 70%"
      Namespace: AWS/EC2
      MetricName: CPUUtilization
      Dimensions:
        - Name: InstanceId
          Value: !Ref MyEC2Instance
      Statistic: Average
      Period: 300
      EvaluationPeriods: 1
      Threshold: 70
      ComparisonOperator: GreaterThanThreshold
      AlarmActions:
        - !Ref AlarmNotificationTopic

# Add SNS Subscription resource below
# Your code here

Hint

Use the AWS::SNS::Subscription resource type with the exact properties to subscribe the email.

Practice

1. What is the main goal of the Operational Excellence pillar in AWS Well-Architected Framework?

easy

A. To optimize costs and reduce spending

B. To secure data and control access to resources

C. To improve and automate processes for better system reliability and efficiency

D. To design systems for high availability and fault tolerance

Solution

1. Step 1: Understand the focus of Operational Excellence

   Operational Excellence focuses on running and monitoring systems to deliver business value and continually improve processes.

2. Step 2: Differentiate from other pillars

   Security focuses on protection, Cost Optimization on spending, Reliability on availability. Operational Excellence is about process improvement and automation.

3. Final Answer:

   To improve and automate processes for better system reliability and efficiency -> Option C

4. Quick Check:

   Operational Excellence = process improvement and automation [OK]

Hint: Operational Excellence = improve processes + automation [OK]

Common Mistakes:

• Confusing Operational Excellence with Security or Cost Optimization
• Thinking it only covers system uptime
• Ignoring the importance of continuous improvement

2. Which AWS service is primarily used to automate operational tasks and workflows?

easy

A. AWS Systems Manager

B. Amazon S3

C. Amazon RDS

D. AWS CloudTrail

Solution

1. Step 1: Identify services for automation

   AWS Systems Manager provides automation for operational tasks like patching, configuration, and runbook execution.

2. Step 2: Exclude unrelated services

   Amazon S3 is storage, Amazon RDS is database, CloudTrail is for logging API calls, not automation.

3. Final Answer:

   AWS Systems Manager -> Option A

4. Quick Check:

   Automation service = AWS Systems Manager [OK]

Hint: Automation in AWS? Think Systems Manager [OK]

Common Mistakes:

• Choosing storage or database services for automation
• Confusing logging services with automation
• Not knowing AWS Systems Manager capabilities

3. Consider this AWS CloudWatch alarm configuration snippet:

{
  "AlarmName": "HighCPU",
  "MetricName": "CPUUtilization",
  "Namespace": "AWS/EC2",
  "Statistic": "Average",
  "Period": 300,
  "EvaluationPeriods": 2,
  "Threshold": 80,
  "ComparisonOperator": "GreaterThanThreshold"
}

What happens when the average CPU utilization exceeds 80% for 10 minutes?

medium

A. The alarm triggers after two consecutive 5-minute periods above 80%

B. The alarm triggers immediately when CPU exceeds 80%

C. The alarm never triggers because threshold is too high

D. The alarm triggers only if CPU stays above 80% for 30 minutes

Solution

1. Step 1: Understand EvaluationPeriods and Period

   The alarm evaluates CPU utilization every 5 minutes (Period=300 seconds) and requires 2 consecutive periods above threshold.

2. Step 2: Calculate total time to trigger

   2 periods x 5 minutes = 10 minutes of CPU > 80% triggers the alarm.

3. Final Answer:

   The alarm triggers after two consecutive 5-minute periods above 80% -> Option A

4. Quick Check:

   EvaluationPeriods x Period = trigger time [OK]

Hint: Alarm triggers after EvaluationPeriods x Period time above threshold [OK]

Common Mistakes:

• Thinking alarm triggers immediately on threshold breach
• Ignoring EvaluationPeriods count
• Misunderstanding Period as total time

4. You have an AWS Lambda function that fails intermittently. Which step helps you debug and improve operational excellence?

medium

A. Remove error handling code to simplify the function

B. Enable detailed CloudWatch Logs and set up alarms on error metrics

C. Manually restart the Lambda function every hour

D. Disable all logging to improve performance

Solution

1. Step 1: Use monitoring to detect issues

   Enabling detailed logs and alarms helps identify failure causes and patterns.

2. Step 2: Avoid harmful practices

   Disabling logs hides problems, manual restarts are inefficient, removing error handling worsens reliability.

3. Final Answer:

   Enable detailed CloudWatch Logs and set up alarms on error metrics -> Option B

4. Quick Check:

   Monitoring + alarms = better debugging [OK]

Hint: Use logs and alarms to find and fix errors [OK]

Common Mistakes:

• Turning off logs to 'speed up' functions
• Ignoring automated monitoring tools
• Relying on manual fixes instead of automation

5. A company wants to improve operational excellence by automating incident response for their EC2 fleet. Which combination of AWS services best achieves this?

hard

A. Amazon RDS + Amazon DynamoDB + AWS Elastic Beanstalk

B. Amazon S3 + AWS Glue + Amazon Athena

C. AWS IAM + AWS KMS + AWS Shield

D. AWS Systems Manager Automation + Amazon CloudWatch Events + AWS Lambda

Solution

1. Step 1: Identify services for automation and event-driven response

   AWS Systems Manager Automation runs operational tasks, CloudWatch Events detect incidents, Lambda executes custom code.

2. Step 2: Exclude unrelated services

   S3, Glue, Athena are for data analytics; IAM, KMS, Shield focus on security; RDS, DynamoDB, Elastic Beanstalk are for databases and app deployment.

3. Final Answer:

   AWS Systems Manager Automation + Amazon CloudWatch Events + AWS Lambda -> Option D

4. Quick Check:

   Automation + event detection + code execution = incident response [OK]

Hint: Combine automation, events, and Lambda for incident response [OK]

Common Mistakes:

• Choosing unrelated data or security services
• Not combining event detection with automation
• Ignoring Lambda's role in custom logic