AWS AmazonCloudWatch documentation change
Summary
Added detailed API cost analysis guidance and CloudTrail monitoring recommendations
Security assessment
Focuses on cost optimization rather than security. No security features or vulnerabilities addressed.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/cloudwatch_billing.md b/AmazonCloudWatch/latest/monitoring/cloudwatch_billing.md index 1b4aee976..6cee47359 100644 --- a//AmazonCloudWatch/latest/monitoring/cloudwatch_billing.md +++ b//AmazonCloudWatch/latest/monitoring/cloudwatch_billing.md @@ -378,0 +379,2 @@ To analyze costs, use Cost Explorer, and group your results by **_API Operation_ +The billing console shows generic API requests under UsageType _Requests_. These appear as _X.XX USD per 1,000 requests - [region]_. This rate applies to all requests with the UsageType Requests, aggregated together, beyond your free tier allowance. + @@ -383 +385 @@ Costs for API requests vary, and you incur costs when you exceed the number of A -`GetMetricData` and `GetMetricWidgetImage` aren't included under the AWS Free Tier limit. For more information, see [Using the AWS Free Tier](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/billing-free-tier.html) in the _AWS Billing User Guide_. +Only API requests with UsageType _Requests_ are included in the AWS Free Tier limit. API requests with any other UsageType incur charges from the first call. For more information, see [Using the AWS Free Tier](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/billing-free-tier.html) in the _AWS Billing User Guide_. @@ -386,0 +389,21 @@ The API requests that typically drive cost are `Put` and `Get` requests. +To monitor API request origins and identify users within your account, enable data events in CloudTrail and analyze recorded events using either: + + * Amazon CloudWatch Logs with Log Insights + + * Amazon S3 with Amazon Athena + + + + +###### Note + +Data events are not logged automatically by trails and event data stores. Logging data events incurs additional costs. For more information, see [AWS CloudTrail Pricing](https://aws.amazon.com/cloudtrail/pricing/). + +For more information, see [Logging data events](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/logging-data-events-with-cloudtrail.html) and [ Identifying resources driving CloudWatch GetMetricData charges using AWS CloudTrail](https://aws.amazon.com/blogs/mt/identifying-resources-driving-amazon-cloudwatch-getmetricdata-charges-using-aws-cloudtrail/). + +**_`API calls not incurring charges`_** + +When you log CloudWatch data events in CloudTrail, you might see more calls than you initiated. This happens because logging CloudWatch data events in CloudTrail captures API actions from internal components. Internal component calls don’t incur CloudWatch charges. However, these events count toward your CloudTrail event logging total and may affect CloudTrail charges. + +For example, CloudTrail will record GetMetricData calls initiated by a monitoring account to retrieve data from a source account, as well as GetMetricData calls initiated by CloudWatch dashboards to refresh widget data. These API calls do not incur CloudWatch charges. + @@ -389 +412 @@ The API requests that typically drive cost are `Put` and `Get` requests. -`PutMetricData` generates costs every time that it's called and can incur significant costs depending on the use case. For more information, see [PutMetricData](https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_PutMetricData.html) in the _Amazon CloudWatch API Reference_. +Each CloudWatch `PutMetricData` API call incurs charges. Frequent calls can significantly increase your costs, especially in high-volume monitoring scenarios. To reduce costs, consider batching multiple metrics in each API call or adjusting your monitoring frequency. For more information, see [PutMetricData](https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_PutMetricData.html) in the _Amazon CloudWatch API Reference_. @@ -404 +427 @@ To make the most of costs that are generated by `PutMetricData`, batch more data -`GetMetricData` can also generate significant costs. Common use cases that drive cost involve third-party monitoring tools that pull data to generate insights. For more information, see [GetMetricData](https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricData.html) in the _Amazon CloudWatch API Reference_. +The CloudWatch `GetMetricData` API operation can also significantly increase your costs. Third-party monitoring tools often increase costs when they frequently pull data to generate insights. To learn more about pricing and best practices for using `GetMetricData`, see [GetMetricData](https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricData.html) in the _Amazon CloudWatch API Reference_.