Album69
  • About
  • Life
  • Travel
  • Tech
  • Galleries
  • SAP-C02 Notes
  • DOP-C02 Notes
X GitHub LinkedIn YouTube

AWS CloudTrail

AWS CloudTrail is a service that enables governance, compliance, operational auditing, and risk auditing of your AWS account by logging, continuously…

Domain 4: Monitoring and Logging
October 4, 2026

1. Overview

AWS CloudTrail is a service that enables governance, compliance, operational auditing, and risk auditing of your AWS account by logging, continuously monitoring, and retaining account activity related to actions across your AWS infrastructure.

Key Characteristics

  • Audit logging - Records API calls and account activity
  • Compliance - Meets regulatory and compliance requirements
  • Security analysis - Detect unusual activity patterns
  • Operational troubleshooting - Debug issues with API calls
  • Multi-region - Can log activity across all regions
  • Real-time - Near real-time event delivery
  • Integrated - Works with CloudWatch, S3, EventBridge

What Problem Does It Solve?

  • Provides visibility into user and resource activity
  • Enables security analysis and compliance reporting
  • Helps with operational troubleshooting
  • Tracks changes to AWS resources
  • Enables forensic analysis after security incidents
  • Supports compliance audits and governance

2. Core Concepts

Trail

  • Configuration that enables logging of AWS API calls
  • Defines where logs are stored (S3 bucket)
  • Can be single-region or multi-region
  • Can include global services (IAM, CloudFront, Route 53)

Event

  • Record of an activity in AWS account
  • Contains details about API call, user, time, source IP
  • Types: Management events, Data events, Insight events
  • JSON format with standardized fields

Management Events

  • Control plane operations (create, delete, modify resources)
  • Enabled by default in trails
  • Examples: CreateInstance, DeleteBucket, PutBucketPolicy
  • Read events vs Write events

Data Events

  • Data plane operations (object-level operations)
  • Not enabled by default (additional cost)
  • Examples: GetObject, PutObject, DeleteObject
  • High volume events

Insight Events

  • Identify unusual activity patterns
  • Machine learning-based analysis
  • Detect spikes in API call volume
  • Additional cost feature

Event History

  • 90-day searchable history
  • Available by default (no trail needed)
  • Management events only
  • Free of charge

3. Trail Configuration

Basic Trail Configuration

{
  "TrailName": "MyTrail",
  "S3BucketName": "my-cloudtrail-bucket",
  "S3KeyPrefix": "cloudtrail-logs/",
  "IncludeGlobalServiceEvents": true,
  "IsMultiRegionTrail": true,
  "EnableLogFileValidation": true,
  "EventSelectors": [
    {
      "ReadWriteType": "All",
      "IncludeManagementEvents": true,
      "DataResources": [
        {
          "Type": "AWS::S3::Object",
          "Values": ["arn:aws:s3:::my-bucket/*"]
        }
      ]
    }
  ]
}

CloudFormation Template

AWSTemplateFormatVersion: '2010-09-09'
Resources:
  CloudTrail:
    Type: AWS::CloudTrail::Trail
    Properties:
      TrailName: MyCloudTrail
      S3BucketName: !Ref CloudTrailBucket
      S3KeyPrefix: cloudtrail-logs/
      IncludeGlobalServiceEvents: true
      IsMultiRegionTrail: true
      EnableLogFileValidation: true
      EventSelectors:
        - ReadWriteType: All
          IncludeManagementEvents: true
          DataResources:
            - Type: AWS::S3::Object
              Values: 
                - "arn:aws:s3:::my-sensitive-bucket/*"
      
  CloudTrailBucket:
    Type: AWS::S3::Bucket
    Properties:
      BucketName: my-cloudtrail-logs-bucket
      PublicAccessBlockConfiguration:
        BlockPublicAcls: true
        BlockPublicPolicy: true
        IgnorePublicAcls: true
        RestrictPublicBuckets: true

4. Event Structure

Standard Event Format

