📌 Table of Contents

1. What is AWS CloudWatch?

2. Why Do We Need CloudWatch?

3. Main Components of CloudWatch

4. CloudWatch Metrics

5. CloudWatch Logs and Log Groups

6. CloudWatch Alarms

7. What is Amazon SNS?

8. CloudWatch + SNS Architecture

9. Practical Project: EC2 CPU Alert

10. Step-by-Step Implementation

11. Testing the Alarm

12. Important CloudWatch Concepts

13. Default vs Custom Metrics

14. Common Use Cases

15. Best Practices

16. Interview Questions and Answers

17. Key Takeaways

1️⃣ What is AWS CloudWatch?

Amazon CloudWatch is a monitoring and observability service provided by AWS.

It helps us monitor:

• 🖥️ EC2 instances

• 📊 CPU utilization

• 💾 Memory and disk usage

• 📜 Application logs

• 🔄 AWS services

• 🚨 Infrastructure problems

• 📩 Alerts and notifications

In simple words:

CloudWatch helps us understand what is happening inside our AWS infrastructure.

For example, imagine you have an EC2 server running your application.

You may want to know:

• Is the server running?

• Is CPU usage too high?

• Is the application generating errors?

• Is disk space running out?

• Has the server stopped responding?

CloudWatch helps you monitor these things.

2️⃣ Why Do We Need CloudWatch?

Without monitoring, we may only discover a problem after users complain.

For example:

Application becomes slow
        ↓
Users face problems
        ↓
Users complain
        ↓
Team starts investigating

This is called reactive monitoring.

With CloudWatch:

Application
     ↓
CloudWatch monitors metrics
     ↓
Threshold is crossed
     ↓
CloudWatch Alarm
     ↓
SNS Notification
     ↓
DevOps Team receives alert

This allows the team to identify problems quickly.

3️⃣ Main Components of AWS CloudWatch

The major components are:

The most important concepts for beginners are:

Metrics → Monitoring Data

Logs → Application/System Records

Alarms → Alert when something goes wrong

SNS → Send notifications

4️⃣ What Are CloudWatch Metrics? 📊

A metric is a numerical measurement that represents the performance or behavior of a resource.

For example:

CPU Utilization = 75%

Network In = 100 MB

Disk Usage = 80%

Number of Requests = 5,000

AWS automatically provides many default metrics for its services.

For an EC2 instance, some common metrics are:

• CPUUtilization

• NetworkIn

• NetworkOut

• DiskReadOps

• DiskWriteOps

• StatusCheckFailed

Example:

CPU Utilization

10:00 → 20%
10:05 → 35%
10:10 → 70%
10:15 → 90%

If CPU reaches a dangerous level, CloudWatch can trigger an alarm.

5️⃣ CloudWatch Logs 📜

Logs contain information about events happening inside applications and systems.

For example:

Application started

User login successful

Database connection failed

API request received

Application error occurred

CloudWatch Logs allows us to collect and store these logs in AWS.

A common structure is:

CloudWatch Logs
      │
      └── Log Group
              │
              ├── Log Stream
              ├── Log Stream
              └── Log Stream

What is a Log Group?

A Log Group is a collection of related logs.

Example:

/aws/codebuild/my-project

This log group may contain logs generated by a CodeBuild project.

Another example:

/application/backend

Inside the Log Group, multiple Log Streams can exist.

6️⃣ What Are CloudWatch Alarms? 🚨

A CloudWatch Alarm watches a metric and performs an action when a condition is met.

For example:

IF CPU Utilization > 80%
FOR 5 minutes

THEN

Send Email Alert

The flow looks like:

EC2 Instance
     ↓
CPU Metric
     ↓
CloudWatch
     ↓
CloudWatch Alarm
     ↓
Amazon SNS
     ↓
📧 Email Notification

7️⃣ What is Amazon SNS? 🔔

Amazon Simple Notification Service (SNS) is a messaging and notification service.

SNS can send notifications through:

