Amazon CloudWatch endpoints and quotas - AWS General Reference

Amazon CloudWatch endpoints and quotas

The following are the service endpoints and service quotas for this service. To connect programmatically to an AWS service, you use an endpoint. In addition to the standard AWS endpoints, some AWS services offer FIPS endpoints in selected Regions. For more information, see AWS service endpoints. Service quotas, also referred to as limits, are the maximum number of service resources or operations for your AWS account. For more information, see AWS service quotas.

Service Endpoints

Region Name Region Endpoint Protocol
US East (Ohio) us-east-2

monitoring.us-east-2.amazonaws.com

monitoring-fips.us-east-2.amazonaws.com

HTTP and HTTPS

HTTPS

US East (N. Virginia) us-east-1

monitoring.us-east-1.amazonaws.com

monitoring-fips.us-east-1.amazonaws.com

HTTP and HTTPS

HTTPS

US West (N. California) us-west-1

monitoring.us-west-1.amazonaws.com

monitoring-fips.us-west-1.amazonaws.com

HTTP and HTTPS

HTTPS

US West (Oregon) us-west-2

monitoring.us-west-2.amazonaws.com

monitoring-fips.us-west-2.amazonaws.com

HTTP and HTTPS

HTTPS

Africa (Cape Town) af-south-1 monitoring.af-south-1.amazonaws.com HTTP and HTTPS
Asia Pacific (Hong Kong) ap-east-1 monitoring.ap-east-1.amazonaws.com HTTP and HTTPS
Asia Pacific (Mumbai) ap-south-1 monitoring.ap-south-1.amazonaws.com HTTP and HTTPS
Asia Pacific (Osaka-Local) ap-northeast-3 monitoring.ap-northeast-3.amazonaws.com HTTP and HTTPS
Asia Pacific (Seoul) ap-northeast-2 monitoring.ap-northeast-2.amazonaws.com HTTP and HTTPS
Asia Pacific (Singapore) ap-southeast-1 monitoring.ap-southeast-1.amazonaws.com HTTP and HTTPS
Asia Pacific (Sydney) ap-southeast-2 monitoring.ap-southeast-2.amazonaws.com HTTP and HTTPS
Asia Pacific (Tokyo) ap-northeast-1 monitoring.ap-northeast-1.amazonaws.com HTTP and HTTPS
Canada (Central) ca-central-1 monitoring.ca-central-1.amazonaws.com HTTP and HTTPS
China (Beijing) cn-north-1 monitoring.cn-north-1.amazonaws.com.cn HTTP and HTTPS
China (Ningxia) cn-northwest-1 monitoring.cn-northwest-1.amazonaws.com.cn HTTP and HTTPS
Europe (Frankfurt) eu-central-1 monitoring.eu-central-1.amazonaws.com HTTP and HTTPS
Europe (Ireland) eu-west-1 monitoring.eu-west-1.amazonaws.com HTTP and HTTPS
Europe (London) eu-west-2 monitoring.eu-west-2.amazonaws.com HTTP and HTTPS
Europe (Milan) eu-south-1 monitoring.eu-south-1.amazonaws.com HTTP and HTTPS
Europe (Paris) eu-west-3 monitoring.eu-west-3.amazonaws.com HTTP and HTTPS
Europe (Stockholm) eu-north-1 monitoring.eu-north-1.amazonaws.com HTTP and HTTPS
Middle East (Bahrain) me-south-1 monitoring.me-south-1.amazonaws.com HTTP and HTTPS
South America (São Paulo) sa-east-1 monitoring.sa-east-1.amazonaws.com HTTP and HTTPS
AWS GovCloud (US-East) us-gov-east-1

monitoring.us-gov-east-1.amazonaws.com

monitoring.us-gov-east-1.amazonaws.com

HTTP and HTTPS

HTTPS

AWS GovCloud (US) us-gov-west-1

monitoring.us-gov-west-1.amazonaws.com

monitoring.us-gov-west-1.amazonaws.com

HTTP and HTTPS

HTTPS

Service Quotas

Resource Default Quota

Actions

5/alarm. This quota cannot be changed.