{
  "eventVersion": "1.08",
  "userIdentity": {
    "type": "IAMUser",
    "principalId": "AIDACKCEVSQ6C2EXAMPLE",
    "arn": "arn:aws:iam::123456789012:user/johndoe",
    "accountId": "123456789012",
    "accessKeyId": "AKIAIOSFODNN7EXAMPLE",
    "userName": "johndoe"
  },
  "eventTime": "2023-11-15T14:30:00Z",
  "eventSource": "ec2.amazonaws.com",
  "eventName": "RunInstances",
  "awsRegion": "us-east-1",
  "sourceIPAddress": "203.0.113.12",
  "userAgent": "aws-cli/2.0.0 Python/3.8.0",
  "requestParameters": {
    "instanceType": "t3.micro",
    "minCount": 1,
    "maxCount": 1
  },
  "responseElements": {
    "instancesSet": {
      "items": [
        {
          "instanceId": "i-1234567890abcdef0",
          "imageId": "ami-12345678",
          "state": {
            "code": 0,
            "name": "pending"
          }
        }
      ]
    }
  },
  "requestID": "12345678-1234-1234-1234-123456789012",
  "eventID": "87654321-4321-4321-4321-210987654321",
  "eventType": "AwsApiCall",
  "recipientAccountId": "123456789012",
  "serviceEventDetails": {
    "responseElements": null
  }
}

Key Event Fields

  • eventVersion - CloudTrail record format version
  • userIdentity - Information about user/role that made request
  • eventTime - Date and time of request (UTC)
  • eventSource - AWS service that request was made to
  • eventName - Requested action
  • awsRegion - AWS region where request was made
  • sourceIPAddress - IP address of requester
  • userAgent - Agent through which request was made
  • requestParameters - Parameters sent with request
  • responseElements - Response elements for actions that make changes
  • errorCode - AWS service error if request returned error
  • errorMessage - Description of error

5. IAM Roles & Permissions

CloudTrail Service Role

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "logs:CreateLogGroup",
        "logs:CreateLogStream",
        "logs:PutLogEvents",
        "logs:DescribeLogGroups",
        "logs:DescribeLogStreams"
      ],
      "Resource": "arn:aws:logs:*:*:*"
    }
  ]
}

S3 Bucket Policy for CloudTrail

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "AWSCloudTrailAclCheck",
      "Effect": "Allow",
      "Principal": {
        "Service": "cloudtrail.amazonaws.com"
      },
      "Action": "s3:GetBucketAcl",
      "Resource": "arn:aws:s3:::my-cloudtrail-bucket"
    },
    {
      "Sid": "AWSCloudTrailWrite",
      "Effect": "Allow",
      "Principal": {
        "Service": "cloudtrail.amazonaws.com"
      },
      "Action": "s3:PutObject",
      "Resource": "arn:aws:s3:::my-cloudtrail-bucket/*",
      "Condition": {
        "StringEquals": {
          "s3:x-amz-acl": "bucket-owner-full-control"
        }
      }
    }
  ]
}

Cross-Account CloudTrail Access

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "AWS": "arn:aws:iam::111111111111:root"
      },
      "Action": [
        "s3:GetBucketAcl",
        "s3:ListBucket"
      ],
      "Resource": "arn:aws:s3:::central-cloudtrail-bucket"
    },
    {
      "Effect": "Allow",
      "Principal": {
        "AWS": "arn:aws:iam::111111111111:root"
      },
      "Action": "s3:GetObject",
      "Resource": "arn:aws:s3:::central-cloudtrail-bucket/*"
    }
  ]
}

User Permissions for CloudTrail Analysis

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "cloudtrail:LookupEvents",
        "cloudtrail:GetTrailStatus",
        "cloudtrail:DescribeTrails"
      ],
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": [
        "s3:GetObject",
        "s3:ListBucket"
      ],
      "Resource": [
        "arn:aws:s3:::my-cloudtrail-bucket",
        "arn:aws:s3:::my-cloudtrail-bucket/*"
      ]
    }
  ]
}

6. Integration with AWS Services

CloudWatch Logs Integration

{
  "CloudWatchLogsLogGroupArn": "arn:aws:logs:us-east-1:123456789012:log-group:CloudTrail/MyTrail:*",
  "CloudWatchLogsRoleArn": "arn:aws:iam::123456789012:role/CloudTrail_CloudWatchLogs_Role"
}

EventBridge Integration

  • CloudTrail events automatically sent to EventBridge
  • Create rules to trigger on specific API calls
  • Real-time response to security events

EventBridge Rule Example

{
  "Rules": [
    {
      "Name": "DetectRootLogin",
      "EventPattern": {
        "source": ["aws.signin"],
        "detail-type": ["AWS Console Sign In via CloudTrail"],
        "detail": {
          "userIdentity": {
            "type": ["Root"]
          }
        }
      },
      "Targets": [
        {
          "Arn": "arn:aws:sns:us-east-1:123456789012:security-alerts",
          "Id": "1"
        }
      ]
    }
  ]
}