• 📧 Email

• 📱 SMS

• 🔗 HTTP/HTTPS endpoints

• 📲 Mobile notifications

• AWS Lambda

• Other AWS services

In this project, SNS will send an email notification when CPU usage crosses the configured threshold.

8️⃣ CloudWatch + SNS Architecture

The architecture for this project is simple:

                ┌─────────────────┐
                │   EC2 Instance  │
                │                 │
                │  CPU Usage      │
                └────────┬────────┘
                         │
                         ▼
                ┌─────────────────┐
                │   CloudWatch    │
                │                 │
                │    Metrics      │
                └────────┬────────┘
                         │
              CPU > Threshold
                         │
                         ▼
                ┌─────────────────┐
                │ CloudWatch Alarm│
                └────────┬────────┘
                         │
                         ▼
                ┌─────────────────┐
                │    Amazon SNS   │
                └────────┬────────┘
                         │
                         ▼
                   📧 Email Alert

9️⃣ Practical Project 🚀

Project: Monitor EC2 CPU Utilization and Send Email Alerts

In this project, we will:

1. Launch an EC2 instance.

2. Monitor its CPU utilization.

3. Create an SNS Topic.

4. Subscribe an email address.

5. Create a CloudWatch Alarm.

6. Set a CPU threshold.

7. Generate CPU load.

8. Trigger the alarm.

9. Receive an email notification.

🔟 Prerequisites

Before starting, you need:

• An AWS Account

• Basic knowledge of EC2

• An EC2 instance

• Permission to access CloudWatch and SNS

• An active email address

Step 1️⃣ Launch an EC2 Instance 🖥️

Go to:

AWS Console
→ EC2
→ Launch Instance

For learning purposes, you can select:

AMI: Ubuntu

Instance Type:
t2.micro / t3.micro

Configure the required settings and launch the instance.

After launching:

EC2 Dashboard
        ↓
Instances
        ↓
Select your instance

Make sure the instance state is:

Running

Step 2️⃣ Check EC2 Metrics in CloudWatch 📊

Go to:

AWS Console
→ CloudWatch
→ Metrics

Then navigate to:

AWS Namespaces
→ EC2
→ Per-Instance Metrics

Select your EC2 instance.

You should see metrics such as:

CPUUtilization

NetworkIn

NetworkOut

DiskReadOps

DiskWriteOps

Select:

CPUUtilization

You will now see a graph showing the CPU usage of your EC2 instance.

Step 3️⃣ Create an SNS Topic 🔔

Go to:

AWS Console
→ Amazon SNS
→ Topics
→ Create Topic

Choose:

Type: Standard

Example:

Name:

EC2-CPU-Alert

Then click:

Create Topic

Step 4️⃣ Create an SNS Subscription 📧

After creating the topic:

SNS Topic
→ Create Subscription

Select:

Protocol:

Email

Enter your email address.

For example:

your-email@example.com

Click:

Create Subscription

AWS will send a confirmation email.

Open the email and click:

Confirm Subscription

Your subscription should now show:

Status: Confirmed

⚠️ Important: If you do not confirm the subscription, SNS will not send notifications to your email.

Step 5️⃣ Create a CloudWatch Alarm 🚨

Go to:

CloudWatch
→ Alarms
→ Create Alarm

Click:

Select Metric

Navigate to:

EC2
→ Per-Instance Metrics
→ CPUUtilization

Select your EC2 instance.

Step 6️⃣ Configure the Alarm Condition

For example:

Threshold Type:

Static

Set the condition:

CPUUtilization > 70%

You can configure:

Whenever CPUUtilization is...

Greater than 70

Example:

CPU Usage: 20%  → OK

CPU Usage: 50%  → OK

CPU Usage: 75%  → ALARM 🚨

Step 7️⃣ Configure the Alarm Action

When the alarm enters the ALARM state, select:

Send notification to:

EC2-CPU-Alert

This connects:

CloudWatch Alarm
        ↓
