AWS Service Health and Operational Monitoring

This guide covers the critical services used to monitor, maintain, and respond to the health of AWS resources and global infrastructure, as required for the AWS Certified DevOps Engineer Professional exam.

Learning Objectives

By the end of this study guide, you will be able to:

• Differentiate between the AWS Service Health Dashboard and the Personal Health Dashboard.
• Configure CloudWatch Alarms and Metric Filters for automated incident response.
• Utilize Systems Manager OpsCenter to aggregate and manage operational issues (OpsItems).
• Design event-driven workflows to remediate health-related events using Amazon EventBridge and AWS Lambda.

Key Terms & Glossary

• SLA (Service Level Agreement): A commitment between a service provider and a client regarding service availability. Example: Amazon S3 Standard offers 99.9% availability over a monthly billing cycle.
• OpsItem: An operational work item in Systems Manager OpsCenter that provides a central location for investigating and resolving issues. Example: A failing EC2 health check automatically creating an entry in OpsCenter.
• Metric Filter: A CloudWatch feature that searches and transforms log data into numerical metrics. Example: Creating a metric that counts the occurrences of the string "404" in your web server logs.
• RTO (Recovery Time Objective): The maximum acceptable delay between the interruption of service and restoration of service.
• RPO (Recovery Point Objective): The maximum acceptable amount of data loss measured in time.

The "Big Idea"

In a complex cloud environment, health is not binary (up or down). It is a spectrum of performance, availability, and security. The "Big Idea" here is moving from Reactive Monitoring (waiting for a user to report an error) to Proactive Observability (using AWS Health APIs and CloudWatch Anomaly Detection) and Automated Remediation (using EventBridge to trigger Lambda functions that fix the state without human intervention).

Formula / Concept Box

Hierarchical Outline

1. AWS Health Services
   • Service Health Dashboard: Public, global view of all AWS service statuses across all regions.
   • AWS Health Dashboard (Personal): Account-specific view; alerts on scheduled maintenance, service EOL, or resource-specific failures.
   • AWS Health API: Programmatic access to health events for custom integration.
2. Amazon CloudWatch
   • Metrics & Dashboards: Collecting data from namespaces (EC2, RDS, Custom).
   • Alarms: Triggering SNS notifications or EC2 Auto Scaling actions.
   • Synthetics (Canaries): Monitoring endpoints and APIs by simulating user behavior.
3. AWS Systems Manager OpsCenter
   • OpsItems: Contextualizing incidents with related AWS resources, runbooks, and logs.
   • Automation Documents: Executing remediation scripts (e.g., restarting an instance).
4. AWS Config
   • Rules & Remediation: Continuous auditing of resource configurations against desired states.

Visual Anchors

Event-Driven Health Response Flow

CloudWatch Alarm State Machine

Definition-Example Pairs

• CloudWatch Synthetic Canary: A script that monitors endpoints 24/7.
  • Example: A NodeJS script that pings your login API every 5 minutes and alerts if the response time exceeds 2 seconds.
• Metric Filter: A pattern-matching tool for log files.
  • Example: Filtering CloudWatch Logs for the word "CRITICAL" and creating a metric that counts these occurrences to trigger an alarm.
• AWS Config Managed Rule: Predefined configuration checks.
  • Example: A rule that checks if all EBS volumes are encrypted; if not, it triggers an SSM Automation to delete or encrypt them.

Worked Examples

Scenario: Automating Response to a Scheduled Maintenance Event

Goal: Ensure that when AWS schedules a maintenance reboot for an EC2 instance, the DevOps team is notified and the instance is drained from the ALB.

1. Detection: AWS Health sends a AWS_EC2_INSTANCE_SCHEDULED_REBOOT event.
2. Event Routing: Create an Amazon EventBridge Rule with the event pattern:
   jsonCopy

   { "source": ["aws.health"], "detail-type": ["AWS Health Event"], "detail": { "service": ["EC2"], "eventTypeCode": ["AWS_EC2_INSTANCE_SCHEDULED_REBOOT"] } }
3. Target 1 (Notification): Set an SNS Topic as a target to email the team.
4. Target 2 (Remediation): Set a Lambda Function to put the instance into Standby in its Auto Scaling Group, ensuring the ALB stops sending traffic.

Checkpoint Questions

1. Which service provides a public view of the status of all AWS services in all regions?
2. What AWS Support plans are required to use the AWS Health API?
3. True/False: Systems Manager OpsCenter can automatically group related OpsItems using AI/ML.
4. How can you transform an error message in a text log file into a numerical graph in CloudWatch?

▶Click to view answers

1. AWS Service Health Dashboard.
2. Business or Enterprise.
3. True (using the 'deduplication' and 'related items' features).
4. By using a CloudWatch Logs Metric Filter.

Muddy Points & Cross-Refs

• Service Health vs. Personal Health: Think of Service Health as the "Weather Channel" (General status) and Personal Health as "Your Home's Security System" (Account-specific).
• CloudWatch Alarms vs. EventBridge: Alarms are based on thresholds (numbers over time). EventBridge is based on events (state changes/API calls).
• Cross-Ref: For deeper remediation logic, refer to AWS Systems Manager Automation Documents and Step Functions.

Comparison Tables

[!IMPORTANT] For the DOP-C02 exam, focus on Event-Driven Architectures. If an exam question asks how to respond to a service outage or maintenance event, the answer almost always involves AWS Health + EventBridge.