AWS Config Integration

  • CloudTrail provides “who” and “when”
  • Config provides “what changed”
  • Combined view of configuration changes

Amazon Athena Integration

  • Query CloudTrail logs using SQL
  • Analyze patterns and trends
  • Cost-effective for large-scale analysis

Athena Table Creation

CREATE EXTERNAL TABLE cloudtrail_logs (
  eventversion STRING,
  useridentity STRUCT<
    type:STRING,
    principalid:STRING,
    arn:STRING,
    accountid:STRING,
    invokedby:STRING,
    accesskeyid:STRING,
    userName:STRING,
    sessioncontext:STRUCT<
      attributes:STRUCT<
        mfaauthenticated:STRING,
        creationdate:STRING>,
      sessionissuer:STRUCT<
        type:STRING,
        principalId:STRING,
        arn:STRING,
        accountId:STRING,
        userName:STRING>>>,
  eventtime STRING,
  eventsource STRING,
  eventname STRING,
  awsregion STRING,
  sourceipaddress STRING,
  useragent STRING,
  errorcode STRING,
  errormessage STRING,
  requestparameters STRING,
  responseelements STRING,
  additionaleventdata STRING,
  requestid STRING,
  eventid STRING,
  resources ARRAY<STRUCT<
    ARN:STRING,
    accountId:STRING,
    type:STRING>>,
  eventtype STRING,
  apiversion STRING,
  readonly STRING,
  recipientaccountid STRING,
  serviceeventdetails STRING,
  sharedeventid STRING,
  vpcendpointid STRING
)
PARTITIONED BY (
  region string,
  year string,
  month string,
  day string
)
STORED AS INPUTFORMAT 'com.amazon.emr.cloudtrail.CloudTrailInputFormat'
OUTPUTFORMAT 'org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat'
LOCATION 's3://my-cloudtrail-bucket/AWSLogs/123456789012/CloudTrail/'

7. Security Best Practices

Encryption

  • S3 bucket encryption - Enable default encryption
  • SSE-KMS - Use customer managed keys for additional control
  • Log file validation - Enable to detect tampering

S3 Bucket Security

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "DenyInsecureConnections",
      "Effect": "Deny",
      "Principal": "*",
      "Action": "s3:*",
      "Resource": [
        "arn:aws:s3:::my-cloudtrail-bucket",
        "arn:aws:s3:::my-cloudtrail-bucket/*"
      ],
      "Condition": {
        "Bool": {
          "aws:SecureTransport": "false"
        }
      }
    },
    {
      "Sid": "DenyUnencryptedObjectUploads",
      "Effect": "Deny",
      "Principal": "*",
      "Action": "s3:PutObject",
      "Resource": "arn:aws:s3:::my-cloudtrail-bucket/*",
      "Condition": {
        "StringNotEquals": {
          "s3:x-amz-server-side-encryption": "AES256"
        }
      }
    }
  ]
}

Access Control

  • Use least privilege for CloudTrail access
  • Separate read and write permissions
  • Use resource-based policies for cross-account access
  • Enable MFA for sensitive operations

Monitoring

  • Monitor CloudTrail configuration changes
  • Alert on trail deletion or modification
  • Monitor for unusual API activity patterns
  • Set up CloudWatch alarms for critical events

8. Monitoring & Troubleshooting

CloudWatch Metrics

  • ErrorCount - Number of errors in log delivery
  • TotalSizeBytes - Size of log files delivered

CloudWatch Alarms

{
  "AlarmName": "CloudTrail-LogDeliveryErrors",
  "MetricName": "ErrorCount",
  "Namespace": "AWS/CloudTrail",
  "Statistic": "Sum",
  "Period": 300,
  "EvaluationPeriods": 1,
  "Threshold": 1,
  "ComparisonOperator": "GreaterThanOrEqualToThreshold",
  "AlarmActions": [
    "arn:aws:sns:us-east-1:123456789012:cloudtrail-alerts"
  ]
}

Common Issues

Trail Not Logging

  • Check trail status: aws cloudtrail get-trail-status
  • Verify S3 bucket permissions
  • Check IAM role permissions
  • Verify trail is enabled

Missing Events

  • Check if event type is enabled (management vs data events)
  • Verify region configuration (single vs multi-region)
  • Check event selectors configuration
  • Verify global services events setting

