Amazon Managed Service for Prometheus service quotas
The following two sections describe the quotas and limits associated with Amazon Managed Service for Prometheus.
Service quotas
Amazon Managed Service for Prometheus has the following quotas. Amazon Managed Service for Prometheus vends CloudWatch usage metrics to monitor Prometheus resource usage. Using the CloudWatch usage metrics alarm feature, you can monitor Prometheus resources and usage to prevent limit errors.
As your projects and workspaces grow, the most common quotas that you may need to monitor or request an increase for are: Active series per workspace, Ingestion rate per workspace, and Ingestion burst size per workspace.
For all adjustable quotas, you can request a quota increase by selecting the link
in the Adjustable column, or by requesting a
quota increase
Note
Unless otherwise noted, these quotas are per workspace.
| Name | Default | Adjustable | Description |
|---|---|---|---|
| Active alert payload size per alert manager | Each supported Region: 20 Megabytes | No | The maximum active alert payload size of all alerts per alert manager. Alert size is dependent on labels and annotations. |
| Active alerts per alert manager | Each supported Region: 1,000 |
Yes |
The maximum number of active alerts per alert manager. |
| Active metrics with metadata per workspace | Each supported Region: 20,000 | No | The number of unique active metrics with metadata per workspace. |
| Active series per workspace | Each supported Region: 10,000,000 per 2 hours |
Yes |
The number of unique active series per workspace. A series is active if a sample has been reported in the past 2 hours. Capacity from 2M to 10M is automatically adjusted based on the last 30 min of usage. |
| Alert aggregation group size in alert manager definition file | Each supported Region: 1,000 |
Yes |
The maximum size of an alert aggregation group in alert manager definition file. Each label value combination of group_by would create an aggregation group. |
| Alert manager definition file size | Each supported Region: 1 Megabytes | No | The maximum size of an alert manager definition file. |
| HA tracker clusters | Each supported Region: 500 | No | The maximum number of clusters that HA tracker will keep track of for ingested samples per workspace. |
| Ingestion burst size per workspace | Each supported Region: 1,000,000 |
Yes |
The maximum number samples that could be ingested per workspace in one burst per second. |
| Ingestion rate per workspace | Each supported Region: 170,000 |
Yes |
Metric sample ingestion rate per workspace per second. |
| Inhibition rules in alert manager definition file | Each supported Region: 100 |
Yes |
The maximum number of inhibition rules in alert manager definition file. |
| Label size | Each supported Region: 7 Kilobytes | No | The maximum combined size of all labels and label values accepted for a series. |
| Labels per metric series | Each supported Region: 70 |
Yes |
Number of labels per metric series. |
| Metadata length | Each supported Region: 1 Kilobytes | No | The maximum length accepted for metric metadata. Metadata refers to Metric Name, HELP and UNIT. |
| Metadata per metric | Each supported Region: 10 | No | The number of metadata per metric. |
| Nodes in alert manager routing tree | Each supported Region: 100 |
Yes |
The maximum number of nodes in the alert manager routing tree. |
| Number of API operations in transactions per second | Each supported Region: 10 |
Yes |
The maximum number of API operations per second per region. This includes workspace CRUD APIs, tagging APIs, rule groups namespace CRUD APIs, and alert manager definition CRUD APIs. |
| Query bytes for instant queries | Each supported Region: 5 Gigabytes | No | The maximum bytes that can be scanned by a single instant query. |
| Query bytes for range queries | Each supported Region: 5 Gigabytes | No | The maximum bytes that can be scanned per 24-hour interval in a single range query. |
| Query chunks fetched | Each supported Region: 20,000,000 | No | The maximum number of chunks that can be scanned during a single query. |
| Query samples | Each supported Region: 50,000,000 | No | The maximum number of samples that can be scanned during a single query. |
| Query series fetched | Each supported Region: 12,000,000 | No | The maximum number of series that can be scanned during a single query. |
| Query time range in days | Each supported Region: 32 | No | The maximum time range of any PromQL query. |
| Request size | Each supported Region: 1 Megabytes | No | The maximum request size for ingestion or query. |
| Retention time for ingested data in days | Each supported Region: 150 |
Yes |
The number of days that data in a workspace is retained. Data older than this is deleted. You may request quota changes to increase or decrease this value. |
| Rule evaluation interval | Each supported Region: 30 Seconds |
Yes |
The minimum rule evaluation interval of a rule group per workspace. |
| Rule group namespace definition file size | Each supported Region: 1 Megabytes | No | The maximum size of a rule group namespace definition file. |
| Rules per workspace | Each supported Region: 2,000 |
Yes |
The maximum number of rules per workspace. |
| Templates in alert manager definition file | Each supported Region: 100 |
Yes |
The maximum number of templates in the alert manager definition file. |
| Workspaces per region per account | Each supported Region: 25 |
Yes |
The maximum number of workspaces per region. |
Active series default
Amazon Managed Service for Prometheus allows you to use up to your quota of active time series by default.
Amazon Managed Service for Prometheus workspaces automatically adapt to your ingestion volume. As your usage increases, Amazon Managed Service for Prometheus will automatically increase your time series capacity to double your baseline usage, up to the default quota. For example, if your average active time series for the last 30 minutes is 3.5 million, you can use up to 7 million time series without throttling.
If you need more than double your previous baseline, Amazon Managed Service for Prometheus automatically allocates more capacity as your ingest volume increases, to help ensure your workload does not experience sustained throttling, up to your quota. However, throttling can occur if you exceed double your previous baseline computed over the last 30 minutes. To avoid throttling, Amazon Managed Service for Prometheus recommends gradually increasing ingestion when increasing to more than double your previous active time series.
Note
The minimum capacity for active time series is 2 million, there is no throttling when you have less than 2 million series.
To go beyond your default quota, you can request a quota increase.
Additional limits on ingested data
Amazon Managed Service for Prometheus also has the following additional requirements for data ingested into the workspace. These are not adjustable.
-
Metric samples older than 1 hour are refused from being ingested.
-
Every sample and metadata must have a metric name.