SNS Topic
        ↓
Email

Step 8️⃣ Name the Alarm

Example:

Alarm Name:

High-EC2-CPU-Utilization

You can also add a description:

This alarm monitors EC2 CPU utilization and sends an SNS notification when CPU usage exceeds 70%.

Click:

Create Alarm

Initially, the alarm state may show:

Insufficient Data

After CloudWatch receives enough metric data, it will change to:

OK

1️⃣1️⃣ How to Test the CloudWatch Alarm 🧪

Now we need to increase the CPU usage of the EC2 instance.

First, connect to your EC2 instance:

ssh -i key.pem ubuntu@<EC2-PUBLIC-IP>

Install a CPU stress tool:

sudo apt update

sudo apt install stress -y

Generate CPU load:

stress --cpu 2 --timeout 300

This command will:

Generate CPU Load
        ↓
Increase CPU Utilization
        ↓
CloudWatch detects metric change
        ↓
Threshold crossed
        ↓
Alarm changes to ALARM
        ↓
SNS sends Email 🚨

After the configured evaluation period, you should receive an email notification.

Example:

Subject:

ALARM: High-EC2-CPU-Utilization

Congratulations! 🎉

You have successfully created an automated AWS monitoring and alerting system.

1️⃣2️⃣ Understanding CloudWatch Alarm States

CloudWatch alarms generally have three states.

🟢 OK

Everything is working normally.

Example:

CPU = 25%

🔴 ALARM

The configured threshold has been crossed.

Example:

CPU > 70%

The configured action is triggered.

🟡 INSUFFICIENT_DATA

CloudWatch does not have enough data to determine the alarm state.

This may happen when:

• The instance was recently launched.

• Metrics are not available yet.

• The monitoring configuration changed.

1️⃣3️⃣ Default Metrics vs Custom Metrics

Default Metrics

AWS automatically provides metrics for many AWS services.

Examples:

EC2 CPU Utilization

Network In

Network Out

You do not need to manually configure these basic metrics.

Custom Metrics

Sometimes AWS does not provide the exact metric you need.

For example:

Application Response Time

Custom Business Metrics

Number of Active Users

Memory Usage

Disk Usage

In such cases, you can send custom data to CloudWatch.

Example architecture:

Application
      ↓
CloudWatch Agent
      ↓
CloudWatch Custom Metric
      ↓
CloudWatch Alarm
      ↓
SNS Notification

1️⃣4️⃣ Important EC2 Metrics

Here are some useful EC2 metrics:

1️⃣5️⃣ CloudWatch Logs Example

Suppose your application generates logs like:

INFO: Application Started

INFO: Database Connected

ERROR: Database Connection Failed

ERROR: API Request Failed

Instead of manually logging into the server and checking:

/var/log/

You can send these logs to:

Amazon CloudWatch Logs

This allows centralized monitoring.

1️⃣6️⃣ Real-World DevOps Monitoring Architecture

In a production environment, monitoring may look like:

                    Application
                         │
          ┌──────────────┼──────────────┐
          │              │              │
          ▼              ▼              ▼
       Metrics          Logs          Events
          │              │              │
          └──────────────┼──────────────┘
                         ▼
                    CloudWatch
                         │
              ┌──────────┴──────────┐
              ▼                     ▼
           Alarms               Dashboards
              │
              ▼
             SNS
              │
        ┌─────┴─────┐
        ▼           ▼
      Email       Slack

1️⃣7️⃣ Common Use Cases of CloudWatch

CloudWatch can be used for:

🖥️ EC2 Monitoring

Monitor:

CPU

Memory

Disk

Network

📜 Application Logs

Monitor:

Errors

Warnings

Application Events

🚨 Automated Alerts

Send alerts when:

CPU is too high

Disk is almost full

Application is failing

EC2 instance is unhealthy

📊 Dashboards

Create dashboards to visualize:

Infrastructure Health

Application Performance

Resource Utilization

Errors

