Q: You want to get an alert when your EC2 instance CPU exceeds 80% for more than 5 minutes. How do you set this up?
1. In CloudWatch, create an Alarm:
Want to master this scenario in a live sandbox? Stephane Maarek's AWS Certified DevOps Engineer Professional Masterclass on Udemy covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "AWS reliability requires differentiating between AWS control plane limits and host-level resource exhaustion. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."
Initial Diagnostics & Root Cause Analysis
Or do it all via CLI:
- In CloudWatch, create an Alarm:
- Metric:
EC2 → Per-Instance Metrics → CPUUtilization - Statistic: Average
- Period: 5 minutes (300 seconds)
- Condition:
> 80
Remediation & Permanent Safeguards
aws cloudwatch put-metric-alarm \
--alarm-name HighCPU \
--metric-name CPUUtilization \
--namespace AWS/EC2 \
--statistic Average \
--period 300 \
--threshold 80 \
--comparison-operator GreaterThanThreshold \
--evaluation-periods 1 \
--alarm-actions arn:aws:sns:...
- Evaluation periods: 1 (alarm triggers after 1 period = 5 minutes above threshold)
- Add an SNS action — send notification to an SNS topic.
- Subscribe your email or PagerDuty endpoint to the SNS topic.
- In CloudWatch, create an Alarm:
- Metric: EC2 → Per-Instance Metrics → CPUUtilization
- Statistic: Average
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Purging compromised IAM user credentials immediately prior to querying CloudTrail forensic event logs when configuring want alert instance Deactivating a compromised key prevents abuse while preserving identity records for CloudTrail forensic queries to assess blast radius.
- Conflating local IAM Permissions Boundaries with organizational Service Control Policies (SCPs) when configuring want alert instance SCPs define maximum permission guards at the AWS Organization level across accounts, whereas permission boundaries limit delegate privileges within a single account.
- Deploying single-AZ cloud infrastructure for production workloads without multi-AZ failover resilience when configuring want alert instance Availability Zone hardware failures or localized network partitions cause complete service downtime when resources are not distributed across >=2 AZs.
- Jumping straight to SSH or instance restarts without reviewing CloudWatch metrics and AWS Systems Manager logs when configuring want alert instance Senior SREs triage control plane and hypervisor metrics via CloudWatch and SSM Session Manager before executing invasive host-level actions.