Management and Governance
RecognitionAWS Managed Service for Prometheus
Explicit monitoring example, especially for container workloads, but not a standalone task.
Key points
- Managed Service for Prometheus supports Prometheus-compatible monitoring, especially for named container workloads.
Best-known use cases
- D1.1, D1.2, and D3.1: collect or query the stated Prometheus metrics for an ECS or EKS operational investigation.
What candidates often confuse it with
- Managed Service for Prometheus stores and queries Prometheus metrics; Managed Grafana visualizes supported sources and CloudWatch covers broader AWS telemetry.
Key takeaway
Use the Prometheus service when the workload and metric format require it, not as a generic dashboard answer.
Related services
- AWS Auto Scaling
- AWS CDK
- AWS CloudFormation
Relevant exam tasks
- D1.1 — Task 1.1: Implement metrics, alarms, and filters by using AWS monitoring and logging services.
- 1.1.1 — Use AWS services (for example, Amazon CloudWatch, AWS CloudTrail, Amazon Managed Service for Prometheus) to configure monitoring and logging for workloads (for example, serverless, compute, AI).
- D1.2 — Task 1.2: Identify and remediate issues by using monitoring and availability metrics.
- 1.2.1 — Analyze performance metrics and automate remediation strategies by using AWS services and functionality (for example, CloudWatch, Lambda, AWS Systems Manager, CloudTrail, Kiro, AWS DevOps Agent).
- D3.1 — Task 3.1: Provision and maintain cloud resources.
- 3.1.1 — Create and manage AMIs and container images (for example, EC2 Image Builder).