Alarms

10/month/customer for free. 5000 per Region, per account. You can request a quota increase.

Alarms based on metric math expressions can have up to 10 metrics.

Anomaly detection models

500 per Region, per account.

API requests

1,000,000/month/customer for free.

Canaries

100 per Region per account in the following Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Europe (Ireland), and Asia Pacific (Tokyo). 20 per Region per account in all other Regions.

You can request a quota increase.

Contributor Insights API requests

GetInsightRuleReport has a quota of 20 transactions per second (TPS), per Region. You can request a quota increase.

The following APIs have a quota of 1 TPS per Region. This quota cannot be changed.

Contributor Insights rules

100 rules per account.

You can request a quota increase.

Custom metrics

No quota.

Dashboards

Up to 500 metrics per dashboard widget. Up to 2500 metrics per dashboard, across all widgets.

These quotas include all metrics retrieved for use in metric math functions, even if those metrics are not displayed on the graph.

These quotas cannot be changed.

DescribeAlarms

9 transactions per second (TPS) per Region. The maximum number of operation requests you can make per second without being throttled.

You can request a quota increase.

DeleteAlarms request

DescribeAlarmHistory request

DescribeAlarmsForMetric request

DisableAlarmActions request

EnableAlarmActions request

SetAlarmState request

3 TPS per Region for each of these operations. The maximum number of operation requests you can make per second without being throttled.

These quotas cannot be changed.

DeleteDashboards request

GetDashboard request

ListDashboards request

PutDashboard request

10 TPS per Region for each of these operations. The maximum number of operation requests you can make per second without being throttled.

These quotas cannot be changed.

PutAnomalyDetector

DescribeAnomalyDetectors

10 TPS per Region. The maximum number of operation requests you can make per second without being throttled.

DeleteAnomalyDetector

5 TPS per Region. The maximum number of operation requests you can make per second without being throttled.

Dimensions

10/metric. This quota cannot be changed.

GetMetricData

50 TPS per Region. The maximum number of operation requests you can make per second without being throttled. You can request a quota increase.

180,000 Datapoints Per Second (DPS) if the StartTime used in the API request is less than or equal to three hours from current time. 396,000 DPS if the StartTime is more than three hours from current time. This is the maximum number of datapoints you can request per second using one or more API calls without being throttled. This quota cannot be changed.

The DPS is calculated based on estimated data points, not actual data points. The data point estimate is caculated using the requested time range, period, and retention period. This means that if the actual data points in the requested metrics are sparse or empty, throttling still occurs if the estimated data points exceed the quota. The DPS quota is per-Region.

GetMetricData

A single GetMetricData call can include as many as 500 MetricDataQuery structures.

This quota cannot be changed.

GetMetricStatistics

400 TPS per Region. The maximum number of operation requests you can make per second without being throttled.

You can request a quota increase.

GetMetricWidgetImage

Up to 500 metrics per image. This quota cannot be changed.

20 TPS per Region. The maximum number of operation requests you can make per second without being throttled. This quota cannot be changed.

ListMetrics

25 TPS per Region. The maximum number of operation requests you can make per second without being throttled.

You can request a quota increase.

Metric data storage

15 months. This quota cannot be changed.

Metric data values

The value of a metric data point must be within the range of -2^360 to 2^360. Special values (for example, NaN, +Infinity, -Infinity) are not supported. This quota cannot be changed.

MetricDatum items

20/PutMetricData request. A MetricDatum object can contain a single value or a StatisticSet object representing many values. This quota cannot be changed.

Metrics

10/month/customer for free.

Period

Maximum value is one day (86,400 seconds). This quota cannot be changed.

PutMetricAlarm request

3 TPS per Region. The maximum number of operation requests you can make per second without being throttled.

You can request a quota increase.

PutMetricData request

40 KB for HTTP POST requests. PutMetricData can handle 150 transactions per second (TPS), which is the maximum number of operation requests you can make per second without being throttled.

You can request a quota increase.

Amazon SNS email notifications

1,000/month/customer for free.

For more information, see CloudWatch Quotas in the Amazon CloudWatch User Guide.