CloudWatch Logs quotas
You can use the table in this section to review the default service quotas, also referred to as limits, for an AWS account in Amazon CloudWatch Logs. Most of the service quotas, but not all, are listed under the Amazon CloudWatch Logs namespace in the Service Quotas console.
Note
If you want to request a quota increase for any of these quotas, see the procedure in this section.
| Resource | Default quota |
|---|---|
|
Account-level policies |
One account-level subscription filter policy per Region per account. One account-level data protection policy per Region per account. 20 account-level field index policies per account. The log group name prefixes that they apply to can't overlap. These quotas can't be changed. |
|
Anomaly detectors |
500 anomaly detectors per account. You can request a quota increase. |
|
Batch size |
The maximum batch size is 1,048,576 bytes. This size is calculated as the sum of all event messages in UTF-8, plus 26 bytes for each log event. This quota can't be changed. |
|
Data archiving |
Up to 5 GB of data archiving for free. This quota can't be changed. |
|
10 transactions per second (TPS/account/Region), after which transactions are throttled. You can request a quota increase. |
|
|
50 transactions per second (TPS/account/Region), after which transactions are throttled. You can request a quota increase. |
|
Custom data identifiers |
Each data protection policy can include up to 10 custom data identifiers. You can request a quota increase. Each regular expression that defines a custom data identifier can include up to 200 characters. This quota can't be changed. |
|
10 transactions per second (TPS/account/Region), after which transactions are throttled. You can request a quota increase. |
|
|
15 transactions per second (TPS/account/Region), after which transactions are throttled. You can request a quota increase. |
|
|
10 transactions per second (TPS/account/Region). You can request a quota increase. |
|
|
25 transactions per second (TPS/account/Region). You can request a quota increase. |
|
|
Discovered log fields |
CloudWatch Logs Insights can discover a maximum of 1000 log event fields in a log group. This quota can't be changed. For more information, see Supported logs and discovered fields. |
|
Extracted log fields in JSON logs |
CloudWatch Logs Insights can extract a maximum of 200 log event fields from a JSON log. This quota can't be changed. For more information, see Supported logs and discovered fields. |
|
Export task |
One active (running or pending) export task at a time, per account. This quota can't be changed. |
|
Field indexes |
As many as 20 indexed fields per policy. This quota can't be changed. |
|
25 requests per second in US East (N. Virginia). 5 requests per second in the following Regions:
10 requests per second in other Regions. This quota can't be changed. |
|
|
30 requests per second in Europe (Paris). 10 requests per second in the following Regions:
25 requests per second in all other Regions. This quota can't be changed. We recommend subscriptions if you are continuously processing new data. If you need historical data, we recommend exporting your data to Amazon S3. |
|
|
Incoming data |
Up to 5 GB of incoming data for free. This quota can't be changed. |
|
Live Tail concurrent sessions. |
15 concurrent sessions. You can request a quota increase. |
|
Live Tail: log groups searched in one session. |
Maximum of 10 log groups scanned in one Live Tail session. This quota can't be changed. |
|
Log event size |
256 KB (maximum). This quota can't be changed. |
|
Log groups |
1,000,000 log groups per account per Region. You can request a quota increase. There is no quota on the number of log streams that can belong to one log group. |
|
Metrics filters |
100 per log group. This quota can't be changed. |
|
Embedded metric format metrics |
100 metrics per log event and 30 dimensions per metric. For more information about the embedded metric format, see Specification: Embedded Metric Format in the Amazon CloudWatch User Guide. |
|
The maximum batch size of a PutLogEvents request is 1MB. This size is calculated as the sum of all event messages in UTF-8, plus 26 bytes for each log event. 5000 transactions per second per account per Region You can request an increase to the per-second throttling quota by using the Service Quotas service. |
|
|
Query execution timeout |
Queries in CloudWatch Logs Insights time out after 60 minutes. This time limit can't be changed. |
|
Queried log groups |
A maximum of 50 log groups can be queried in a single CloudWatch Logs Insights query, when you specify log groups individually. This quota can't be changed. If you use log group criteria to choose log groups based on their name prefixes, or select to query "all log groups", you can query up to 10,000 log groups in a single query. |
|
Query concurrency |
For Standard class log groups, a maximum of 30 concurrent CloudWatch Logs Insights queries, including queries that have been added to dashboards. This maximum of 30 applies to the total number of concurrent queries, no matter the query language used. Only 15 of these concurrent queries can be in OpenSearch Service PPL and/or OpenSearch Service SQL. For Infrequent Access class log groups, a maximum of 5 concurrent CloudWatch Logs Insights queries, including queries that have been added to dashboards. These quotas can't be changed. |
|
Queries generated from natural language |
As many as five concurrent natural-language generated query requests. |
|
Query availability |
Queries constructed in the console are available for 30 days, via the History command. This availability period can't be changed. Query definitions created by using PutQueryDefinition do not expire. |
|
Query results availability |
Results from a query are retrievable for 7 days. This availability time can't be changed. |
|
Query results displayed in console |
Up to to 10,000 rows of query results are displayed on the console. |
|
Regular expressions |
Up to 5 filter patterns containing regular expressions for each log group when creating metric filters or subscription filters. This quota can't be changed. Up to 2 regular expressions for each filter pattern, when creating a delimited or JSON filter pattern for metric filters and subscription filters or when filtering log events. |
|
Resource policies |
Up to 10 CloudWatch Logs resource policies per Region per account. This quota can't be changed. |
|
Saved queries |
You can save as many as 1000 CloudWatch Logs Insights queries, per Region per account. This quota can't be changed. |
|
Subscription filters |
2 per log group. This quota can't be changed. |
|
Transformers |
A log transformer can have a maximum of 5 parser-type processors. It can have a maximum of 20 processors overall. Each log group can have only one log-group level transformer. Each account can have as many as 20 account-level transformers. None of these transformers can apply to identical or overlapping log group prefixes. None of these quotas can be changed. |
Managing your CloudWatch Logs service quotas
CloudWatch Logs has integrated with Service Quotas, an AWS service that enables you to view and manage your quotas from a central location. For more information, see What Is Service Quotas? in the Service Quotas User Guide.
Service Quotas makes it easy to look up the value of your CloudWatch Logs service quotas.
