AWS Certified DevOps
1 Domain 1: SDLC Automation
1.1 Continuous Integration and Continuous Deployment (CICD)
1.1 1 Design and implement CICD pipelines
1.1 2 Manage code repositories
1.1 3 Implement deployment strategies
1.2 Infrastructure as Code (IaC)
1.2 1 Define and deploy infrastructure using AWS CloudFormation
1.2 2 Manage and modularize templates
1.2 3 Implement service and infrastructure bluegreen deployments
1.3 Configuration Management
1.3 1 Automate configuration management
1.3 2 Implement and manage configuration changes
1.3 3 Implement and manage infrastructure changes
1.4 Monitoring and Logging
1.4 1 Design and implement logging and monitoring
1.4 2 Analyze and troubleshoot issues
1.4 3 Implement and manage alarms and notifications
2 Domain 2: Configuration Management and Infrastructure as Code
2.1 Infrastructure as Code (IaC)
2.1 1 Define and deploy infrastructure using AWS CloudFormation
2.1 2 Manage and modularize templates
2.1 3 Implement service and infrastructure bluegreen deployments
2.2 Configuration Management
2.2 1 Automate configuration management
2.2 2 Implement and manage configuration changes
2.2 3 Implement and manage infrastructure changes
2.3 Version Control
2.3 1 Manage code repositories
2.3 2 Implement version control strategies
2.3 3 Manage branching and merging
3 Domain 3: Monitoring and Logging
3.1 Monitoring
3.1 1 Design and implement monitoring
3.1 2 Implement and manage alarms and notifications
3.1 3 Analyze and troubleshoot issues
3.2 Logging
3.2 1 Design and implement logging
3.2 2 Analyze and troubleshoot issues
3.2 3 Implement and manage log retention and archival
3.3 Metrics and Dashboards
3.3 1 Design and implement metrics collection
3.3 2 Create and manage dashboards
3.3 3 Analyze and troubleshoot performance issues
4 Domain 4: Policies and Standards Automation
4.1 Security and Compliance
4.1 1 Implement and manage security policies
4.1 2 Implement and manage compliance policies
4.1 3 Automate security and compliance checks
4.2 Cost Management
4.2 1 Implement and manage cost optimization strategies
4.2 2 Automate cost monitoring and alerts
4.2 3 Analyze and troubleshoot cost issues
4.3 Governance
4.3 1 Implement and manage governance policies
4.3 2 Automate governance checks
4.3 3 Analyze and troubleshoot governance issues
5 Domain 5: Incident and Event Response
5.1 Incident Management
5.1 1 Design and implement incident management processes
5.1 2 Automate incident detection and response
5.1 3 Analyze and troubleshoot incidents
5.2 Event Management
5.2 1 Design and implement event management processes
5.2 2 Automate event detection and response
5.2 3 Analyze and troubleshoot events
5.3 Root Cause Analysis
5.3 1 Perform root cause analysis
5.3 2 Implement preventive measures
5.3 3 Analyze and troubleshoot root cause issues
6 Domain 6: High Availability, Fault Tolerance, and Disaster Recovery
6.1 High Availability
6.1 1 Design and implement high availability architectures
6.1 2 Implement and manage load balancing
6.1 3 Analyze and troubleshoot availability issues
6.2 Fault Tolerance
6.2 1 Design and implement fault-tolerant architectures
6.2 2 Implement and manage failover strategies
6.2 3 Analyze and troubleshoot fault tolerance issues
6.3 Disaster Recovery
6.3 1 Design and implement disaster recovery strategies
6.3 2 Implement and manage backup and restore processes
6.3 3 Analyze and troubleshoot disaster recovery issues
5.2 Event Management Explained

Event Management Explained

Key Concepts

Detailed Explanation

Event Sources

Event sources are the originators of events. These can be AWS services like EC2, S3, or custom applications. Events are generated when specific actions occur, such as an S3 bucket being created or an EC2 instance being terminated.

Event Patterns

Event patterns are predefined rules that match specific events. These patterns define the criteria for which events should be routed to event targets. For example, an event pattern might specify that only events related to EC2 instance terminations should be processed.

Event Bus

An event bus is a channel that routes events between event sources and event targets. It acts as a central hub for event management, allowing events to be filtered, transformed, and delivered to the appropriate targets.

Event Targets

Event targets are the destinations where events are sent. These can include AWS services like Lambda functions, SNS topics, SQS queues, or custom HTTP endpoints. Event targets process the events and take appropriate actions based on the event data.

EventBridge

EventBridge is a serverless event bus service that makes it easy to connect applications using data from various sources. It allows you to create event-driven architectures by routing events from event sources to event targets based on defined event patterns.

Examples and Analogies

Example: EventBridge Rule

Here is an example of creating an EventBridge rule to trigger a Lambda function when an S3 bucket is created:

{
    "Source": ["aws.s3"],
    "DetailType": ["AWS API Call via CloudTrail"],
    "Detail": {
        "eventSource": ["s3.amazonaws.com"],
        "eventName": ["CreateBucket"]
    }
}
    

Example: Event Target

Here is an example of configuring an EventBridge target to invoke a Lambda function:

{
    "Id": "1",
    "Arn": "arn:aws:lambda:us-east-1:123456789012:function:MyLambdaFunction"
}
    

Analogy: Event Management as a Mailroom

Think of event management as a mailroom in a large organization. Event sources are like departments that generate mail (events). Event patterns are like sorting rules that determine which mail goes to which recipient. The event bus is like the mailroom itself, where mail is sorted and routed. Event targets are like recipients who receive and process the mail. EventBridge is like the mailroom management system that automates the entire process, ensuring that mail is delivered efficiently and accurately.