Study guide

1.6 GuardDuty, Inspector, Macie, and Security Hub

AWS Solutions Architect Associate SAA-C03

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About the AWS Solutions Architect Associate (SAA-C03) Exam Study Strategies and Exam Tips for SAA-C03 The AWS Well-Architected Framework

2 Domain 1: Design Secure Architectures (30%)

1.1 IAM Fundamentals — Users, Groups, Roles, and Policies 1.2 AWS Organizations, SCPs, and Multi-Account Strategy 1.3 VPC Security — Security Groups, NACLs, and VPC Endpoints 1.4 Encryption, KMS, and Secrets Management 1.5 AWS WAF, Shield, and Network Firewall 1.6 GuardDuty, Inspector, Macie, and Security Hub 1.7 The Shared Responsibility Model for Solutions Architects 1.8 Data Protection, Compliance, and Audit Services

3 Domain 2: Design Resilient Architectures (26%)

2.1 Elastic Load Balancing (ELB) — ALB, NLB, and GWLB 2.2 EC2 Auto Scaling — Dynamic, Predictive, and Scheduled 2.3 Multi-AZ and Multi-Region Architectures 2.4 Disaster Recovery Strategies — RTO and RPO 2.5 Decoupling with SQS, SNS, and EventBridge 2.6 AWS Step Functions and Workflow Orchestration

4 Domain 3: Design High-Performing Architectures (24%)

3.1 EC2 Instance Types, Purchasing Options, and Placement Groups 3.2 Lambda, Serverless Compute, and Container Services 3.3 Amazon S3 - Storage Classes, Lifecycle, and Performance 3.4 Block and File Storage - EBS, EFS, and FSx 3.5 Database Services - RDS, Aurora, DynamoDB, and More 3.6 CloudFront, Route 53, and Global Accelerator 3.7 Data Ingestion and Transformation - Kinesis, Glue, and EMR

5 Domain 4: Design Cost-Optimized Architectures (20%)

4.1 Compute Cost Optimization — Right-Sizing, RIs, Savings Plans, and Spot 4.2 Storage Cost Optimization — S3 Tiers, EBS, and Data Transfer 4.3 Database Cost Optimization 4.4 AWS Cost Management and Monitoring Tools

6 VPC and Networking Deep Dive

5.1 VPC Architecture — Subnets, Route Tables, and Gateways 5.2 VPC Connectivity — Peering, Transit Gateway, and Direct Connect 5.3 Amazon API Gateway 5.4 CloudFormation and Infrastructure as Code 5.5 AWS PrivateLink and Endpoint Services

7 Migration, Transfer, and Hybrid Services

6.1 The 7 Rs of Cloud Migration 6.2 AWS Snow Family — Snowball Edge Devices 6.3 CloudWatch, CloudTrail, and AWS Config 6.4 Amazon Cognito and Identity Federation 6.5 AWS DataSync and Transfer Family

8 Serverless Architecture and Application Services

7.1 Serverless Architecture Patterns 7.2 Advanced SQS Patterns — DLQ, Backpressure, and FIFO 7.3 Analytics Services — Athena, OpenSearch, and QuickSight 7.4 Container Orchestration — ECS, EKS, and ECR

9 Advanced Topics and Exam Scenarios

8.1 Advanced IAM — Permission Boundaries, Federation, and Cross-Account 8.2 Caching Strategies and ElastiCache Patterns 8.3 Hybrid Architecture — DNS, Storage, and Compute 8.4 SAA-C03 Scenario Practice — Putting It All Together

1.6 GuardDuty, Inspector, Macie, and Security Hub

Key Takeaways Explain This Topic AI

Amazon GuardDuty uses machine learning on CloudTrail, VPC Flow Logs, and DNS logs to detect threats with one-click, agentless enablement.

Amazon Inspector continuously scans EC2 instances, ECR container images, and Lambda functions for CVE vulnerabilities and network exposure.

Amazon Macie uses machine learning to discover and classify sensitive data such as PII and financial data in Amazon S3.

AWS Security Hub CSPM (listed as AWS Security Hub in the SAA-C03 exam guide) aggregates findings from GuardDuty, Inspector, Macie, and partners and runs control checks against standards like CIS and PCI DSS.

All four are detective controls — they find issues but do not remediate; pair them with EventBridge and Lambda for automated response.

Last updated: October 2026

Quick Answer: GuardDuty = ML threat detection from logs. Inspector = vulnerability (CVE) scanning of EC2, containers, and Lambda. Macie = sensitive-data discovery in S3. Security Hub = the aggregation dashboard. All are detective — they find problems but do not fix them; automate response with EventBridge + Lambda .

Amazon GuardDuty

GuardDuty continuously analyzes log telemetry with machine learning and threat-intelligence feeds. It is agentless and enabled with one click.

  • Data Source What It Analyzes
  • CloudTrail management events API calls (who/what/when)
  • CloudTrail S3 data events Object-level S3 access
  • VPC Flow Logs Network traffic patterns
  • DNS logs Suspicious domain lookups
  • EKS audit logs Kubernetes API activity
  • RDS login activity / Lambda network / Runtime Monitoring Brute force, anomalous egress, process activity

