amazonaws.com – logs
You can use Amazon CloudWatch Logs to monitor, store, and access your log files from EC2 instances, CloudTrail, and other sources. You can then retrieve the associated log data from CloudWatch Logs using the CloudWatch console. Alternatively, you can use CloudWatch Logs commands in the Amazon Web Services CLI, CloudWatch Logs API, or CloudWatch Logs SDK.
You can use CloudWatch Logs to:
-
Monitor logs from EC2 instances in real time: You can use CloudWatch Logs to monitor applications and systems using log data. For example, CloudWatch Logs can track the number of errors that occur in your application logs. Then, it can send you a notification whenever the rate of errors exceeds a threshold that you specify. CloudWatch Logs uses your log data for monitoring so no code changes are required. For example, you can monitor application logs for specific literal terms (such as "NullReferenceException"). You can also count the number of occurrences of a literal term at a particular position in log data (such as "404" status codes in an Apache access log). When the term you are searching for is found, CloudWatch Logs reports the data to a CloudWatch metric that you specify.
-
Monitor CloudTrail logged events: You can create alarms in CloudWatch and receive notifications of particular API activity as captured by CloudTrail. You can use the notification to perform troubleshooting.
-
Archive log data: You can use CloudWatch Logs to store your log data in highly durable storage. You can change the log retention setting so that any log events earlier than this setting are automatically deleted. The CloudWatch Logs agent helps to quickly send both rotated and non-rotated log data off of a host and into the log service. You can then access the raw log data when you need it.
- Homepage
- https://api.apis.guru/v2/specs/amazonaws.com:logs/2014-03-28.json
- Provider
- amazonaws.com:logs / logs
- OpenAPI version
- 3.0.0
- Spec (JSON)
- https://api.apis.guru/v2/specs/amazonaws.com/logs/2014-03-28/openapi.json
- Spec (YAML)
- https://api.apis.guru/v2/specs/amazonaws.com/logs/2014-03-28/openapi.yaml
Tools (50)
Extracted live via the executor SDK.
-
xAmzTargetLogs20140328AssociateKmsKey.associateKmsKeyAssociates the specified KMS key with the specified log group.
Associating a KMS key with a log group overrides any existing associations between the log group and a KMS key. After a KMS key is associated with a log group, all newly ingested data for the log group is encrypted using the KMS key. This association is stored as long as the data encrypted with the KMS keyis still within CloudWatch Logs. This enables CloudWatch Logs to decrypt this data whenever it is requested.
CloudWatch Logs supports only symmetric KMS keys. Do not use an associate an asymmetric KMS key with your log group. For more information, see .
It can take up to 5 minutes for this operation to take effect.
If you attempt to associate a KMS key with a log group but the KMS key does not exist or the KMS key is disabled, you receive an
InvalidParameterExceptionerror. -
xAmzTargetLogs20140328CancelExportTask.cancelExportTaskCancels the specified export task.
The task must be in the
PENDINGorRUNNINGstate. -
xAmzTargetLogs20140328CreateExportTask.createExportTaskCreates an export task so that you can efficiently export data from a log group to an Amazon S3 bucket. When you perform a
CreateExportTaskoperation, you must use credentials that have permission to write to the S3 bucket that you specify as the destination.Exporting log data to S3 buckets that are encrypted by KMS is supported. Exporting log data to Amazon S3 buckets that have S3 Object Lock enabled with a retention period is also supported.
Exporting to S3 buckets that are encrypted with AES-256 is supported.
This is an asynchronous call. If all the required information is provided, this operation initiates an export task and responds with the ID of the task. After the task has started, you can use to get the status of the export task. Each account can only have one active (
RUNNINGorPENDING) export task at a time. To cancel an export task, use .You can export logs from multiple log groups or multiple time ranges to the same S3 bucket. To separate log data for each export task, specify a prefix to be used as the Amazon S3 key prefix for all exported objects.
Time-based sorting on chunks of log data inside an exported file is not guaranteed. You can sort the exported log field data by using Linux utilities.
-
xAmzTargetLogs20140328CreateLogGroup.createLogGroupCreates a log group with the specified name. You can create up to 20,000 log groups per account.
You must use the following guidelines when naming a log group:
-
Log group names must be unique within a Region for an Amazon Web Services account.
-
Log group names can be between 1 and 512 characters long.
-
Log group names consist of the following characters: a-z, A-Z, 0-9, '_' (underscore), '-' (hyphen), '/' (forward slash), '.' (period), and '#' (number sign)
When you create a log group, by default the log events in the log group do not expire. To set a retention policy so that events expire and are deleted after a specified time, use .
If you associate an KMS key with the log group, ingested data is encrypted using the KMS key. This association is stored as long as the data encrypted with the KMS key is still within CloudWatch Logs. This enables CloudWatch Logs to decrypt this data whenever it is requested.
If you attempt to associate a KMS key with the log group but the KMS keydoes not exist or the KMS key is disabled, you receive an
InvalidParameterExceptionerror.CloudWatch Logs supports only symmetric KMS keys. Do not associate an asymmetric KMS key with your log group. For more information, see .
_ -
-
xAmzTargetLogs20140328CreateLogStream.createLogStreamCreates a log stream for the specified log group. A log stream is a sequence of log events that originate from a single source, such as an application instance or a resource that is being monitored.
There is no limit on the number of log streams that you can create for a log group. There is a limit of 50 TPS on
CreateLogStreamoperations, after which transactions are throttled.You must use the following guidelines when naming a log stream:
-
Log stream names must be unique within the log group.
-
Log stream names can be between 1 and 512 characters long.
-
Don't use ':' (colon) or '*' (asterisk) characters.
-
-
xAmzTargetLogs20140328DeleteDataProtectionPolicy.deleteDataProtectionPolicyDeletes the data protection policy from the specified log group.
For more information about data protection policies, see .
-
xAmzTargetLogs20140328DeleteDestination.deleteDestinationDeletes the specified destination, and eventually disables all the subscription filters that publish to it. This operation does not delete the physical resource encapsulated by the destination.
-
xAmzTargetLogs20140328DeleteLogGroup.deleteLogGroupDeletes the specified log group and permanently deletes all the archived log events associated with the log group.
-
xAmzTargetLogs20140328DeleteLogStream.deleteLogStreamDeletes the specified log stream and permanently deletes all the archived log events associated with the log stream.
-
xAmzTargetLogs20140328DeleteMetricFilter.deleteMetricFilterDeletes the specified metric filter.
-
xAmzTargetLogs20140328DeleteQueryDefinition.deleteQueryDefinitionDeletes a saved CloudWatch Logs Insights query definition. A query definition contains details about a saved CloudWatch Logs Insights query.
Each
DeleteQueryDefinitionoperation can delete one query definition.You must have the
logs:DeleteQueryDefinitionpermission to be able to perform this operation. -
xAmzTargetLogs20140328DeleteResourcePolicy.deleteResourcePolicyDeletes a resource policy from this account. This revokes the access of the identities in that policy to put log events to this account.
-
xAmzTargetLogs20140328DeleteRetentionPolicy.deleteRetentionPolicyDeletes the specified retention policy.
Log events do not expire if they belong to log groups without a retention policy.
-
xAmzTargetLogs20140328DeleteSubscriptionFilter.deleteSubscriptionFilterDeletes the specified subscription filter.
-
xAmzTargetLogs20140328DescribeDestinations.describeDestinationsLists all your destinations. The results are ASCII-sorted by destination name.
-
xAmzTargetLogs20140328DescribeExportTasks.describeExportTasksLists the specified export tasks. You can list all your export tasks or filter the results based on task ID or task status.
-
xAmzTargetLogs20140328DescribeLogGroups.describeLogGroupsLists the specified log groups. You can list all your log groups or filter the results by prefix. The results are ASCII-sorted by log group name.
CloudWatch Logs doesn’t support IAM policies that control access to the
DescribeLogGroupsaction by using theaws:ResourceTag/key-namecondition key. Other CloudWatch Logs actions do support the use of theaws:ResourceTag/key-namecondition key to control access. For more information about using tags to control access, see .If you are using CloudWatch cross-account observability, you can use this operation in a monitoring account and view data from the linked source accounts. For more information, see .
-
xAmzTargetLogs20140328DescribeLogStreams.describeLogStreamsLists the log streams for the specified log group. You can list all the log streams or filter the results by prefix. You can also control how the results are ordered.
You can specify the log group to search by using either
logGroupIdentifierorlogGroupName. You must include one of these two parameters, but you can't include both.This operation has a limit of five transactions per second, after which transactions are throttled.
If you are using CloudWatch cross-account observability, you can use this operation in a monitoring account and view data from the linked source accounts. For more information, see .
-
xAmzTargetLogs20140328DescribeMetricFilters.describeMetricFiltersLists the specified metric filters. You can list all of the metric filters or filter the results by log name, prefix, metric name, or metric namespace. The results are ASCII-sorted by filter name.
-
xAmzTargetLogs20140328DescribeQueries.describeQueriesReturns a list of CloudWatch Logs Insights queries that are scheduled, running, or have been run recently in this account. You can request all queries or limit it to queries of a specific log group or queries with a certain status.
-
xAmzTargetLogs20140328DescribeQueryDefinitions.describeQueryDefinitionsThis operation returns a paginated list of your saved CloudWatch Logs Insights query definitions.
You can use the
queryDefinitionNamePrefixparameter to limit the results to only the query definitions that have names that start with a certain string. -
xAmzTargetLogs20140328DescribeResourcePolicies.describeResourcePoliciesLists the resource policies in this account.
-
xAmzTargetLogs20140328DescribeSubscriptionFilters.describeSubscriptionFiltersLists the subscription filters for the specified log group. You can list all the subscription filters or filter the results by prefix. The results are ASCII-sorted by filter name.
-
xAmzTargetLogs20140328DisassociateKmsKey.disassociateKmsKeyDisassociates the associated KMS key from the specified log group.
After the KMS key is disassociated from the log group, CloudWatch Logs stops encrypting newly ingested data for the log group. All previously ingested data remains encrypted, and CloudWatch Logs requires permissions for the KMS key whenever the encrypted data is requested.
Note that it can take up to 5 minutes for this operation to take effect.
-
xAmzTargetLogs20140328FilterLogEvents.filterLogEventsLists log events from the specified log group. You can list all the log events or filter the results using a filter pattern, a time range, and the name of the log stream.
You must have the
logs;FilterLogEventspermission to perform this operation.You can specify the log group to search by using either
logGroupIdentifierorlogGroupName. You must include one of these two parameters, but you can't include both.By default, this operation returns as many log events as can fit in 1 MB (up to 10,000 log events) or all the events found within the specified time range. If the results include a token, that means there are more log events available. You can get additional results by specifying the token in a subsequent call. This operation can return empty results while there are more log events available through the token.
The returned log events are sorted by event timestamp, the timestamp when the event was ingested by CloudWatch Logs, and the ID of the
PutLogEventsrequest.If you are using CloudWatch cross-account observability, you can use this operation in a monitoring account and view data from the linked source accounts. For more information, see .
-
xAmzTargetLogs20140328GetDataProtectionPolicy.getDataProtectionPolicyReturns information about a log group data protection policy.
-
xAmzTargetLogs20140328GetLogEvents.getLogEventsLists log events from the specified log stream. You can list all of the log events or filter using a time range.
By default, this operation returns as many log events as can fit in a response size of 1MB (up to 10,000 log events). You can get additional log events by specifying one of the tokens in a subsequent call. This operation can return empty results while there are more log events available through the token.
If you are using CloudWatch cross-account observability, you can use this operation in a monitoring account and view data from the linked source accounts. For more information, see .
You can specify the log group to search by using either
logGroupIdentifierorlogGroupName. You must include one of these two parameters, but you can't include both. -
xAmzTargetLogs20140328GetLogGroupFields.getLogGroupFieldsReturns a list of the fields that are included in log events in the specified log group. Includes the percentage of log events that contain each field. The search is limited to a time period that you specify.
You can specify the log group to search by using either
logGroupIdentifierorlogGroupName. You must specify one of these parameters, but you can't specify both.In the results, fields that start with
@are fields generated by CloudWatch Logs. For example,@timestampis the timestamp of each log event. For more information about the fields that are generated by CloudWatch logs, see .The response results are sorted by the frequency percentage, starting with the highest percentage.
If you are using CloudWatch cross-account observability, you can use this operation in a monitoring account and view data from the linked source accounts. For more information, see .
-
xAmzTargetLogs20140328GetLogRecord.getLogRecordRetrieves all of the fields and values of a single log event. All fields are retrieved, even if the original query that produced the
logRecordPointerretrieved only a subset of fields. Fields are returned as field name/field value pairs.The full unparsed log event is returned within
@message. -
xAmzTargetLogs20140328GetQueryResults.getQueryResultsReturns the results from the specified query.
Only the fields requested in the query are returned, along with a
@ptrfield, which is the identifier for the log record. You can use the value of@ptrin a operation to get the full log record.GetQueryResultsdoes not start running a query. To run a query, use .If the value of the
Statusfield in the output isRunning, this operation returns only partial results. If you see a value ofScheduledorRunningfor the status, you can retry the operation later to see the final results.If you are using CloudWatch cross-account observability, you can use this operation in a monitoring account to start queries in linked source accounts. For more information, see .
-
xAmzTargetLogs20140328ListTagsForResource.listTagsForResourceDisplays the tags associated with a CloudWatch Logs resource. Currently, log groups and destinations support tagging.
-
xAmzTargetLogs20140328ListTagsLogGroup.listTagsLogGroupThe ListTagsLogGroup operation is on the path to deprecation. We recommend that you use instead.
Lists the tags for the specified log group.
-
xAmzTargetLogs20140328PutDataProtectionPolicy.putDataProtectionPolicyCreates a data protection policy for the specified log group. A data protection policy can help safeguard sensitive data that's ingested by the log group by auditing and masking the sensitive log data.
Sensitive data is detected and masked when it is ingested into the log group. When you set a data protection policy, log events ingested into the log group before that time are not masked.
By default, when a user views a log event that includes masked data, the sensitive data is replaced by asterisks. A user who has the
logs:Unmaskpermission can use a or operation with theunmaskparameter set totrueto view the unmasked log events. Users with thelogs:Unmaskcan also view unmasked data in the CloudWatch Logs console by running a CloudWatch Logs Insights query with theunmaskquery command.For more information, including a list of types of data that can be audited and masked, see .
-
xAmzTargetLogs20140328PutDestination.putDestinationCreates or updates a destination. This operation is used only to create destinations for cross-account subscriptions.
A destination encapsulates a physical resource (such as an Amazon Kinesis stream). With a destination, you can subscribe to a real-time stream of log events for a different account, ingested using .
Through an access policy, a destination controls what is written to it. By default,
PutDestinationdoes not set any access policy with the destination, which means a cross-account user cannot call against this destination. To enable this, the destination owner must call afterPutDestination.To perform a
PutDestinationoperation, you must also have theiam:PassRolepermission. -
xAmzTargetLogs20140328PutDestinationPolicy.putDestinationPolicyCreates or updates an access policy associated with an existing destination. An access policy is an that is used to authorize claims to register a subscription filter against a given destination.
-
xAmzTargetLogs20140328PutLogEvents.putLogEventsUploads a batch of log events to the specified log stream.
The sequence token is now ignored in
PutLogEventsactions.PutLogEventsactions are always accepted and never returnInvalidSequenceTokenExceptionorDataAlreadyAcceptedExceptioneven if the sequence token is not valid. You can use parallelPutLogEventsactions on the same log stream.The batch of events must satisfy the following constraints:
-
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.
-
None of the log events in the batch can be more than 2 hours in the future.
-
None of the log events in the batch can be more than 14 days in the past. Also, none of the log events can be from earlier than the retention period of the log group.
-
The log events in the batch must be in chronological order by their timestamp. The timestamp is the time that the event occurred, expressed as the number of milliseconds after
Jan 1, 1970 00:00:00 UTC. (In Amazon Web Services Tools for PowerShell and the Amazon Web Services SDK for .NET, the timestamp is specified in .NET format:yyyy-mm-ddThh:mm:ss. For example,2017-09-15T13:45:30.) -
A batch of log events in a single request cannot span more than 24 hours. Otherwise, the operation fails.
-
The maximum number of log events in a batch is 10,000.
-
The quota of five requests per second per log stream has been removed. Instead,
PutLogEventsactions are throttled based on a per-second per-account quota. You can request an increase to the per-second throttling quota by using the Service Quotas service.
If a call to
PutLogEventsreturns "UnrecognizedClientException" the most likely cause is a non-valid Amazon Web Services access key ID or secret key. -
-
xAmzTargetLogs20140328PutMetricFilter.putMetricFilterCreates or updates a metric filter and associates it with the specified log group. With metric filters, you can configure rules to extract metric data from log events ingested through .
The maximum number of metric filters that can be associated with a log group is 100.
When you create a metric filter, you can also optionally assign a unit and dimensions to the metric that is created.
Metrics extracted from log events are charged as custom metrics. To prevent unexpected high charges, do not specify high-cardinality fields such as
IPAddressorrequestIDas dimensions. Each different value found for a dimension is treated as a separate metric and accrues charges as a separate custom metric.CloudWatch Logs disables a metric filter if it generates 1,000 different name/value pairs for your specified dimensions within a certain amount of time. This helps to prevent accidental high charges.
You can also set up a billing alarm to alert you if your charges are higher than expected. For more information, see .
-
xAmzTargetLogs20140328PutQueryDefinition.putQueryDefinitionCreates or updates a query definition for CloudWatch Logs Insights. For more information, see .
To update a query definition, specify its
queryDefinitionIdin your request. The values ofname,queryString, andlogGroupNamesare changed to the values that you specify in your update operation. No current values are retained from the current query definition. For example, imagine updating a current query definition that includes log groups. If you don't specify thelogGroupNamesparameter in your update operation, the query definition changes to contain no log groups.You must have the
logs:PutQueryDefinitionpermission to be able to perform this operation. -
xAmzTargetLogs20140328PutResourcePolicy.putResourcePolicyCreates or updates a resource policy allowing other Amazon Web Services services to put log events to this account, such as Amazon Route 53. An account can have up to 10 resource policies per Amazon Web Services Region.
-
xAmzTargetLogs20140328PutRetentionPolicy.putRetentionPolicySets the retention of the specified log group. With a retention policy, you can configure the number of days for which to retain log events in the specified log group.
CloudWatch Logs doesn’t immediately delete log events when they reach their retention setting. It typically takes up to 72 hours after that before log events are deleted, but in rare situations might take longer.
To illustrate, imagine that you change a log group to have a longer retention setting when it contains log events that are past the expiration date, but haven’t been deleted. Those log events will take up to 72 hours to be deleted after the new retention date is reached. To make sure that log data is deleted permanently, keep a log group at its lower retention setting until 72 hours after the previous retention period ends. Alternatively, wait to change the retention setting until you confirm that the earlier log events are deleted.
-
xAmzTargetLogs20140328PutSubscriptionFilter.putSubscriptionFilterCreates or updates a subscription filter and associates it with the specified log group. With subscription filters, you can subscribe to a real-time stream of log events ingested through and have them delivered to a specific destination. When log events are sent to the receiving service, they are Base64 encoded and compressed with the GZIP format.
The following destinations are supported for subscription filters:
-
An Amazon Kinesis data stream belonging to the same account as the subscription filter, for same-account delivery.
-
A logical destination that belongs to a different account, for cross-account delivery.
-
An Amazon Kinesis Data Firehose delivery stream that belongs to the same account as the subscription filter, for same-account delivery.
-
An Lambda function that belongs to the same account as the subscription filter, for same-account delivery.
Each log group can have up to two subscription filters associated with it. If you are updating an existing filter, you must specify the correct name in
filterName.To perform a
PutSubscriptionFilteroperation, you must also have theiam:PassRolepermission. -
-
xAmzTargetLogs20140328StartQuery.startQuerySchedules a query of a log group using CloudWatch Logs Insights. You specify the log group and time range to query and the query string to use.
For more information, see .
Queries time out after 15 minutes of runtime. If your queries are timing out, reduce the time range being searched or partition your query into a number of queries.
If you are using CloudWatch cross-account observability, you can use this operation in a monitoring account to start a query in a linked source account. For more information, see . For a cross-account
StartQueryoperation, the query definition must be defined in the monitoring account.You can have up to 20 concurrent CloudWatch Logs insights queries, including queries that have been added to dashboards.
-
xAmzTargetLogs20140328StopQuery.stopQueryStops a CloudWatch Logs Insights query that is in progress. If the query has already ended, the operation returns an error indicating that the specified query is not running.
-
xAmzTargetLogs20140328TagLogGroup.tagLogGroupThe TagLogGroup operation is on the path to deprecation. We recommend that you use instead.
Adds or updates the specified tags for the specified log group.
To list the tags for a log group, use . To remove tags, use .
For more information about tags, see in the Amazon CloudWatch Logs User Guide.
CloudWatch Logs doesn’t support IAM policies that prevent users from assigning specified tags to log groups using the
aws:Resource/key-nameoraws:TagKeyscondition keys. For more information about using tags to control access, see . -
xAmzTargetLogs20140328TagResource.tagResourceAssigns one or more tags (key-value pairs) to the specified CloudWatch Logs resource. Currently, the only CloudWatch Logs resources that can be tagged are log groups and destinations.
Tags can help you organize and categorize your resources. You can also use them to scope user permissions by granting a user permission to access or change only resources with certain tag values.
Tags don't have any semantic meaning to Amazon Web Services and are interpreted strictly as strings of characters.
You can use the
TagResourceaction with a resource that already has tags. If you specify a new tag key for the alarm, this tag is appended to the list of tags associated with the alarm. If you specify a tag key that is already associated with the alarm, the new tag value that you specify replaces the previous value for that tag.You can associate as many as 50 tags with a CloudWatch Logs resource.
-
xAmzTargetLogs20140328TestMetricFilter.testMetricFilterTests the filter pattern of a metric filter against a sample of log event messages. You can use this operation to validate the correctness of a metric filter pattern.
-
xAmzTargetLogs20140328UntagLogGroup.untagLogGroupThe UntagLogGroup operation is on the path to deprecation. We recommend that you use instead.
Removes the specified tags from the specified log group.
To list the tags for a log group, use . To add tags, use .
CloudWatch Logs doesn’t support IAM policies that prevent users from assigning specified tags to log groups using the
aws:Resource/key-nameoraws:TagKeyscondition keys. -
xAmzTargetLogs20140328UntagResource.untagResourceRemoves one or more tags from the specified resource.
-
openapi.previewSpecPreview an OpenAPI document before adding it as a source
-
openapi.addSourceAdd an OpenAPI source and register its operations as tools