AWS Certified DevOps Engineer - Professional (DOP-C02) glossary
Terms selected for AWS Certified DevOps Engineer - Professional (DOP-C02) based on common objective language and practice focus.
Alerting Thresholds
Alerting thresholds are predefined limits that trigger alerts when system metrics exceed acceptable values, indicating potential issues.
Read full term ->Architecture Safeguards
Architecture safeguards are proactive measures incorporated into system design to prevent failures and improve system reliability.
Read full term ->Automated Response Patterns
Automated response patterns are predefined actions that systems automatically execute in response to specific events or incidents.
Read full term ->Blue/Green Deployment
Release strategy that shifts traffic from current environment to a parallel new environment after validation.
Read full term ->Canary Deployment
Progressive release method where a small percentage of users receive a new version before full rollout.
Read full term ->Chaos Engineering
Practice of intentionally introducing failures to validate system resilience and operational readiness.
Read full term ->CI/CD Pipeline
Automated workflow that integrates source changes, validates builds, runs tests, and deploys releases reliably.
Read full term ->CI/CD Workflow
A CI/CD workflow automates the process of integrating code changes, testing them, and deploying them to production environments.
Read full term ->CloudFormation Change Set
Preview of proposed infrastructure modifications before executing a CloudFormation stack update.
Read full term ->Compliance Release Gates
Compliance release gates are checkpoints in the CI/CD pipeline that ensure code changes meet regulatory and organizational compliance requirements before deployment.
Read full term ->Configuration Drift
Configuration drift occurs when the configuration of infrastructure resources deviates from the desired state defined in code.
Read full term ->Deployment Controls
Deployment controls are mechanisms integrated into CI/CD pipelines to ensure that only validated and approved code changes are deployed to production environments.
Read full term ->Disaster Recovery Strategy
A disaster recovery strategy outlines the procedures and technologies used to recover and restore services after a catastrophic event.
Read full term ->Error Budget
Allowed unreliability amount derived from SLO targets, used to balance velocity and stability.
Read full term ->Event-Driven Remediation
Event-driven remediation involves automatically executing corrective actions in response to specific events to minimize downtime and service disruption.
Read full term ->GitOps
Operational model where Git repositories are the source of truth for infrastructure and application configuration.
Read full term ->High Availability Patterns
High availability patterns are design strategies that ensure applications remain operational and accessible even in the event of failures.
Read full term ->Identity and Access Management
Identity and Access Management (IAM) involves defining and managing the roles and permissions of users and systems to ensure secure access to resources.
Read full term ->Immutable Infrastructure
Deployment approach where components are replaced rather than patched in place.
Read full term ->Blameless Postmortem
Structured incident review focused on systemic learning and prevention rather than individual blame.
Read full term ->Incident Runbooks
Incident runbooks are detailed guides that outline the steps and procedures to follow during incident response to ensure effective resolution.
Read full term ->Infrastructure Drift
Condition where actual environment configuration diverges from declared infrastructure-as-code definitions.
Read full term ->Infrastructure Patterns
Infrastructure patterns are reusable templates or blueprints that define the architecture and configuration of cloud resources for consistent deployment across environments.
Read full term ->Infrastructure Provisioning
Infrastructure provisioning is the automated process of setting up and configuring cloud resources using Infrastructure as Code (IaC) tools.
Read full term ->Log Analysis
Log analysis involves collecting, examining, and interpreting log data to troubleshoot and optimize system performance.
Read full term ->Observability Controls
Observability controls are tools and practices used to monitor and gain insights into the performance and health of systems and applications.
Read full term ->Observability
Operational capability to understand system state through metrics, logs, traces, and events.
Read full term ->Policy as Code
Encoding governance and security rules in machine-readable form for automated validation.
Read full term ->Progressive Delivery
Release discipline that incrementally exposes new functionality based on automated validation and risk controls.
Read full term ->Release Strategy
A release strategy defines the approach for deploying applications to production, including methods for minimizing risk and ensuring stability.
Read full term ->Rollback Strategy
Predefined method for reverting deployments quickly when metrics or health checks degrade.
Read full term ->Secrets Rotation
Automated periodic renewal of credentials to reduce compromise risk and credential lifetime.
Read full term ->Security Controls
Security controls are policies and mechanisms integrated into systems and processes to protect data and resources from unauthorized access and threats.
Read full term ->SLO, SLI, and SLA
Reliability measurement framework: indicators, internal targets, and external commitments.
Read full term ->