Typical findings: cryptocurrency mining , compromised credentials (API calls from unusual geographies), data exfiltration , port-scanning reconnaissance, and malware on instances. Findings carry a severity (Low/Medium/High) and stream to EventBridge for automated containment (for example, isolating an instance via a Lambda function).

Amazon Inspector

Amazon Inspector automatically and continuously scans workloads for software vulnerabilities and unintended network reachability — no manual scan trigger needed.

  • Feature Detail
  • Targets EC2 instances, ECR container images, Lambda functions
  • Finds Known CVEs , network-reachability exposure
  • Mechanism Uses the SSM Agent (preinstalled on most AMIs)
  • Scoring Inspector risk score prioritizes by exploitability and exposure
  • Routes to Security Hub, EventBridge, S3 export

On the Exam: "Scan EC2 or container images for known software vulnerabilities (CVEs)" → Inspector (not GuardDuty, which watches runtime/log behavior).

Amazon Macie

Amazon Macie discovers, classifies, and protects sensitive data in Amazon S3 using ML and managed data identifiers.

  • Feature Detail
  • Discovers PII (names, SSNs, card numbers), PHI, financial data, credentials
  • Scope S3 buckets, scheduled or on-demand jobs
  • Also flags Public buckets, unencrypted buckets, externally shared buckets
  • Routes to Security Hub, EventBridge

On the Exam: Any mention of personally identifiable information (PII) in S3 → Macie .

AWS Security Hub CSPM

AWS Security Hub CSPM (Cloud Security Posture Management; the SAA-C03 exam guide still lists it as AWS Security Hub) is the single pane of glass that ingests and normalizes findings into the AWS Security Finding Format (ASFF) and runs its own security-control checks.

  • Feature Detail
  • Aggregates GuardDuty, Inspector, Macie, IAM Access Analyzer, Firewall Manager, partners
  • Standards CIS AWS Foundations, PCI DSS , AWS Foundational Security Best Practices, NIST
  • Checks Continuous automated compliance scoring
  • Multi-account Org-wide aggregation via a delegated administrator
  • Routes to EventBridge for automated workflows
  • Scenario-to-Service Map
  • Scenario Keyword Service
  • Cryptomining / compromised credentials GuardDuty
  • Software CVEs on EC2 or container images Inspector
  • PII discovery in S3 Macie
  • Centralized findings + CIS/PCI scoring Security Hub
  • Automated remediation of a finding EventBridge + Lambda

Common Trap: None of these four services remediate automatically. If a question asks how to automatically respond to a finding, the answer pairs the detective service with EventBridge triggering Lambda or Systems Manager Automation .

Detective vs. Preventive vs. Responsive

The exam expects you to classify controls. Preventive controls stop bad actions before they happen — SCPs, security groups, NACLs, IAM policies, WAF rules. Detective controls find problems after the fact — GuardDuty, Inspector, Macie, Config, CloudTrail, Security Hub. Responsive automation closes the loop — EventBridge rules invoking Lambda or Systems Manager Automation runbooks. A complete answer to "continuously detect threats and automatically contain them" is therefore a detective service (GuardDuty) plus a responsive pipeline (EventBridge → Lambda), never a single service.

How the Services Compose

These tools are designed to stack, and questions often combine them. A reference pattern: GuardDuty detects a compromised instance, Inspector confirms which unpatched CVE was exploited, Macie assesses whether the affected S3 data contained PII, and Security Hub aggregates all three findings into one normalized view scored against the AWS Foundational Security Best Practices and CIS standards. Config runs alongside to record exactly how the resource was configured at the time of the incident.

Recognizing that Security Hub CSPM is the aggregator and posture checker — it runs control checks against standards but does not detect threats the way GuardDuty does — prevents the common error of picking Security Hub when the task is actually threat detection.

Multi-Account Operation

All four support delegated administrator and org-wide aggregation through AWS Organizations, so a central Security Tooling account can view findings from every member account. This is the recommended enterprise pattern: enable GuardDuty, Inspector, Macie, and Security Hub org-wide, designate one security account as the delegated administrator, and route consolidated findings to that account's Security Hub.

Service-to-Telemetry Quick Reference

  • Service Primary Telemetry One-Line Job
  • GuardDuty CloudTrail, VPC Flow, DNS, EKS, RDS logins Detect active threats
  • Inspector EC2/ECR/Lambda software inventory Find CVE vulnerabilities
  • Macie S3 object content Find sensitive data (PII)
  • Security Hub Findings from the above + partners Aggregate and score compliance

Exam framing: Match the keyword — "mining/credentials" → GuardDuty, "CVE/patch" → Inspector, "PII in S3" → Macie, "single dashboard/CIS score" → Security Hub — then add EventBridge + Lambda if auto-remediation is required.