aws / aws/aws-cdk

📊Tracking: Amazon Managed Service for Prometheus

Open
#14,353 4 comments 103 reactions 0 assignees View on GitHub
feature-request management/tracking p1
Dominant language
TypeScript
Stars
12.9k
Forks
4.6k
Avg merge
2d 3h
Merged PRs (30d)
83

Description

Add your +1 👍 to help us prioritize high-level constructs for this service
---

### Overview:

Amazon Managed Service for Prometheus (AMP) is a Prometheus-compatible monitoring service that makes it easy to monitor containerized applications at scale. The Cloud Native Computing Foundation’s Prometheus project is a popular open source monitoring and alerting solution optimized for container environments. With AMP, you can use the open source Prometheus query language (PromQL) to monitor the performance of containerized workloads without having to manage the underlying infrastructure required to manage the ingestion, storage, and querying of operational metrics. AMP automatically scales as your workloads grow or shrink, and is integrated with AWS security services to enable fast and secure access to data. You can collect Prometheus metrics from Amazon Elastic Kubernetes Service (Amazon EKS) and Amazon Elastic Container Service (Amazon ECS) environments, using AWS Distro for OpenTelemetry or Prometheus servers as collection agents.

[AWS Docs](https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-getting-started.html)

### Maturity: CloudFormation resources needed

See the [AWS Construct Library Module Lifecycle doc](https://github.com/aws/aws-cdk-rfcs/blob/master/text/0107-construct-library-module-lifecycle.md) for more information about maturity levels.

### Implementation:

See the [CDK API Reference](url) for more implementation details.

### Issue list:

---
This is a 📊Tracking Issue

Contributor guide

Open the contributing guide

Research direction

Start with the linked AWS Docs and the AWS Construct Library Module Lifecycle document, then review the intended CDK API reference once its placeholder URL is replaced. This tracking issue names no files or tests and does not define concrete constructs, use cases, or completion criteria, so the implementation scope must be established before work can begin.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, prometheus
Domain
cloud, infrastructure, observability-sre
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.