1️⃣8️⃣ Best Practices 💡

1. Avoid Monitoring Everything

Focus on important metrics.

For example:

CPU

Memory

Disk

Application Errors

Latency

2. Use Meaningful Alarm Names

Bad:

Alarm-123

Good:

Production-EC2-High-CPU

3. Configure Proper Thresholds

Avoid setting unrealistic values.

For example:

CPU > 10%

This may generate unnecessary alerts.

Instead:

CPU > 80%
for 5 minutes

4. Avoid Alert Fatigue

Too many alerts can cause teams to ignore notifications.

Configure alarms only for meaningful issues.

5. Use Multiple Monitoring Layers

A production application should monitor:

Infrastructure

Application

Database

Network

Security

🎯 Important Interview Questions and Answers

Q1. What is AWS CloudWatch?

Answer:

AWS CloudWatch is a monitoring and observability service that helps monitor AWS resources, applications, metrics, logs, and events. It can also create alarms and trigger automated actions or notifications.

Q2. What is a CloudWatch Metric?

Answer:

A metric is a numerical measurement that represents the performance or behavior of an AWS resource.

Examples include:

CPUUtilization

NetworkIn

NetworkOut

Q3. What is a CloudWatch Alarm?

Answer:

A CloudWatch Alarm monitors a metric and performs an action when the metric crosses a configured threshold.

For example:

CPU > 80%
        ↓
CloudWatch Alarm
        ↓
SNS Notification

Q4. What is a Log Group?

Answer:

A Log Group is a collection of logs from related applications or AWS resources.

For example:

/aws/codebuild/project-name

Multiple log streams can exist inside a Log Group.

Q5. What is the difference between Metrics and Logs?

Q6. What are the states of a CloudWatch Alarm?

There are three main states:

OK

ALARM

INSUFFICIENT_DATA

Q7. What is Amazon SNS?

Answer:

Amazon Simple Notification Service (SNS) is a messaging service that sends notifications to subscribers using protocols such as email, SMS, HTTP/HTTPS, and AWS services.

Q8. How can CloudWatch send an email alert?

The process is:

CloudWatch Metric
        ↓
CloudWatch Alarm
        ↓
SNS Topic
        ↓
Email Subscription
        ↓
Email Alert

Q9. What is the difference between Default and Custom Metrics?

Default Metrics:

Automatically provided by AWS.

Example:

EC2 CPU Utilization

Custom Metrics:

Metrics manually sent to CloudWatch.

Example:

Application Response Time

Q10. Can CloudWatch monitor memory and disk usage on EC2?

Answer:

These are not typically available as standard EC2 host metrics in the same way as CPU utilization. To collect detailed memory and disk metrics, you generally configure the CloudWatch Agent on the EC2 instance.

🏁 Project Summary

In this project, we created a complete monitoring and alerting system.

Architecture:

EC2 Instance
      │
      ▼
CloudWatch Metrics
      │
      ▼
CloudWatch Alarm
      │
      ▼
Amazon SNS
      │
      ▼
📧 Email Notification

What We Learned

✅ What AWS CloudWatch is
✅ Why monitoring is important
✅ CloudWatch Metrics
✅ CloudWatch Logs
✅ Log Groups and Log Streams
✅ CloudWatch Alarms
✅ Amazon SNS
✅ EC2 CPU Monitoring
✅ Creating CPU Threshold Alerts
✅ Sending Email Notifications
✅ Default vs Custom Metrics
✅ CloudWatch Best Practices
✅ Real-world monitoring concepts

🎉 Conclusion

AWS CloudWatch is one of the most important services for monitoring AWS infrastructure.

As a DevOps Engineer, deploying an application is only one part of the job. You also need to know whether the application and infrastructure are healthy.

CloudWatch helps answer questions such as:

Is my server healthy? 🖥️

Is CPU usage too high? 📈

Is my application generating errors? ❌

Is disk space running out? 💾

Should the DevOps team be alerted? 🚨

