Table of contents
Why do we use Amazon Managed Service for Prometheus (AMP)
Amazon Managed Service for Prometheus (AMP) is a serverless, Prometheus-compatible monitoring service for container metrics. It securely monitors and alerts on container environments.
AMP is a solution for monitoring containers based on the popular Cloud Native Computing Foundation (CNCF) Prometheus project.
Amazon Managed Service for Prometheus reduces the heavy lifting required to get started with monitoring applications across Amazon Elastic Kubernetes Service and Amazon Elastic Container Service, as well as self-managed Kubernetes clusters.
Amazon Managed Service for Prometheus automatically scales as our monitoring needs grow. It offers highly available, multi-Availability Zone deployments, and integrates AWS security and compliance capabilities. Amazon Managed Service for Prometheus offers native support for the Prometheus query language (PromQL) as well as over 150+ Prometheus exporters (such as Java/JMX, Apache Kafka, and Redis) maintained by the open-source community.
Amazon Managed Service for Prometheus is powered by Cortex, an open-source CNCF project that adds horizontal scalability to ingest, store, query, and alert on Prometheus metrics.
Metrics ingested into a workspace are stored for 150 days and then automatically deleted.
Why should we use AMP?
We can use Amazon Managed Service for Prometheus if we want a service that is fully compatible with the Prometheus open-source project. We should also choose Amazon Managed Service for Prometheus if we are already running Prometheus and are looking to eliminate that ongoing operational cost while also improving security.
Amazon Managed Service for Prometheus (AMP) is specifically optimized for monitoring container-based workloads. Amazon Managed Service for Prometheus offers a Prometheus-compatible API for ingesting and querying your Prometheus metrics.
Amazon Managed Service for Prometheus is a metric-only service and does not collect logs or distributed trace data. We can export selected CloudWatch metrics to Amazon Managed Service for Prometheus to use PromQL as the common query language for querying and alarming on all your stored metrics.
Features
Highly secure, scalable, and available
AMP offers enterprise-ready security and compliance. AMP (Amazon Managed Service for Prometheus) includes built-in support for AWS Identity and Access Management (IAM).
With AWS PrivateLink, we can connect our VPCs to Amazon Managed Service for Prometheus and other services in AWS in a secure and scalable manner.
AMP manages the operational complexity of elastically scaling the ingestion, storage, and querying of metrics.
AMP is highly available and deployed in multiple AWS Regions and across Availability Zones, which are connected with low-latency, high-throughput, and highly redundant networking.
Cost-effective
Pay only for what we use. There are no upfront fees or commitments. We pay only for what we use based on metrics ingested, stored, and queried.
Easy to deploy and manage
We can create an Amazon Managed Service for Prometheus workspace, which is a Prometheus instance, with a few clicks in the AWS console.
Each AMP workspace is automatically deployed across multiple Availability Zones, and is immediately ready to ingest and query metrics. We can quickly enable metric collection in multiple ways.
We can configure AWS Distro for OpenTelemetry to collect metrics from a Prometheus-instrumented application, and send the metrics to Amazon Managed Service for Prometheus.
We can also ingest metrics from Prometheus servers in your Amazon EKS clusters and in self-managed Kubernetes clusters running on Amazon EC2.
Ingest and Collect
Amazon Managed Service for Prometheus includes a remote write-compatible API that can ingest metrics from OpenTelemetry, Prometheus libraries, and existing Prometheus servers.
Metrics can be ingested from any clusters running on AWS and hybrid environments, with on-demand scaling to meet your growing needs. Existing metric collectors such as the OpenTelemetry collector and the Prometheus server can be used to securely remote write Prometheus metrics to Amazon Managed Service for Prometheus from over 150+ third party Exporters such as Java/JMX, Apache Kafka, and Redis.
We can collect Prometheus metrics from Amazon EKS and Amazon ECS by using AWS Distro for OpenTelemetry (ADOT) or Prometheus servers as collection agents.
Monitor and Alert
AMP includes a query-compatible HTTP API that allows us to query metrics, metric labels, metric metadata, and time series metrics.
Tools such as Grafana, an open-source interactive visualization tool for time series data, are commonly used to query and visualize metrics from Prometheus.
Analyze
Prometheus provides a flexible query language called PromQL (Prometheus Query Language) to filter, aggregate, and alarm on metrics and quickly gain performance visibility without any code changes.
Supported Regions
Amazon Managed Service for Prometheus currently supports the following Regions:
• US East (Ohio)
• US East (N. Virginia)
• US West (Oregon)
• Asia Pacific (Singapore)
• Asia Pacific (Sydney)
• Asia Pacific (Tokyo)
• Europe (Frankfurt)
• Europe (Ireland)
• Europe (London)
• Europe (Stockholm)
References:
aws.amazon.com/prometheus/pricing
docs.aws.amazon.com/prometheus/latest/userg..
docs.aws.amazon.com/prometheus/latest/userg..
Hands-on Reference Links:
Create Workspace
catalog.workshops.aws/observability/en-US/a..
Ingest metrics from Amazon EKS
catalog.workshops.aws/observability/en-US/a..
Ingest metrics from Amazon ECS
catalog.workshops.aws/observability/en-US/a..
Configure Alert Manager
catalog.workshops.aws/observability/en-US/a..
Ingest cost metrics from Kubecost
catalog.workshops.aws/observability/en-US/a..
Community and Social Footprints :
Happy Learning 📚
Thank you!