Instiq
Chapter 3 · Continuous Improvement for Existing Solutions·v2.1.0·Updated 6/28/2026·~11 min

What's changed: Service coverage: added a catalog section (s4) for developer tools and operations management (CI/CD, Grafana/Prometheus, Proton, Amplify/Device Farm)

3.4Developer Tools and Operations Management Services

Key points

Supporting services for improvement and automated delivery—CI/CD pipelines (CodePipeline, CodeBuild, CodeDeploy, CodeArtifact, CodeGuru), open-source-compatible observability (Managed Grafana, Managed Service for Prometheus), standardized templates (Proton), and frontend/testing (Amplify, Device Farm)—by definition, role, and when to choose.

Continuous improvement needs pipelines that deliver change safely and automatically, plus a basis to observe state. This section organizes the related services by definition, role, and when to choose.

3.4.1CI/CD pipeline

  • AWS CodePipeline: orchestration that automates the build to test to deploy flow. Choose it to chain stages triggered by source changes (the overall pipeline controller).
  • AWS CodeBuild: managed build that compiles/tests/produces artifacts. Choose it to run CI builds without managing servers.
  • AWS CodeDeploy: automated deployment to EC2/on-prem/Lambda/ECS (rolling/blue-green/canary). Choose it to automate releases with safe deployment strategies.
  • AWS CodeArtifact: managed repository for software packages (npm/Maven/PyPI, etc.). Choose it to share and cache internal dependencies securely.
  • Amazon CodeGuru: ML-based automated code-review findings and application profiling. Choose it to continuously improve code quality and expensive code paths.

3.4.2Open-source-compatible observability

  • Amazon Managed Grafana: managed Grafana (dashboard visualization). Choose it to visualize metrics from many sources in Grafana centrally.
  • Amazon Managed Service for Prometheus: managed Prometheus (time-series metrics). Choose it to store Kubernetes/container Prometheus metrics without operational overhead.

3.4.3Standardization, frontend, and testing

  • AWS Proton: lets a platform team define standard container/serverless templates and offer self-service to developers to standardize and govern IaC and deployments across an organization (note: AWS Proton stopped onboarding new customers in 2024; alternatives are Service Catalog or CDK/CloudFormation plus pipelines).
  • AWS Amplify: combines frontend/full-stack hosting with backend provisioning. Choose it to launch web/mobile apps quickly with CI/CD hosting included.
  • AWS Device Farm: cloud service to test apps on real phones/browsers. Choose it to automate compatibility testing across many real devices.
Exam point

Common distinctions: whole pipeline = CodePipeline; build = CodeBuild; deploy (blue-green, etc.) = CodeDeploy; package management = CodeArtifact; code quality/profiling = CodeGuru; Grafana dashboards = Managed Grafana; Prometheus metrics = Managed Service for Prometheus; IaC standardization = Proton; real-device testing = Device Farm. CodePipeline orchestrates; CodeBuild/CodeDeploy execute (build/deploy).

Diagram of IaC, CI/CD, monitoring, and operations.
Build, deliver, monitor, operate

3.4.4Section summary

  • CI/CD = CodePipeline (orchestrate)/CodeBuild (build)/CodeDeploy (deploy)/CodeArtifact/CodeGuru
  • Observability = Managed Grafana/Managed Service for Prometheus; standardization = Proton; FE/testing = Amplify/Device Farm

Sign in to track progress — Log in.

Quick check

(just a quick review)

Q1. You want orchestration that chains build, test, and deploy stages automatically on source change. What?

Q2. You want to automate production deployments to EC2/ECS safely via blue-green or canary. What?

Q3. A platform team wants to define approved container/serverless templates and offer governed self-service to developers. What?

Check your understandingPractice questions for Chapter 3: Continuous Improvement for Existing Solutions