By combining CloudWatch + CloudWatch Alarms + Amazon SNS, we can build an automated monitoring and alerting system that helps teams detect issues quickly.

Build it → Monitor it → Detect problems → Alert the team → Improve reliability. 🚀

This project is a great beginner step toward understanding AWS Monitoring, Observability, and Production Infrastructure.

🚀 Complete Learning & Career Resources | 2027–2028

A curated collection of learning resources for AI, Data Analytics, Python, Data Engineering, Cybersecurity, Cloud, Networking, Finance, Digital Marketing, Project Management, DevOps and Generative AI.

📚 Learn  →  🧪 Practice  →  🛠️ Build  →  🐙 Share  →  🚀 Grow

🌟 About This Repository

Welcome to the Complete Learning & Career Resources Repository! 🚀

This repository is designed as a centralized learning hub for students, developers, QA engineers, DevOps engineers, cloud learners, cybersecurity enthusiasts, data professionals, project managers, business professionals and anyone interested in continuous learning.

The goal is simple:

Learn → Practice → Build → Document → Share → Grow

Instead of searching for useful resources again and again, this repository brings them together in one place.

🎯 What You Will Find Here

• 🤖 Artificial Intelligence

• 🧠 Generative AI

• 📊 Data Analytics

• 🐍 Python

• ⚙️ Data Engineering

• ☁️ Cloud Computing

• 🌐 Computer Networking

• 🔐 Cybersecurity

• ⚙️ DevOps

• 📋 Project Management

• 💰 Finance

• 📈 Digital Marketing

• 🧩 Business Analysis

• 🚀 Career Development

• 🎓 Professional Learning

• 🛠️ Project Ideas

• 📚 Learning Roadmaps

📊 Repository Overview

📚 Table of Contents

• 🌟 About This Repository

• 🎯 What You Will Find Here

• 📊 Repository Overview

• 🤖 AI Courses

• 🔵 Google Courses

• 🟣 IBM Courses

• 🔥 Best Courses 2027–2028

• 🌟 Learning & Career Resources

• 🗺️ Recommended Learning Roadmaps

• 📊 Data Analytics Roadmap

• 🐍 Python Roadmap

• ☁️ Cloud & DevOps Roadmap

• 🔐 Cybersecurity Roadmap

• 🤖 AI Roadmap

• 🧪 How to Learn Effectively

• 🛠️ Project Ideas

• 📂 Recommended GitHub Project Structure

• 📈 Career Roadmap

• 💡 Learning Checklist

• 🧠 Golden Rules

• 📖 My Resources

• 🌐 Useful Links

• ⭐ Support This Repository

• 🔄 Future Updates

• ⚠️ Affiliate Disclosure

🤖 AI Courses

🚀 Explore AI fundamentals, Python, AI infrastructure, Generative AI, AI governance and specialized AI applications.

🔵 Google Courses

🌐 Explore Data Analytics, AI, Cybersecurity, Networking, Cloud, Digital Marketing and Project Management.

🟣 IBM Courses

💙 Explore SQL, Python, Data Analytics, Deep Learning, RAG and Generative AI resources.

🔥 Best Courses 2027–2028

🎯 A broader collection covering AI, Data, Python, Finance, Cybersecurity, Marketing, Networking, Management and Data Engineering.

🌟 Learning & Career Resources

💡 Additional resources for learning, career development, language learning, hosting, education and professional growth.

🗺️ Recommended Learning Roadmaps

Choose one roadmap according to your career goal. You don't need to learn everything at once.

🤖 AI Roadmap

AI Fundamentals
      ↓
Python Basics
      ↓
Mathematics & Statistics
      ↓
Data Fundamentals
      ↓
Machine Learning
      ↓
Deep Learning
      ↓
Generative AI
      ↓
Prompt Engineering
      ↓
RAG
      ↓
Vector Databases
      ↓
Agentic AI
      ↓
AI Applications
      ↓
Real-World Projects
      ↓
GitHub Portfolio