Amazon Prometheus Service

Name: Amazon Prometheus Service API
Brand: Amazon Prometheus Service
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring ObservabilityapiKey21 EndpointsREST

For Agents

Provision and manage Prometheus-compatible metric workspaces, alert manager definitions, and rule groups for cloud-native applications via 21 control-plane operations.

Connect the Amazon Prometheus Service to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amazon Prometheus Service, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Amazon Prometheus Service API.

Create and tag Prometheus workspaces that ingest remote-write metrics from EKS, ECS, or self-managed Kubernetes clusters

Define and update alert manager configurations to route firing alerts to receivers like Slack and PagerDuty

Manage rule group namespaces that hold recording and alerting rules evaluated server side

Toggle logging on a workspace to capture rules engine evaluation diagnostics in CloudWatch Logs

GET STARTED

Start building with Amazon Prometheus Service API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Amazon Prometheus Service, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Amazon Managed Service for Prometheus, keeping it validated and agent-ready. Amazon Managed Service for Prometheus (AMP) is a fully managed Prometheus-compatible monitoring service for container and Kubernetes workloads. The control-plane API exposes 21 operations covering workspaces, alert manager definitions, rule group namespaces, logging configuration, and resource tagging. Platform and SRE teams use it to provision metric stores at scale without operating their own Prometheus servers.

Use Cases

Patterns agents use Amazon Prometheus Service API for, with concrete tasks.

★ Multi-Tenant Kubernetes Monitoring

Platform teams use AMP to provide isolated Prometheus workspaces per tenant or environment without operating Prometheus servers. CreateWorkspace returns a remote-write endpoint that each cluster ships metrics to via Prometheus or the AWS Distro for OpenTelemetry. Tenants get isolated metric storage with shared infrastructure costs, and the workspace tag set is used for chargeback.

Call CreateWorkspace with alias=tenant-acme and tags including CostCenter, then return the prometheusEndpoint for the cluster's remote-write configuration

Centralised Alert Manager Configuration

SRE teams use PutAlertManagerDefinition to push a single alert manager YAML configuration to many workspaces, ensuring consistent routing of firing alerts to on-call channels. The definition is versioned per workspace, and DescribeAlertManagerDefinition lets a deploy pipeline diff the active definition against the desired state before applying changes.

Call PutAlertManagerDefinition with the YAML config Base64 encoded for the target workspace, then DescribeAlertManagerDefinition to confirm the new revision is active

Recording and Alerting Rule Lifecycle

Application teams ship recording rules and alerting rules to AMP through CreateRuleGroupsNamespace and UpdateRuleGroupsNamespace. Each namespace holds a set of rule groups defined in Prometheus YAML, and changes are evaluated server side as soon as they are applied. ListRuleGroupsNamespaces gives an inventory across a workspace for review and cleanup.

Call CreateRuleGroupsNamespace with name=app-rules and a Base64 encoded YAML body containing recording and alerting rules for the workspace

AI Agent Observability Provisioner

An AI agent invoked through Jentic provisions a fresh Prometheus workspace whenever a new tenant onboards. The agent searches Jentic for the create-workspace operation, executes it with the tenant's tags, and returns the resulting endpoint URL to the deployment pipeline. Jentic handles SigV4 signing so the agent never sees the raw access key id and secret.

Search Jentic for create amazon prometheus workspace, load the CreateWorkspace operation, execute it with the tenant alias and tags, and return the prometheusEndpoint

Key Endpoints

21 endpoints — jentic publishes the only available openapi specification for amazon managed service for prometheus, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/workspaces

Create a new Prometheus workspace

GET

/workspaces

List all Prometheus workspaces in the region

GET

/workspaces/{workspaceId}

Describe a workspace by id

PUT

/workspaces/{workspaceId}/alertmanager/definition

Put an alert manager definition for a workspace

POST

/workspaces/{workspaceId}/rulegroupsnamespaces

Create a rule group namespace inside a workspace

PUT

/workspaces/{workspaceId}/logging

Enable or update logging for a workspace

POST

/workspaces

Create a new Prometheus workspace

GET

/workspaces

List all Prometheus workspaces in the region

GET

/workspaces/{workspaceId}

Describe a workspace by id

PUT

/workspaces/{workspaceId}/alertmanager/definition

Put an alert manager definition for a workspace

POST

/workspaces/{workspaceId}/rulegroupsnamespaces

Create a rule group namespace inside a workspace

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS access key id and secret access key for AMP are stored encrypted in the Jentic vault. Jentic performs SigV4 signing for both control-plane and data-plane requests server side, so the agent never sees the raw secret access key.

Intent-based discovery

Agents search Jentic with phrases like create prometheus workspace or update alert manager definition, and Jentic returns the matching AMP operation with its input schema, so the agent does not have to map operation names to AWS path conventions.

Time to first call

Direct integration: 1 to 2 days including SigV4 signing, YAML Base64 encoding for rule groups and alert manager definitions, and IAM scoping. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Amazon API Gateway

API Gateway emits metrics that can be relayed into AMP for unified observability of public APIs

Use API Gateway alongside AMP when the agent is centralising metrics for HTTP APIs that should be alerted on the same way as cluster workloads.

Complementary

AWS Amplify

Amplify-hosted apps can ship custom metrics into an AMP workspace for production monitoring

Use Amplify alongside AMP when the agent owns both the application platform and its monitoring story.

Alternative

New Relic

Full observability platform with Prometheus remote-write support; choose when you also need APM and logs in one tool

Choose New Relic when the agent needs unified APM, logs, and metrics; choose AMP when the team is standardising on Prometheus tooling and wants AWS-native billing and IAM.

FAQs

Specific to using Amazon Prometheus Service API through Jentic.

Why is there no official OpenAPI spec for Amazon Managed Service for Prometheus?

AWS does not publish an OpenAPI specification for AMP; the official surface is the AWS SDKs and the Smithy model. Jentic generates and maintains this spec so that AI agents and developers can call Amazon Prometheus Service via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Amazon Managed Prometheus API use?

AMP uses AWS Signature Version 4 (SigV4) on the control plane, signed with an IAM access key id and secret access key. The data plane (remote-write and query) uses SigV4 too. Through Jentic the access key id and secret access key are stored encrypted in the vault and SigV4 signing is performed server side.

Can I push Prometheus rules with the Amazon Managed Prometheus API?

Yes. Use POST /workspaces/{workspaceId}/rulegroupsnamespaces with a Base64 encoded YAML body containing one or more rule groups. AMP evaluates the rules server side as soon as the namespace is created, and PUT updates an existing namespace in place.

What are the rate limits for the Amazon Managed Prometheus API?

AMP applies per-region throttling on control-plane operations like CreateWorkspace and PutAlertManagerDefinition; rates are higher for read operations like ListWorkspaces. Data-plane remote-write and query throttling depend on the workspace's active series and query rate. ThrottlingException should be retried with exponential backoff.

How do I create a workspace with the Amazon Managed Prometheus API through Jentic?

Install the SDK with pip install jentic, search Jentic for create amazon prometheus workspace, load the CreateWorkspace operation schema, and execute it with an alias and tags. Jentic handles SigV4 signing and returns the workspace id and remote-write endpoint URL.

Can I delete a workspace and recover its metrics later?

No. DeleteWorkspace permanently removes the workspace and all stored metrics; there is no undelete. Before deletion, snapshot any required dashboards or export metrics through the query API. AMP retains metrics for the workspace's configured retention period only while the workspace exists.