Log Delivery Delays

  • Normal delay: 5-15 minutes
  • Check CloudWatch metrics for errors
  • Verify S3 bucket accessibility
  • Check for S3 bucket policy restrictions

Troubleshooting Commands

# Check trail status
aws cloudtrail get-trail-status --name MyTrail

# Describe trail configuration
aws cloudtrail describe-trails --trail-name-list MyTrail

# Look up recent events
aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventName,AttributeValue=RunInstances

# Validate log file integrity
aws cloudtrail validate-logs --trail-arn arn:aws:cloudtrail:us-east-1:123456789012:trail/MyTrail --start-time 2023-11-15T00:00:00Z

9. Common Exam Scenarios

Scenario 1: Detect root account usage

Solution:

  • Create EventBridge rule for AWS Console Sign In events
  • Filter for userIdentity.type = “Root”
  • Target SNS topic for immediate alerts
  • Use CloudWatch Logs Insights for analysis

Scenario 2: Track S3 object access

Solution:

  • Enable data events for S3 in CloudTrail
  • Configure event selectors for specific buckets
  • Use GetObject, PutObject, DeleteObject events
  • Additional cost for data events

Scenario 3: Centralized logging for multiple accounts

Solution:

  • Create central S3 bucket in security account
  • Configure cross-account bucket policy
  • Create trails in each account pointing to central bucket
  • Use AWS Organizations for automated setup

Scenario 4: Detect unusual API activity

Solution:

  • Enable CloudTrail Insights
  • Monitor for spikes in API call volume
  • Set up EventBridge rules for Insight events
  • Use machine learning for anomaly detection

Scenario 5: Compliance audit requirements

Solution:

  • Enable log file validation
  • Use multi-region trail
  • Enable global services events
  • Set up long-term retention in S3
  • Use S3 Glacier for cost-effective archival

Scenario 6: Real-time security response

Solution:

  • Stream CloudTrail to CloudWatch Logs
  • Create CloudWatch Logs metric filters
  • Set up CloudWatch alarms
  • Trigger Lambda for automated response

Scenario 7: Investigate security incident

Solution:

  • Use CloudTrail Event History for recent events
  • Query CloudTrail logs in S3 using Athena
  • Filter by user, IP address, or time range
  • Correlate with VPC Flow Logs and GuardDuty

Scenario 8: Monitor infrastructure changes

Solution:

  • Focus on management events (write operations)
  • Filter for specific services (EC2, IAM, S3)
  • Use EventBridge for real-time notifications
  • Integrate with AWS Config for configuration tracking

10. CLI Commands Reference

Trail Management

# Create trail
aws cloudtrail create-trail \
  --name MyTrail \
  --s3-bucket-name my-cloudtrail-bucket \
  --include-global-service-events \
  --is-multi-region-trail \
  --enable-log-file-validation

# Start logging
aws cloudtrail start-logging --name MyTrail

# Stop logging
aws cloudtrail stop-logging --name MyTrail

# Get trail status
aws cloudtrail get-trail-status --name MyTrail

# Describe trails
aws cloudtrail describe-trails

# Delete trail
aws cloudtrail delete-trail --name MyTrail

Event Selectors

# Configure event selectors
aws cloudtrail put-event-selectors \
  --trail-name MyTrail \
  --event-selectors '[{
    "ReadWriteType": "All",
    "IncludeManagementEvents": true,
    "DataResources": [{
      "Type": "AWS::S3::Object",
      "Values": ["arn:aws:s3:::my-bucket/*"]
    }]
  }]'

# Get event selectors
aws cloudtrail get-event-selectors --trail-name MyTrail

Event Lookup

# Lookup events by attribute
aws cloudtrail lookup-events \
  --lookup-attributes AttributeKey=EventName,AttributeValue=CreateUser \
  --start-time 2023-11-01T00:00:00Z \
  --end-time 2023-11-15T23:59:59Z

# Lookup events by user
aws cloudtrail lookup-events \
  --lookup-attributes AttributeKey=Username,AttributeValue=johndoe

# Lookup events by resource
aws cloudtrail lookup-events \
  --lookup-attributes AttributeKey=ResourceName,AttributeValue=i-1234567890abcdef0

Insights

# Enable insights
aws cloudtrail put-insight-selectors \
  --trail-name MyTrail \
  --insight-selectors '[{
    "InsightType": "ApiCallRateInsight"
  }]'

# Get insights
aws cloudtrail get-insight-selectors --trail-name MyTrail

