Skip to Content
Cloud Engineering Academy
9. DevOps & CI/CD

Module 9 cheat sheet

One-page revision summary for DevOps & CI/CD: services, Azure DevOps mapping, commands, limits and defaults, decision rules, exam traps and cost traps.

DOP-C02DVA-C03

Assumes: AWS CLI v2 · GitHub Actions · CodePipeline V2 · .NET 10 LTS · Region us-east-1 · facts as stated in the Module 9 lessons; items marked VERIFY there are not repeated as certain here. Verified against official sources on 2026-11-18.

A printable summary of Module 9. Each row links back to the lesson with the detail. Source control in this module is GitHub, connected to AWS services through CodeConnections; AWS CodeCommit is optional (see the module overview for its availability history).

Key services

ServiceWhat it is for
GitHub rulesets, CODEOWNERS, environmentsProtected main, required reviews, required checks, approval gates (see Git and GitHub)
GitHub ActionsWorkflow runner; assumes AWS roles with OIDC, no stored keys
IAM OIDC provider + rolesShort-lived credentials via AssumeRoleWithWebIdentity, scoped by trust policy
CodeConnectionsLets CodePipeline and CodeBuild read a GitHub repository
CodeBuildRuns buildspec.yml in a container; builds and tests
CodePipeline (V2)Orchestrates source, build, approval and deploy stages
CodeDeployTraffic shifting for Lambda aliases (and the older ECS controller) with hooks and alarms
Amazon ECRImage registry: immutable tags, scan on push, lifecycle policy
ECS deployment strategiesROLLING, BLUE_GREEN, LINEAR, CANARY with alarms and circuit breaker
Secrets Manager / Parameter StoreRuntime secrets, fetched by the app, not by the pipeline

.NET / Azure DevOps → AWS

Microsoft / AzureAWS
Azure Repos + branch policiesGitHub rulesets + CODEOWNERS (or CodeCommit approval rule templates)
Azure Pipelines YAMLGitHub Actions workflow, or CodePipeline + CodeBuild
Service connection with a secretOIDC provider + IAM role, no secret
Environments with approvalsGitHub environments with required reviewers, or CodePipeline manual approval
App Service deployment slotsECS BLUE_GREEN with bake time; Lambda alias with weighted traffic
Variable groups / Key Vault linkEnvironment secrets / Secrets Manager / Parameter Store
Azure Artifacts / ACRCodeArtifact / ECR
Subscription per environmentAWS account per environment under Organizations

Most useful commands

TaskCommand
Who am I (which role did the pipeline get)?aws sts get-caller-identity
List OIDC providersaws iam list-open-id-connect-providers
Show a role's trust policyaws iam get-role --role-name NAME --query Role.AssumeRolePolicyDocument
Image digest for a tagaws ecr describe-images --repository-name REPO --image-ids imageTag=TAG --query 'imageDetails[0].imageDigest' --output text
Scan findingsaws ecr describe-image-scan-findings --repository-name REPO --image-id imageTag=TAG
Start a pipelineaws codepipeline start-pipeline-execution --name NAME
Approve a manual stageaws codepipeline put-approval-result ...
Start a CodeBuild buildaws codebuild start-build --project-name NAME
Watch an ECS deploymentaws ecs describe-services --cluster C --services S
Publish a Lambda versionaws lambda publish-version --function-name FN
Move an aliasaws lambda update-alias --function-name FN --name live --function-version N
Offline trust-policy proof (lab)dotnet run --project src/Harbourline.Delivery -- trust-eval POLICY.json CLAIMS.json
Leftovers after a labaws resourcegroupstaggingapi get-resources --tag-filters Key=Lab,Values=m09-delivery-pipeline

Key limits and defaults

ItemValueLesson
GitHub OIDC provider URL / audiencehttps://token.actions.githubusercontent.com / sts.amazonaws.comGitHub Actions with OIDC
Thumbprint for the GitHub providerNot needed; IAM validates the certificate chainGitHub Actions with OIDC
Workflow permission for the tokenpermissions: id-token: writeGitHub Actions with OIDC
OIDC sub formsrepo:O/R:environment:prod, repo:O/R:ref:refs/heads/main, repo:O/R:pull_requestGitHub Actions with OIDC
Role session1 hour by default (configurable up to the role maximum)GitHub Actions with OIDC
ECR tag immutabilityA tag cannot be re-pointed; bump the versionDocker and ECR
ECR scanningBasic on push (included); enhanced via Inspector (billed)Docker and ECR
Circuit breakerRolling updates onlyECS strategies
BLUE_GREENYou must set bakeTimeInMinutesECS strategies
Lambda canary configse.g. CodeDeployDefault.LambdaCanary10Percent5Minutes, LambdaLinear10PercentEvery1Minute, LambdaAllAtOnceLambda deployments
permissions: blockA job that sets it replaces the defaults entirelyPipeline security

Decision rules

If…Then…
Code is on GitHub and you want one toolGitHub Actions + OIDC
Policy requires AWS-native orchestrationCodePipeline V2 + CodeBuild, source via CodeConnections
Need to promote to prod safelyBuild once, deploy the same image digest to each environment
Stateless internal APIROLLING + circuit breaker + alarms
Customer-facing or payments APIBLUE_GREEN or CANARY with bake time and alarm rollback
Lambda releaseVersion + alias + CodeDeploy canary with hooks and alarms
Fastest back-out of new behaviourFeature flag, then code rollback
Schema changeExpand, migrate, contract across separate releases; never a destructive change in the same release
Pipeline needs AWS accessOIDC role per repository and environment; no long-lived keys
Runtime secretApp reads it from Secrets Manager; the pipeline never holds it
Infra changePlan on PR with a read-only role; apply only from main after environment approval, applying the reviewed plan
Segregation of dutiesRelease policy check blocks when the approver is the author

Common exam traps

  • A tag is not an identity: deploy by digest; mutable tags such as latest can change under you.
  • A trust policy without a sub condition lets any repository using GitHub's provider assume the role; always pin aud and sub.
  • Wildcards in sub (StringLike) are the usual mistake: repo:org/* trusts every repository.
  • Fork and pull-request jobs must hold no cloud role; avoid pull_request_target with untrusted code.
  • Circuit breaker is rolling-only; traffic-shifting strategies rely on health checks, hooks and alarms.
  • Rollback cannot undo data: only backward-compatible (expand/contract) changes roll back safely.
  • Lambda alias traffic is weighted between two versions and only published versions are immutable; $LATEST is mutable.
  • CodePipeline V2 is billed per action minute (see the CodeBuild lesson for V1 versus V2).
  • CodeCommit availability changed over time; GitHub with CodeConnections is the default in this course.
  • Pinning actions means a full commit SHA, not @v4.

Cost traps

TrapAvoid it by
ALB and Fargate left running after a blue/green labDeploy, test and destroy within an hour; tag everything and list by tag
Both blue and green running longer than neededShort bake time in labs
ECR images accumulatingLifecycle policy; delete the repository after the module
ECR enhanced scanning (Inspector)Use basic scanning for labs
CodePipeline V2 action minutes and CodeBuild minutesTreat Lab 9.6 as optional; small compute type
Private-repository Actions minutesUse a public repository or watch the monthly allowance
Evidence bucket versions kept foreverLifecycle rules; Object Lock only where policy needs it

Independent learning resource — not affiliated with, endorsed or sponsored by Amazon Web Services. AWS and related marks are trademarks of Amazon.com, Inc. or its affiliates. All banking data in examples is fictional. Sample architectures are for learning and are not automatically compliant with GDPR, PCI DSS or any banking regulation.

On this page