Amazon Managed Service for Prometheus

What it is

Amazon Managed Service for Prometheus is a serverless, Prometheus-compatible monitoring service for container metrics. It uses the same open-source Prometheus data model and PromQL query language, but AWS scales ingestion, storage, and querying for you and runs it across multiple AZ (Availability Zone)An isolated location within an AWS Region, made up of one or more data centers with their own power, cooling, and networking. The AZs in a Region are linked by fast, low-latency connections, so spreading resources across them protects against the failure of one site.Glossary entry: data in a workspace is replicated across three Availability Zones.

Choose it when a question mentions Prometheus, PromQL, or monitoring Kubernetes or EKS metrics without running Prometheus servers yourself. It works with Amazon EKS and self-managed Kubernetes clusters.

Concepts

Workspace: a logical space dedicated to storing and querying Prometheus metrics.
Ingesting metrics:
- AWS managed collectors scrape metrics from EKS clusters without running your own agents.
- Alternatively, send metrics from your own Prometheus server or an OpenTelemetry collector using remote write.
Querying: use PromQL, for example from Amazon Managed Grafana dashboards.
Rules: recording rules precompute queries, and alerting rules fire alerts.
Alert manager: groups, routes, silences, and inhibits alerts. It sends notifications to Amazon SNS topics in the same account, and from there to email, chat, or other tools.

Security, resilience, performance, and cost

Security: integrates with AWS security services; access is controlled with IAM, and requests can stay private through VPC endpointA private connection from a VPC to an AWS service or another endpoint service without crossing the internet. Gateway endpoints, for Amazon S3 and DynamoDB, are route table targets; interface endpoints are network interfaces that use AWS PrivateLink.Glossary entry.
Resilience: Multi-AZRunning standby or extra copies of a resource in other Availability Zones so that it survives the loss of one. An Amazon RDS Multi-AZ deployment keeps one or two standby copies and fails over to one automatically.Glossary entry by design, with data replicated across three Availability Zones.
Performance: scales automatically with the number of metrics.
Cost: no upfront fees; pay for metrics ingested, queried, stored, and collected.

Managed Prometheus or another option?

If the requirement is	Choose
Prometheus metrics and PromQL without managing servers	Amazon Managed Service for Prometheus
Dashboards over Prometheus and other sources	Amazon Managed Grafana
AWS service metrics, logs, and alarms	Amazon CloudWatch
Container metrics in CloudWatch	CloudWatch Container Insights

Reverse mindmap: when the question points here

Is it Amazon Managed Service for Prometheus?

Yes, when the question says
- Managed Prometheus for EKS or Kubernetes leads to Managed Service for Prometheus
- Keep using PromQL without running servers leads to Managed Service for Prometheus
Choose the feature
- Scrape EKS metrics with no agents to manage leads to AWS managed collector
- Send from our own Prometheus leads to Remote write
- Alert on a PromQL expression leads to Alerting rules and alert manager
- Notify a team leads to Alert manager to SNS
- Visualize the metrics leads to Managed Grafana
No, when the question says
- Native AWS metrics and alarms leads to CloudWatch

Key takeaways

Managed Service for Prometheus is serverless and Prometheus-compatible, for container metrics, especially EKS.
Data is replicated across three Availability Zones; ingestion, storage, and queries scale automatically.
Ingest with AWS managed collectors or remote write; query with PromQL; alert through alert manager to SNS.
Pair it with Managed Grafana for dashboards; pay for metrics ingested, queried, stored, and collected.