11. Architecture Patterns

Single Account Setup

AWS Account
    ↓
CloudTrail Trail
    ↓
S3 Bucket → CloudWatch Logs → EventBridge → SNS/Lambda

Multi-Account Centralized Logging

Account A (Dev)     Account B (Prod)     Account C (Security)
     ↓                    ↓                      ↓
CloudTrail Trail    CloudTrail Trail      Central S3 Bucket
     ↓                    ↓                      ↓
     └────────────────────┴──────────────→ Athena Analysis
                                               ↓
                                          Security Team

Real-Time Security Monitoring

CloudTrail → CloudWatch Logs → Metric Filter → CloudWatch Alarm
                                                      ↓
                                               SNS → Lambda
                                                      ↓
                                              Automated Response

Compliance Architecture

CloudTrail (Multi-Region) → S3 Bucket (Encrypted)
                                ↓
                         S3 Lifecycle Policy
                                ↓
                    S3 Glacier (Long-term Archive)
                                ↓
                         Compliance Reports

12. Best Practices for DOP-C02 Exam

Security

  • Always enable log file validation
  • Use customer managed KMS keys for encryption
  • Enable MFA delete on S3 bucket
  • Use least privilege IAM policies
  • Enable S3 bucket versioning
  • Block public access on CloudTrail S3 buckets

Operational

  • Use multi-region trails for global visibility
  • Enable global services events
  • Set up CloudWatch alarms for critical events
  • Use EventBridge for real-time response
  • Implement log retention policies
  • Regular backup of CloudTrail configuration

Cost Optimization

  • Use data events selectively (high cost)
  • Implement S3 lifecycle policies
  • Use S3 Intelligent Tiering
  • Archive old logs to Glacier
  • Monitor CloudTrail costs regularly

Compliance

  • Enable CloudTrail in all regions
  • Use AWS Organizations for centralized setup
  • Implement cross-account logging
  • Regular audit of CloudTrail configuration
  • Document retention policies
  • Use AWS Config for configuration compliance

13. Comparison with Other Services

CloudTrail vs CloudWatch Logs

FeatureCloudTrailCloudWatch Logs
PurposeAPI audit loggingApplication/system logs
Data SourceAWS API callsApplications, OS, AWS services
RetentionIndefinite (S3)Configurable
CostPer trail + S3 storagePer GB ingested/stored

CloudTrail vs AWS Config

FeatureCloudTrailAWS Config
FocusWho did what, whenWhat changed
DataAPI calls and eventsResource configurations
TimelineReal-time eventsConfiguration snapshots
Use CaseAudit and complianceConfiguration management

CloudTrail vs VPC Flow Logs

FeatureCloudTrailVPC Flow Logs
ScopeAWS API callsNetwork traffic
LevelAccount/serviceNetwork interface
DataAPI metadataIP, port, protocol
Use CaseSecurity auditNetwork troubleshooting

14. Exam Tips

What to Remember

  • 90-day Event History - Available by default, no trail needed
  • Management events - Enabled by default in trails
  • Data events - Additional cost, not enabled by default
  • Multi-region trails - Log events from all regions
  • Global services - IAM, CloudFront, Route 53 events
  • Log file validation - Detect tampering with digest files
  • Real-time delivery - 5-15 minute delay to S3
  • EventBridge integration - Automatic for all CloudTrail events

Common Traps

  • Data events are NOT enabled by default (cost implications)
  • Event History is only 90 days (need trail for longer retention)
  • Global services events only logged in us-east-1 by default
  • CloudTrail does NOT log data plane operations by default
  • Log file validation requires separate digest files
  • Cross-account access requires both IAM and S3 bucket policies

Scenario-Based Questions

  • Focus on security incident investigation
  • Understand compliance and audit requirements
  • Know real-time vs batch processing options
  • Understand cost implications of data events
  • Know integration with other AWS services
  • Understand multi-account logging strategies

Key Integrations to Know

  • EventBridge - Real-time event processing
  • CloudWatch Logs - Log aggregation and analysis
  • Athena - SQL queries on CloudTrail logs
  • AWS Config - Configuration change tracking
  • GuardDuty - Security threat detection
  • S3 - Log storage and lifecycle management

15. Quick Reference Cheat Sheet

Essential CLI Commands

aws cloudtrail create-trail --name MyTrail --s3-bucket-name bucket
aws cloudtrail start-logging --name MyTrail
aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventName,AttributeValue=CreateUser
aws cloudtrail get-trail-status --name MyTrail

