AmazonCloudWatch

dashboard

DashboardsUsageHour-Basic

CloudWatch charges a usage fee per hour for each CloudWatch Dashboard. For all billing codes that have the '-basic' appendange such as this one, this corresponds to the fee for dashboards that have 50 or fewer metrics.

DashboardsUsageHour

CloudWatch charges a usage fee per hour for each CloudWatch Dashboard. This billing code represents the fee for a CloudWatch dashboard that has more than 50 metrics. Dashboards that have more than 50 metrics incur a higher fee per month than Dashboards with 50 metrics or less.

api-request

CW:Requests

CW:GMD-Metrics

This billing code is an abbreviation for "CloudWatch - Get Metric Data". When querying with Metrics Insights through the GetMetricData API, your charge is calculated based on the number of metrics analyzed, regardless of how you output the results. You can request up to five statistics for the same metric in a single GetMetricData metric request. Each additional set of up to five statistics requested for that same metric is billed as an additional metric request. GetMetricData is charged at a rate per 1,000 metrics requested.

CW:GMWI-Metrics

This billing code is an abbreviation for "CloudWatch - Get Metric Widget Image". You can use the GetMetricWidgetImage API to retrieve a snapshot graph of one or more Amazon CloudWatch metrics as a bitmap image. You can then embed this image into your services and products, such as wiki pages, reports, and documents. You could also retrieve images regularly, such as every minute, and create your own custom live dashboard. The graph you retrieve can include all CloudWatch metric graph features, including metric math and horizontal and vertical annotations. This billing code is charged per 1,000 requests.

CW:GIRR-Metrics

This billing code is an abbreviation for "CloudWatch - Get Insight Rule Report". This operation returns the time series data collected by a Contributor Insights rule. The data includes the identity and number of contributors to the log group. This billing code is charged at a rate per 1,000 metrics requested.

alarm

CW:AlarmMonitorUsage

CW:HighResAlarmMonitorUsage

CW:CompositeAlarmMonitorUsage

With CloudWatch, you can combine several alarms into one composite alarm to create a summarized, aggregated health indicator over a whole application or group of resources. Composite alarms are alarms that determine their state by monitoring the states of other alarms. You define rules to combine the status of those monitored alarms using Boolean logic. This is the billing code for composite alarms and they're charged at a rate per composite alarm per month.

MetricInsightAlarmUsage

metric

CW:MetricMonitorUsage

CW:ObservationUsage

data-payload

S3-Egress-Bytes

Vended logs are specific AWS service logs natively published by AWS services on behalf of the customer and available at volume discount pricing, and delivered to S3. This is the billing code specific to vending logs to S3.

DataProcessing-Bytes

CloudWatch charges for Bytes process. This is the billing code for data ingestion for Standard log class.

VendedLog-Bytes

Vended logs are specific AWS service logs natively published by AWS services on behalf of the customer and available at volume discount pricing, and delivered to CloudWatch. This is the billing code specific to vending logs to CloudWatch Logs.

S3-Egress-InputBytes

Vended logs are specific AWS service logs natively published by AWS services on behalf of the customer and available at volume discount pricing, and delivered to S3. This is the billing code specific to vending logs to S3 specifically in parquet format.

DataScanned-Bytes

DataProcessingIA-Bytes

Logs-LiveTail

CloudWatch Logs allows you to live tail logs. This is the billing code for logs analyzed during a CloudWatch Logs Live Tail session which is charged at a rate of $0.01 per minute.

VendedLogIA-Bytes

Vended logs are specific AWS service logs natively published by AWS services on behalf of the customer and available at volume discount pricing, and delivered to CloudWatch. This is the billing code specific to vending logs to CloudWatch Logs Infrequent Access.

FH-Egress-Bytes

Vended logs are specific AWS service logs natively published by AWS services on behalf of the customer and available at volume discount pricing, and delivered to Data Firehose. This is the billing code specific to vending logs to Data Firehose.

VendedLog-Bytes-CFLogs

FH-Egress-Bytes-CFLogs

storage-snapshot

TimedStorage-ByteHrs

The amount of storage measured in Byte-Hour. Byte-Hours are calculated based on the storage volume (in bytes) and the duration of storage (in hours). For example, storing 1 byte of data for 1 hour is equivalent to 1 Byte-Hour.

metric-streams

MetricStreamUsage

canaries

CW:Canary-runs

CloudWatch charges a rate per canary run. This is the billing code for total Canary run charges.

contributor-insights

CW:ContributorRulesManaged

CW:ContributorInsightRules

other

Service Categories
CW:ContributorInsightEvents

CW:InternetMonitor-MonitoredResource

When you create an internet monitor, you associate application resources with it to be monitored, such as Amazon Virtual Private Clouds (VPCs), CloudFront distributions, and WorkSpaces directories. You are charged $0.01 per resource per hour for each monitor.

DataProtection-Bytes

CW:ContributorEventsManaged

CW:RUM-events

CloudWatch RUM is priced on the number of RUM events collected. Each data item collected using the RUM web client is considered a RUM event. Examples of a RUM event include a page view, a JavaScript error, and an HTTP error. This is the billing code for total RUM events and it is charged per 100,000 events.

CW:InternetMonitor-CityNetwork

A city-network is the location (city) where your clients access your application resources and the network, such as an internet service provider, through which clients access the resources. You are charged $0.74 per 10,000 monitored city-networks per hour, after the first 100 city-networks (across all monitors per account).

S3-Egress-InputBytes

Vended logs are specific AWS service logs natively published by AWS services on behalf of the customer and available at volume discount pricing, and delivered to S3. This is the billing code specific to vending logs to S3 specifically in parquet format.

CW:RUM-free-events

CloudWatch has a free tier for RUM events. The first time free trial includes 1 million RUM events per account.

application-signals

Application-Signals

You are billed per million inbound and outbound requests to and from your applications and Service Level Objectives (SLO). Inbound requests refer to service requests received by your applications. Outbound requests are those made by your application to dependencies monitored for application performance. Each inbound request received generates 1 application signal. Each outbound request made generates 1 application signal. Every SLO generates 2 application signals per SLI (service level indicator) metric period.

cloudwatch-events

Logs-LiveTail

cloudwatch-network-monitor

CWNMHybrid-Paid

application-signals-bytes

Application-Signals-Bytes

For CloudWatch Signals, you are are billed per GB of application metrics and spans ingested in CloudWatch in addition to the requests made which is a separate distinct charge. This billing code represents the amount of data ingested per month.