Operations Management

Container Monitoring with Amazon Managed Service for Prometheus - Collecting and Analyzing EKS Metrics

Collect EKS/ECS metrics in a Prometheus-compatible format and query them with PromQL. Learn how to build a container monitoring platform integrated with Managed Grafana.

約 3 分で読めます

Overview of Managed Prometheus

Managed Service for Prometheus is a Prometheus-compatible managed monitoring service. It automates Prometheus server provisioning, scaling, storage management, and high-availability configuration, letting you focus on metrics collection and querying. You send metrics via the Prometheus remote write API and run queries with PromQL. Existing Prometheus exporters, Grafana dashboards, and alert rules can be migrated as-is.

Integration with EKS

The standard pattern for collecting metrics from EKS clusters is to deploy an ADOT (AWS Distro for OpenTelemetry) collector as a DaemonSet. The ADOT collector scrapes metrics from each node's kubelet, cAdvisor, and kube-state-metrics, then sends them to the Managed Prometheus remote write endpoint. IRSA (IAM Roles for Service Accounts) grants the ADOT collector write permissions to Managed Prometheus. If you are using Prometheus Operator, you can keep your ServiceMonitor and PodMonitor configurations as-is and simply change the remote write destination to Managed Prometheus to complete the migration.

PromQL and Alerting

Use PromQL to query collected metrics and build dashboards in Managed Grafana. In addition to standard Kubernetes metrics such as CPU usage, memory usage, pod restart counts, and request latency, you can also collect and visualize application-specific custom metrics. Alert Manager lets you define PromQL-based alert rules and send notifications to SNS topics. Metrics are retained for 150 days, making them useful for long-term capacity planning and trend analysis. For designing container monitoring operations, related books (Amazon) can be a helpful reference.

Managed Prometheus Pricing

Managed Prometheus pricing consists of metric ingestion, storage, and queries. Ingestion costs approximately $0.90 per 10 million samples for the first 2 billion samples/month. Storage costs approximately $0.03 per GB/month, with a 150-day retention period. Queries are billed based on samples processed, at approximately $0.10 per 10 million samples. Compared to self-hosted Prometheus servers, the managed service tends to have a lower total cost for medium and larger environments, since it eliminates EC2 instance operational costs and storage management overhead.

Summary

Managed Prometheus is a Prometheus-compatible managed monitoring service optimized for collecting metrics from container workloads. The standard integration pattern is to automatically collect metrics from EKS using the ADOT collector, query them with PromQL, and visualize them in Managed Grafana.

Related Services

Amazon Managed Service for PrometheusA Prometheus-compatible managed monitoring service for collecting, querying, and alerting on container metricsAmazon EKSA managed service for easily building and operating Kubernetes clusters on AWSAmazon Managed GrafanaA managed Grafana service for visualizing AWS data sources and building dashboards

Related Articles

Building a Unified Observability Dashboard with Amazon Managed GrafanaLearn how to build a multi-source observability dashboard by integrating CloudWatch, Prometheus, and OpenSearch data sources.Building a Service Mesh with AWS App Mesh - Controlling and Observing Microservice CommunicationLearn how to declaratively configure canary deployments, retry policies, and mTLS encryption using Envoy sidecars, and visualize service dependencies with X-Ray integration.Container-Optimized OS - Strengthening Container Host Security and Operations with BottlerocketLearn how to optimize container hosts with AWS Bottlerocket. Covers the minimal OS design, automatic updates, immutable infrastructure, and integration with ECS/EKS.

More on This Topic

How AWS Keeps Time Internally - Amazon Time Sync Service and Leap Second Smearing DesignLearn how Amazon Time Sync Service works, how GPS and atomic clocks provide high-precision time sources, the design decision to absorb leap seconds through smearing, and why time synchronization matters in distributed systems.Centralizing SaaS Audit Logs with AWS AppFabric - OCSF Standardization and Security Lake IntegrationLearn how AppFabric collects audit logs from SaaS applications, standardizes them to OCSF format, and builds analysis pipelines.Implementing Feature Flags with AWS AppConfig - Safe Configuration Deployment and RollbackRoll out configuration changes independently from code deployments using Linear and Exponential strategies. Ensure safety with automatic rollback triggered by CloudWatch alarms.Architecture Review - Systematically Evaluate Workloads with the AWS Well-Architected ToolLearn about architecture reviews using the AWS Well-Architected Tool. Covers evaluation based on the six pillars, improvement planning, and custom lens usage.Audit Log Design and Operations - Complete API Activity Recording with CloudTrailLearn how to design audit logs using AWS CloudTrail, including recording API activity, long-term storage in S3, and compliance automation through integration with AWS Config.Lessons from AWS Incident Reports (COE) - How Past Major Outages Shaped Design PrinciplesAnalyze the root causes of past major incidents including the S3 outage, us-east-1 DNS failure, and Kinesis outage from AWS's published Correction of Errors (COE) and incident reports, and explain how they changed AWS's design principles.Tag Design Determines Operations - Trivia and Practical Naming Conventions for AWS Resource Tagging StrategyWe explain why AWS resource tags are not just labels but the foundation for cost allocation, access control, and automation, covering tag key naming conventions, how to use the 50-tag limit, and governance through tag policies.Why AWS Service Quotas Exist - Multi-Tenant Design That Protects Shared InfrastructureExplain how AWS service quotas (formerly service limits) are not mere restrictions but a design to protect other customers in a multi-tenant environment, covering the noisy neighbor problem, soft vs hard limits, and what happens behind quota increase requests.

Similar Articles and Services

Amazon Managed GrafanaA fully managed Grafana service that integrates over 30 data sources including CloudWatch, Prometheus, and Timestream to build operational dashboardsBuilding a Unified Observability Dashboard with Amazon Managed GrafanaLearn how to build a multi-source observability dashboard by integrating CloudWatch, Prometheus, and OpenSearch data sources.The Integration Power of the AWS Observability Stack - Operational Transparency Through CloudWatch, X-Ray, and CloudTrailThis article examines the integration level of the AWS observability stack centered on CloudWatch, X-Ray, and CloudTrail, comparing it with Azure Monitor and GCP Cloud Logging to explain how the three pillars of metrics, traces, and logs drive differences in operational quality.