Event Types

  • Management Events - Control plane (create, delete, modify)
  • Data Events - Data plane (GetObject, PutObject)
  • Insight Events - Unusual activity patterns (ML-based)

Key Event Fields

eventName, eventSource, eventTime, userIdentity, sourceIPAddress,
requestParameters, responseElements, errorCode, awsRegion

Trail Configuration Options

  • Single-region vs Multi-region
  • Global services events (IAM, CloudFront, Route 53)
  • Log file validation (integrity checking)
  • CloudWatch Logs integration
  • Event selectors (management vs data events)

16. Reference Links

AWS Official Documentation

  • CloudTrail User Guide
  • CloudTrail Event Reference
  • CloudTrail Log File Examples
  • CloudTrail Supported Services
  • CloudTrail Insights

Workshops

  • Security Workshop - CloudTrail
  • Well-Architected Security Labs

Whitepapers

  • AWS Security Best Practices
  • AWS Logging and Monitoring Guide

17. Summary

AWS CloudTrail is essential for security, compliance, and operational visibility in AWS environments and is heavily tested in the DOP-C02 exam. Key areas to master:

  1. Event types (management, data, insight) and their use cases
  2. Trail configuration (single vs multi-region, global services)
  3. IAM permissions for CloudTrail and S3 bucket policies
  4. Integration with CloudWatch, EventBridge, Athena, Config
  5. Security best practices (encryption, validation, access control)
  6. Real-time monitoring with EventBridge and CloudWatch
  7. Compliance requirements and multi-account strategies
  8. Cost optimization for data events and storage
  9. Troubleshooting common issues and log analysis
  10. Event structure and key fields for investigation

Understanding these concepts with hands-on practice will ensure success on CloudTrail-related questions in the DOP-C02 exam.

      What's in this dop-c02

      • 1. Overview
        • Key Characteristics
        • What Problem Does It Solve?
      • 2. Core Concepts
        • Trail
        • Event
        • Management Events
        • Data Events
        • Insight Events
        • Event History
      • 3. Trail Configuration
        • Basic Trail Configuration
        • CloudFormation Template
      • 4. Event Structure
        • Standard Event Format
        • Key Event Fields
      • 5. IAM Roles & Permissions
        • CloudTrail Service Role
        • S3 Bucket Policy for CloudTrail
        • Cross-Account CloudTrail Access
        • User Permissions for CloudTrail Analysis
      • 6. Integration with AWS Services
        • CloudWatch Logs Integration
        • EventBridge Integration
        • EventBridge Rule Example
        • AWS Config Integration
        • Amazon Athena Integration
        • Athena Table Creation
      • 7. Security Best Practices
        • Encryption
        • S3 Bucket Security
        • Access Control
        • Monitoring
      • 8. Monitoring & Troubleshooting
        • CloudWatch Metrics
        • CloudWatch Alarms
        • Common Issues
        • Troubleshooting Commands
      • 9. Common Exam Scenarios
        • Scenario 1: Detect root account usage
        • Scenario 2: Track S3 object access
        • Scenario 3: Centralized logging for multiple accounts
        • Scenario 4: Detect unusual API activity
        • Scenario 5: Compliance audit requirements
        • Scenario 6: Real-time security response
        • Scenario 7: Investigate security incident
        • Scenario 8: Monitor infrastructure changes
      • 10. CLI Commands Reference
        • Trail Management
        • Event Selectors
        • Event Lookup
        • Insights
      • 11. Architecture Patterns
        • Single Account Setup
        • Multi-Account Centralized Logging
        • Real-Time Security Monitoring
        • Compliance Architecture
      • 12. Best Practices for DOP-C02 Exam
        • Security
        • Operational
        • Cost Optimization
        • Compliance
      • 13. Comparison with Other Services
        • CloudTrail vs CloudWatch Logs
        • CloudTrail vs AWS Config
        • CloudTrail vs VPC Flow Logs
      • 14. Exam Tips
        • What to Remember
        • Common Traps
        • Scenario-Based Questions
        • Key Integrations to Know
      • 15. Quick Reference Cheat Sheet
        • Essential CLI Commands
        • Event Types
        • Key Event Fields
        • Trail Configuration Options
      • 16. Reference Links
        • AWS Official Documentation
        • Workshops
        • Whitepapers
      • 17. Summary
      © Album69 2026
      X GitHub LinkedIn YouTube