The official AWS Certified DevOps Engineer - Professional syllabus, organized by domain. Check off each point as you review it.
Inicia sesión para guardar tu progreso entre sesiones.
Implement CI/CD pipelines
CodeArtifact recommends one repository per domain holding the external connection to a public registry, with the other repositories using it as an upstream; cross-account access needs both a domain policy and a repository policy. In Amazon ECR, lifecycle policies expire images by rule priority, cross-account replication needs only a registry policy in the destination, and pull through cache rules sync registries such as Docker Hub.
Connect a CodeArtifact repository to a public repository ↗Automate the cleanup of images by using lifecycle policies in Amazon ECR ↗
CodePipeline V2 pipelines with AWS CodeConnections connections support push triggers (branches, file paths and Git tags) and pull request triggers; filters inside one event type are ANDed and excludes take precedence. The CODEBUILD_CLONE_REF output format hands CodeBuild a full Git clone, and CloudFormation Git sync keeps a stack in sync with its template in the repository.
Automate starting pipelines using triggers and filtering ↗Syncing stacks with source code stored in a Git repository with Git sync ↗
CodeBuild runs the install, pre_build, build and post_build phases of the buildspec; Amazon S3 caching is shared across build hosts and supports dynamic keys, while local caching serves only the same host and is not supported with a VPC. VPC builds use private subnets with a NAT gateway, Docker builds need privileged mode, and exported-variables passes values to later CodePipeline actions.
Build specification reference for CodeBuild ↗Use AWS CodeBuild with Amazon Virtual Private Cloud ↗
CodeBuild retrieves secrets with the parameter-store and secrets-manager buildspec sections or PARAMETER_STORE and SECRETS_MANAGER variables, never PLAINTEXT. CloudFormation uses secretsmanager dynamic references (other accounts by full ARN) and ssm-secure (same account only). Cross-account access needs a resource policy and a customer managed KMS key, and ECS injects a secret when the task starts.
Build specification reference for CodeBuild ↗Access AWS Secrets Manager secrets from a different account ↗
CodeDeploy supports in-place and blue/green deployments with predefined canary, linear and all-at-once configurations for ECS and Lambda, and rolls back automatically on failure or when a CloudWatch alarm fires. ECS has native blue/green deployments with test traffic, lifecycle hooks and bake time; Elastic Beanstalk offers rolling, immutable and traffic-splitting policies, and AWS SAM automates gradual Lambda deployments.
Working with deployment configurations in CodeDeploy ↗Deployment policies and settings ↗
Integrate automated testing into CI/CD pipelines
CodeBuild starts builds from GitHub, GitLab and Bitbucket webhooks filtered by pull request events, BASE_REF, HEAD_REF or FILE_PATH, and the pull request build policy can require comment approval by a trusted contributor. CodePipeline V2 supports pull request triggers with the PARALLEL execution mode, and for CodeCommit, EventBridge rules on pull request events plus approval rule templates control testing and merges.
GitHub webhook events ↗Automate starting pipelines using triggers and filtering ↗
Distributed Load Testing on AWS runs JMeter, k6 or Locust load tests in Fargate containers across Regions without servers to manage. AWS FIS runs experiments with actions, targets selected by tags and stop conditions based on CloudWatch alarms; CloudWatch Synthetics canaries measure availability and latency on a schedule, and CodeBuild batch builds split tests across isolated environments.
Automate the testing of your software applications at scale ↗Stop conditions for AWS FIS ↗
In ECS, a container health check runs a command whose exit code 0 means success and any non-zero code means failure; only health checks defined in the task definition are monitored, and CMD-SHELL enables shell operators. cfn-signal sends the cfn-init exit code to a creation policy with -e $?, and a Lambda action in CodePipeline reports its result with PutJobSuccessResult or PutJobFailureResult.
Determine Amazon ECS task health using container health checks ↗cfn-signal ↗
CodeBuild creates test reports (JUnit XML, NUnit, TestNG, Cucumber JSON, Visual Studio TRX) and coverage reports (JaCoCo XML, SimpleCov, Clover, Cobertura, LCOV) from the buildspec reports section. A group name creates a group prefixed with the project name and an ARN reuses an existing one; the role needs BatchPutTestCases and BatchPutCodeCoverages, and raw files can be exported to S3.
Test reports in AWS CodeBuild ↗Create code coverage reports ↗
CodePipeline invokes AWS services for testing through managed actions: the Lambda action must close the job with PutJobSuccessResult or PutJobFailureResult (with a continuationToken for long work), the Step Functions action starts a state machine and, for Standard workflows, returns its output as an artifact, and InspectorScan fails on severity thresholds. CodeBuild publishes test and coverage reports from the reports section.
AWS Lambda invoke action reference ↗AWS Step Functions invoke action reference ↗
Build and manage artifacts
In CodeArtifact the recommended layout is one repository per domain with the external connection to the public registry and the others using it as an upstream; package origin controls (Publish/Upstream) prevent dependency substitution. In ECR, cross-account replication needs a registry policy in the destination, destination settings come from repository creation templates, and pull through cache syncs registries such as Docker Hub.
Connect a CodeArtifact repository to a public repository ↗Private image replication in Amazon ECR ↗
CodeBuild produces artifacts as defined in the buildspec: artifacts and secondary-artifacts for several outputs, exported-variables to pass values to CodePipeline, and cache with dynamic keys in S3. Batch builds (graph, list, matrix, fanout) use their own batch role. Lambda compute starts faster but does not support Docker, privileged mode, VPC access or caching.
Build specification reference for CodeBuild ↗Run builds on AWS Lambda compute ↗
EC2 Image Builder automates images with recipes (AMI, or container with a Dockerfile and an ECR repository), build and test components, temporary infrastructure, and distribution to Regions and accounts, including launch template updates. Scheduled pipelines can run only when dependencies change, Amazon Inspector scans the images, and lifecycle policies retire old ones.
How EC2 Image Builder works ↗Configure AMI distribution with an EC2 launch template ↗
Implement deployment strategies for instance, container, and serverless environments
Access to artifact repositories combines IAM and resource policies: CodeArtifact needs codeartifact:GetAuthorizationToken and sts:GetServiceBearerToken on the identity, plus a domain and a repository policy for other accounts, which accept aws:PrincipalOrgID. In ECS, the task execution role pulls images from ECR or from private registries with repositoryCredentials. Cross-account artifacts need a customer managed KMS key.
AWS CodeArtifact authentication and tokens ↗Amazon ECS task execution IAM role ↗
The CodeDeploy agent is needed only on the EC2/On-Premises platform, not for ECS or Lambda. It is installed and updated with its Systems Manager Distributor package through State Manager; on-premises instances register with an IAM session ARN and temporary credentials. Its configuration file controls :max_revisions:, :proxy_uri: and :enable_auth_policy:, required with VPC endpoints.
Working with the CodeDeploy agent ↗Use CodeDeploy with Amazon Virtual Private Cloud ↗
Deployment failures are diagnosed from the events and logs of each lifecycle event. In CodeDeploy, ApplicationStop uses the scripts of the last successful revision (--ignore-application-stop-failures unblocks it), long-running processes must be redirected to /dev/null, and DownloadBundle fails on permissions or a bucket in another Region. In ECS, the deployment circuit breaker rolls back and emits EventBridge events.
Troubleshoot EC2/On-Premises deployment issues ↗How the Amazon ECS deployment circuit breaker detects failures ↗
Each platform has its own methods: Elastic Beanstalk offers all at once, rolling, rolling with additional batch, immutable, traffic splitting and blue/green with a CNAME swap; CodeDeploy does in-place or blue/green on EC2 and canary, linear or all-at-once on Lambda and ECS; ECS has native blue/green, linear and canary with bake time; and API Gateway runs canary releases on a stage.