# Amazon CloudWatch

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch

> Amazon CloudWatch is a monitoring and observability service offered by Amazon Web Services (AWS) that provides data and actionable insights to monitor applications, respond to system-wide performance changes, optimize resource utilization, and get a unified view of operational health.

Practice exams covering Amazon CloudWatch: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [AIB-C01 (beta) AWS Certified AI Business Strategist](https://blowstack.com/practice-exams/aws-certified-ai-business-strategist), [AIF-C01 AWS Certified AI Practitioner](https://blowstack.com/practice-exams/aws-certified-ai-practitioner), [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate), [DVA-C02 AWS Certified Developer - Associate](https://blowstack.com/practice-exams/aws-certified-developer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [AIP-C01 AWS Certified Generative AI Developer - Professional](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional), [MLA-C02 (beta) AWS Certified Machine Learning Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate), [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C02 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 8 key features of Amazon CloudWatch

Amazon CloudWatch provides real-time monitoring, customizable alarms, dashboards for consolidated data visualization, logs management, event-driven automation, the capability to publish custom metrics, and seamless integration with AWS services.

1. **Real-time Monitoring**: Amazon CloudWatch enables real-time monitoring of AWS resources and applications, allowing users to collect and track metrics, collect and monitor log files, and set alarms.
2. **Alarms**: Users can set alarms in CloudWatch to receive notifications or automatically change the resources being monitored, based on predefined rules, which helps in proactive issue resolution and automation of actions.
3. **Dashboards**: CloudWatch offers customizable dashboards that provide a consolidated view of the metrics and alarms for your AWS resources, making it easier to view and analyze your operations.
4. **Logs**: With CloudWatch Logs, users can monitor, store, and access their log files from Amazon EC2 instances, AWS CloudTrail, and other sources, enabling efficient troubleshooting and security analysis.
5. **Amazon EventBridge**: Amazon EventBridge (formerly Amazon CloudWatch Events) deliver a near real-time stream of system events that describe changes in AWS resources, allowing users to respond automatically to state changes with triggered actions.
6. **Custom Metrics**: Users can publish their own metrics to CloudWatch, enabling them to monitor application performance and operational health uniquely suited to their needs.
7. **Integration**: CloudWatch seamlessly integrates with other AWS services, providing comprehensive monitoring solutions that enhance the performance and availability of cloud resources.
8. **Automatic Service Dashboards**: The CloudWatch home page automatically displays metrics about every AWS service you use.

## Where Amazon CloudWatch is used

Amazon CloudWatch is utilized for application and infrastructure monitoring, log management and analysis, automated alarming and notifications, and creating custom dashboards for comprehensive operational visibility.

1. **Application Monitoring**: Amazon CloudWatch facilitates real-time monitoring of applications by gathering and tracking metrics, which enables teams to observe application performance, optimize resource utilization, and identify and respond to issues promptly, ensuring high availability and performance.
2. **Infrastructure Monitoring**: This use case involves using CloudWatch to monitor the health and performance of AWS resources such as EC2 instances, DynamoDB tables, and RDS database instances. It helps in detecting failures, measuring resource utilization, and ensuring that the infrastructure scales properly to meet demand.
3. **Log Management and Analysis**: CloudWatch Logs support the collection, monitoring, and analysis of log files from AWS resources, applications, and on-premises servers. This facilitates troubleshooting, the security monitoring of environment, and the retention of logs for compliance purposes.
4. **Automated Alarming and Notifications**: With CloudWatch, users can set up alarms and notifications based on specific metrics or logs. This helps in automated incident detection and enables teams to take immediate action or automate responses to ensure continuous operation and mitigate issues.
5. **Custom Dashboards for Operational Visibility**: CloudWatch allows the creation of customizable dashboards to visualize the performance and health of AWS resources and applications. This centralized view helps stakeholders understand operational status and make informed decisions.

## How Amazon CloudWatch is priced

Amazon CloudWatch pricing includes a free tier for basic monitoring, a pay-as-you-go model for additional usage, and extra charges for detailed monitoring.

- **Amazon CloudWatch Free Tier**: Offers a limited amount of data ingestion, alarm evaluations, and dashboard metrics for free each month.
- **Pay-as-you-go Pricing**: There is no upfront commitment or minimum fee; charges are based on usage and billed at the end of the month.
- **Detailed Monitoring**: Additional charges apply for enabling detailed monitoring for Amazon EC2 instances and other AWS services, providing more granular data.
- **Classic Custom Metrics**: Custom metric charges are prorated hourly and incurred only during hours when metrics are sent; each unique combination of dimensions is treated as a separate metric.
- **CloudWatch Omni**: Standard CloudWatch ingestion and storage rates apply, with additional charges for queries above the included allowance.
- **OpenTelemetry Metrics**: Publishing OpenTelemetry metrics costs $0.50 per GB ingested, including 15 months of storage with no separate API-call, metric-storage, or unique-series charges.
- **OpenTelemetry Vended Metric Enrichment**: Converting AWS-generated CloudWatch metrics to OpenTelemetry format and enriching them with resource tags and account metadata costs $0.50 per GB ingested.
- **PromQL Queries**: PromQL API queries cost $0.01 per million samples scanned; queries through the CloudWatch console, including dashboards, are free, while PromQL alarm evaluations incur sample-scanning query charges.
- **Logs Insights Queries**: Logs Insights queries are charged according to the amount of ingested log data scanned by each query.
- **Logs Storage**: Log storage is billed per compressed GB, with separate rates for Standard, Infrequent Access, and Archive Instant Access storage.
- **Logs Live Tail**: Live Tail costs $0.01 per minute.
- **Logs Data Protection**: Data Protection is free for Standard logs and charged per GB scanned for Infrequent Access logs.
- **Log Centralization**: For cross-account and cross-Region log centralization, data transfer and ingestion for the first copy are free; additional copies cost $0.05 per GB, and storage charges apply to every copy.
- **Data Transfer**: CloudWatch has no data transfer IN charge; data transfer OUT from CloudWatch Logs follows the corresponding Amazon EC2 outbound transfer rates.
- **Vended Logs**: Logs from designated AWS services use volume-tiered pricing and can be delivered to CloudWatch Logs, Amazon S3, or Amazon Data Firehose.
- **Analyze with OpenSearch**: Analyzing CloudWatch Logs through OpenSearch incurs standard CloudWatch Logs ingestion and storage charges plus OpenSearch Serverless and OpenSearch Direct Query usage charges.
- **Contributor Insights for CloudWatch Logs**: Contributor Insights log rules are charged per rule per month and per million matching log events per month.
- **Contributor Insights for DynamoDB**: Contributor Insights for DynamoDB is charged per rule per month and per million DynamoDB events generated when table items are read or written.
- **Contributor Insights for PrivateLink**: Contributor Insights for PrivateLink is charged per rule per month, with each rule evaluating up to 50,000 endpoints.
- **Metric Streams**: Metric Streams are billed by metric update, including four default statistics; each additional set of five statistics requested for a metric counts as another update, and Amazon Data Firehose ingestion charges also apply.
- **Metric Centralization**: The first physical metric copy to a destination account is free; subsequent copies to additional Regions or accounts cost $0.05 per GB copied.
- **Dashboards**: Custom dashboard charges are prorated hourly for as long as each dashboard exists.
- **Alarms**: Alarm charges accrue hourly from the first hour an alarm exists; metric alarms are charged for each metric listed in the alarm expression.
- **Application Signals and Transaction Search**: The bundled Application Signals and transaction search model charges per GB of application metrics and spans ingested and per million spans indexed as X-Ray trace summaries, with the first 1% of spans indexed free.
- **Application Signals Without Transaction Spans**: Application Signals without transaction-span visibility is billed per million signals: each inbound or outbound application request generates one signal, and each SLO generates two signals per SLI metric period.
- **X-Ray Traces**: X-Ray charges separately for traces recorded, retrieved, and scanned.
- **Synthetics**: Synthetics is billed per canary run.
- **Real User Monitoring**: Web RUM is billed by event count, while RUM OpenTelemetry spans and events are billed per GB ingested.
- **Container Insights with OpenTelemetry for EKS**: Container Insights with OpenTelemetry for EKS costs $0.08 per GB ingested, with no separate API-call, storage, or metric-series charges.
- **Container Insights Enhanced Observability for EKS**: Enhanced observability for EKS uses tiered observation-based pricing that combines metric storage and performance-log ingestion; log storage and container-log ingestion remain separately charged.
- **Container Insights Enhanced Observability for ECS**: Enhanced observability for ECS is billed per metric per month, prorated hourly, combining metric storage and performance-log ingestion; log storage and container-log ingestion remain separately charged.
- **Database Insights Retention**: Database Insights retention charges use vCPU-hours for provisioned instances and ACU-hours for Serverless and Limitless instances, with separate first-month and additional-month retention rates.
- **Custom Logs Ingestion**: Custom log ingestion is billed per GB, with separate rates for Standard and Infrequent Access.
- **Classic Metric API Usage**: PutMetricData incurs request charges in addition to metric storage; GetMetricData and GetInsightRuleReport are billed by metrics requested, while GetMetricStatistics and ListMetrics are billed by requests.
- **Metrics Insights Queries**: Metrics Insights queries through GetMetricData are billed by the total number of metrics analyzed; Metrics Insights queries through the CloudWatch console are free.
- **Log Query Alarms**: Log query alarms incur a standard alarm charge plus query charges per GB scanned.
- **Metrics Insights Query Alarms**: Metrics Insights query alarms are billed for each metric analyzed by the query.
- **Anomaly Detection Alarms**: Anomaly detection alarms are billed for each metric in the alarm expression plus two additional alarm metrics for the model's upper and lower bands.
- **Composite Alarms**: Composite alarms are billed per composite alarm per month.
- **Dashboard API Usage**: GetDashboard, ListDashboards, PutDashboard, and DeleteDashboards are billed per API request.

## Services Amazon CloudWatch works with

- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: Monitors the performance and resource utilization of Amazon EC2 instances, including CPU utilization, disk read/write operations, and network traffic.
- **[Amazon RDS](https://blowstack.com/tools/cloud-services-hub/amazon-rds)**: Tracks the operational health and performance metrics for Amazon RDS instances, including CPU utilization, storage space, and memory usage.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: Provides storage metrics and counts HTTP requests for Amazon S3 buckets, including the number of bytes downloaded or uploaded.
- **[AWS Lambda](https://blowstack.com/tools/cloud-services-hub/aws-lambda)**: Monitors AWS Lambda functions by tracking metrics such as invocation count, duration, and error rates.
- **[Amazon API Gateway](https://blowstack.com/tools/cloud-services-hub/amazon-api-gateway)**: CloudWatch collects API Gateway request counts, latency, and error metrics, along with configured access and execution logs. Alarms can flag rising API error rates or latency.
- **[Amazon AppFlow](https://blowstack.com/tools/cloud-services-hub/amazon-appflow)**: CloudWatch receives AppFlow flow-execution metrics, including records processed and execution failures, so you can monitor data transfers and alarm on unsuccessful runs.
- **[Amazon Athena](https://blowstack.com/tools/cloud-services-hub/amazon-athena)**: CloudWatch receives Athena query metrics for enabled workgroups, including execution time and data scanned. Athena can also query CloudWatch telemetry exposed through the S3 Tables integration.
- **[Amazon Augmented AI (Amazon A2I)](https://blowstack.com/tools/cloud-services-hub/amazon-augmented-ai-(amazon-a2i))**: CloudWatch receives Amazon A2I human-review workflow metrics, allowing you to track human-loop activity and monitor review completion times.
- **[Amazon Aurora](https://blowstack.com/tools/cloud-services-hub/amazon-aurora)**: CloudWatch collects Aurora database and cluster metrics, including connection counts, replica lag, and storage activity. Supported database logs and Enhanced Monitoring output can also be delivered to CloudWatch Logs.
- **[Amazon Aurora Serverless](https://blowstack.com/tools/cloud-services-hub/amazon-aurora-serverless)**: CloudWatch tracks Aurora Serverless capacity and utilization metrics, including serverless database capacity and ACU utilization. These metrics help identify workloads approaching their configured capacity limits.
- **[Amazon Bedrock](https://blowstack.com/tools/cloud-services-hub/amazon-bedrock)**: CloudWatch collects Bedrock invocation counts, latency, throttling, and error metrics. Configured model invocation logging can also deliver supported request and response records to CloudWatch Logs.
- **[Amazon Bedrock AgentCore](https://blowstack.com/tools/cloud-services-hub/amazon-bedrock-agentcore)**: CloudWatch powers AgentCore observability by collecting agent metrics, logs, and traces. You can inspect agent sessions and correlate model calls with tool execution and application failures.
- **[Amazon Braket](https://blowstack.com/tools/cloud-services-hub/amazon-braket)**: CloudWatch collects Braket quantum-task metrics and hybrid-job logs and metrics. These provide visibility into task execution and the progress of hybrid quantum algorithms.
- **[Amazon CloudFront](https://blowstack.com/tools/cloud-services-hub/amazon-cloudfront)**: CloudWatch receives CloudFront distribution metrics such as requests, error rates, and cache performance. CloudFront Functions also sends function execution logs to CloudWatch Logs.
- **[Amazon CloudSearch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudsearch)**: CloudWatch collects CloudSearch domain metrics, including search latency, indexing activity, and resource utilization. Alarms can identify search errors or capacity pressure.
- **[Amazon CodeGuru](https://blowstack.com/tools/cloud-services-hub/amazon-codeguru)**: CloudWatch receives supported CodeGuru operational metrics, allowing you to monitor code-review and profiling activity and create alarms for operational problems.
- **[Amazon Cognito](https://blowstack.com/tools/cloud-services-hub/amazon-cognito)**: CloudWatch receives Cognito authentication and usage metrics, while supported user-pool logging settings can deliver activity logs to CloudWatch Logs. These help investigate authentication failures and unusual sign-in activity.
- **[Amazon Comprehend](https://blowstack.com/tools/cloud-services-hub/amazon-comprehend)**: CloudWatch collects Comprehend endpoint metrics such as request latency, errors, and inference-unit utilization. You can use these metrics to monitor real-time analysis capacity.
- **[Amazon Connect](https://blowstack.com/tools/cloud-services-hub/amazon-connect)**: CloudWatch receives Connect operational metrics and configured contact-flow logs. Dashboards and Logs Insights queries can help investigate contact-flow failures and contact-center service issues.
- **[Amazon Data Firehose](https://blowstack.com/tools/cloud-services-hub/amazon-kinesis-data-firehose)**: CloudWatch Logs subscription filters can stream log records to Data Firehose for delivery to supported destinations. CloudWatch also monitors Firehose delivery metrics and receives configured delivery error logs.
- **[Amazon DataZone](https://blowstack.com/tools/cloud-services-hub/amazon-datazone)**: CloudWatch receives DataZone operational telemetry, including supported data-source execution logs and metrics. This helps diagnose ingestion failures and monitor domain activity.
- **[Amazon Detective](https://blowstack.com/tools/cloud-services-hub/amazon-detective)**: CloudWatch receives Detective data-ingestion metrics for behavior graphs. You can monitor ingestion volume and detect interruptions in supported data sources.
- **[Amazon DevOps Guru](https://blowstack.com/tools/cloud-services-hub/amazon-devops-guru)**: DevOps Guru analyzes CloudWatch metrics and supported log data to identify anomalous application behavior. Its insights can connect a performance problem with related metrics and log anomalies.
- **[Amazon DocumentDB (with MongoDB compatibility)](https://blowstack.com/tools/cloud-services-hub/amazon-documentdb-(with-mongodb-compatibility))**: CloudWatch collects DocumentDB instance and cluster metrics, including connections, memory, and replica lag. Configured audit and profiler logs can also be published to CloudWatch Logs.
- **[Amazon DynamoDB](https://blowstack.com/tools/cloud-services-hub/amazon-dynamodb)**: CloudWatch collects DynamoDB table and index metrics such as consumed capacity, throttled requests, and latency. Contributor Insights can identify frequently accessed or throttled partition keys.
- **[Amazon EC2 Auto Scaling](https://blowstack.com/tools/cloud-services-hub/amazon-ec2-auto-scaling)**: CloudWatch alarms drive EC2 Auto Scaling scaling policies, and CloudWatch receives metrics about Auto Scaling group capacity. Target-tracking policies create and manage alarms for their scaling targets.
- **[Amazon ECS Anywhere](https://blowstack.com/tools/cloud-services-hub/amazon-ecs-anywhere)**: CloudWatch Logs can receive container output from ECS Anywhere tasks through the awslogs logging driver. The CloudWatch agent can collect additional host telemetry from the external instances.
- **[Amazon EKS Anywhere](https://blowstack.com/tools/cloud-services-hub/amazon-eks-anywhere)**: CloudWatch Container Insights can collect metrics and logs from EKS Anywhere clusters through installed collectors. This provides visibility into cluster nodes, pods, and container resource usage.
- **[Amazon Elastic Block Store (Amazon EBS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-block-store-(amazon-ebs))**: CloudWatch collects EBS volume metrics such as read and write operations, throughput, queue length, and applicable burst balances. Alarms can warn when a volume approaches performance limits.
- **[Amazon Elastic Container Registry (Amazon ECR)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-registry-(amazon-ecr))**: CloudWatch receives ECR repository usage metrics, including image push and pull activity. These metrics support dashboards and alarms for container-image distribution.
- **[Amazon Elastic Container Service (Amazon ECS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-service-(amazon-ecs))**: CloudWatch collects ECS service metrics, while Container Insights adds task and container telemetry. The awslogs logging driver sends container output directly to CloudWatch Logs.
- **[Amazon Elastic File System (Amazon EFS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-file-system-(amazon-efs))**: CloudWatch collects EFS metrics for throughput, client connections, storage, and permitted performance. Alarms can identify throughput constraints or increasing file-system utilization.
- **[Amazon Elastic Kubernetes Service (Amazon EKS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-kubernetes-service-(amazon-eks))**: CloudWatch receives enabled EKS control-plane logs, and Container Insights collects cluster, node, pod, and container telemetry. Application Signals can add application-level performance monitoring.
- **[Amazon ElastiCache](https://blowstack.com/tools/cloud-services-hub/amazon-elasticache)**: CloudWatch collects ElastiCache metrics such as cache hits, evictions, memory usage, and replication lag. Supported engine and slow logs can also be delivered to CloudWatch Logs.
- **[Amazon EMR](https://blowstack.com/tools/cloud-services-hub/amazon-emr)**: CloudWatch receives EMR cluster and job metrics, and supported EMR deployment options can send application logs to CloudWatch Logs. These help identify failed jobs and resource bottlenecks.
- **[Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge)**: CloudWatch publishes alarm state-change events to EventBridge, where rules can route them to automation targets. EventBridge can also deliver matched events to CloudWatch Logs and publishes its own delivery metrics.
- **[Amazon Fraud Detector](https://blowstack.com/tools/cloud-services-hub/amazon-fraud-detector)**: CloudWatch receives Fraud Detector prediction metrics, including request volume, latency, and errors. These help monitor the health of real-time fraud evaluation.
- **[Amazon FSx](https://blowstack.com/tools/cloud-services-hub/amazon-fsx-(for-all-types))**: CloudWatch collects file-system-specific FSx metrics for storage, throughput, I/O, and resource utilization. Supported FSx file-access audit logs can also be delivered to CloudWatch Logs.
- **[Amazon GameLift](https://blowstack.com/tools/cloud-services-hub/amazon-gamelift)**: CloudWatch collects GameLift fleet, game-session, player-session, and matchmaking metrics. Dashboards and alarms can reveal placement failures or insufficient hosting capacity.
- **[Amazon GuardDuty](https://blowstack.com/tools/cloud-services-hub/amazon-guardduty)**: CloudWatch receives GuardDuty Malware Protection metrics for supported scanning workflows. These metrics help monitor scan outcomes, failures, and skipped resources.
- **[Amazon HealthLake](https://blowstack.com/tools/cloud-services-hub/amazon-healthlake)**: CloudWatch receives HealthLake operational metrics and supported import and export job logs. You can use them to investigate failed data-processing jobs and monitor datastore requests.
- **[Amazon Inspector](https://blowstack.com/tools/cloud-services-hub/amazon-inspector)**: CloudWatch exposes supported Inspector usage metrics, allowing you to monitor service usage and create alarms as usage approaches applicable quotas.
- **[Amazon Kendra](https://blowstack.com/tools/cloud-services-hub/amazon-kendra)**: CloudWatch collects Kendra query and indexing metrics, while data-source synchronization logs can be delivered to CloudWatch Logs. These help diagnose failed synchronization jobs and search errors.
- **[Amazon Keyspaces (for Apache Cassandra)](https://blowstack.com/tools/cloud-services-hub/amazon-keyspaces-(for-apache-cassandra))**: CloudWatch collects Keyspaces table metrics, including consumed capacity, throttling, latency, and errors. Alarms can warn when provisioned capacity is insufficient.
- **[Amazon Kinesis Data Streams](https://blowstack.com/tools/cloud-services-hub/amazon-kinesis-data-streams)**: CloudWatch Logs subscriptions can deliver log events to Kinesis Data Streams for real-time processing. CloudWatch also collects stream and optional shard-level metrics for throughput, throttling, and consumer lag.
- **[Amazon Kinesis Video Streams](https://blowstack.com/tools/cloud-services-hub/amazon-kinesis-video-streams)**: CloudWatch collects Kinesis Video Streams metrics for ingestion, playback, latency, and errors. These help identify interruptions between video producers and consumers.
- **[Amazon Lex](https://blowstack.com/tools/cloud-services-hub/amazon-lex)**: CloudWatch receives Lex runtime metrics and configured text conversation logs. You can monitor bot latency and errors and inspect conversations that did not reach the intended outcome.
- **[Amazon Location Service](https://blowstack.com/tools/cloud-services-hub/amazon-location-service)**: CloudWatch collects Location Service request, latency, and error metrics. Alarms can identify increased failures in map, route, place, or tracking operations.
- **[Amazon Macie](https://blowstack.com/tools/cloud-services-hub/amazon-macie)**: CloudWatch receives Macie metrics for sensitive-data discovery and bucket monitoring. You can track discovery activity and identify processing errors.
- **[Amazon Managed Blockchain](https://blowstack.com/tools/cloud-services-hub/amazon-managed-blockchain)**: CloudWatch collects supported Managed Blockchain network and node metrics, and configured blockchain logs can be delivered to CloudWatch Logs. These help monitor node health and transaction-processing activity.
- **[Amazon Managed Grafana](https://blowstack.com/tools/cloud-services-hub/amazon-managed-grafana)**: CloudWatch is a built-in data source for Managed Grafana, allowing dashboards to query CloudWatch metrics and logs. Teams can combine AWS telemetry with other supported data sources in the same dashboards.
- **[Amazon Managed Service for Apache Flink](https://blowstack.com/tools/cloud-services-hub/amazon-managed-service-for-apache-flink)**: CloudWatch collects Flink application metrics and configured application logs. You can monitor checkpoint failures, backpressure, processing latency, and application restarts.
- **[Amazon Managed Service for Prometheus](https://blowstack.com/tools/cloud-services-hub/amazon-managed-service-for-prometheus)**: CloudWatch receives Managed Service for Prometheus workspace metrics for ingestion, queries, and rule evaluation. These help detect rejected samples, query failures, and workspace capacity pressure.
- **[Amazon Managed Streaming for Apache Kafka](https://blowstack.com/tools/cloud-services-hub/amazon-managed-streaming-for-apache-kafka)**: CloudWatch collects MSK broker and cluster metrics and can receive broker logs. CloudWatch's MSK observability solution provides dashboards for investigating broker health and Kafka performance.
- **[Amazon Managed Workflows for Apache Airflow (Amazon MWAA)](https://blowstack.com/tools/cloud-services-hub/amazon-managed-workflows-for-apache-airflow-(amazon-mwaa))**: CloudWatch receives MWAA environment metrics and configured scheduler, worker, webserver, DAG-processing, and task logs. These help diagnose failed workflows and scheduler bottlenecks.
- **[Amazon MemoryDB for Redis](https://blowstack.com/tools/cloud-services-hub/amazon-memorydb-for-redis)**: CloudWatch collects MemoryDB node and cluster metrics, including memory usage, connections, throughput, and replication behavior. Alarms can identify resource pressure before it affects application requests.
- **[Amazon Monitron](https://blowstack.com/tools/cloud-services-hub/amazon-monitron)**: CloudWatch receives Monitron live-data-export metrics. You can monitor export success and failures when sending sensor data to a configured Kinesis data stream.
- **[Amazon MQ](https://blowstack.com/tools/cloud-services-hub/amazon-mq)**: CloudWatch collects MQ broker and queue metrics, and enabled broker logs are published to CloudWatch Logs. You can alarm on growing queue depth, resource pressure, or unavailable brokers.
- **[Amazon Neptune](https://blowstack.com/tools/cloud-services-hub/amazon-neptune)**: CloudWatch collects Neptune database metrics and supported database logs. These help investigate slow graph queries, replication lag, and resource utilization.
- **[Amazon OpenSearch Service](https://blowstack.com/tools/cloud-services-hub/amazon-opensearch-service)**: CloudWatch monitors OpenSearch clusters and receives configured application, audit, and slow logs. CloudWatch Logs also integrates with OpenSearch Service for log analytics and can stream log subscriptions into OpenSearch domains.
- **[Amazon Personalize](https://blowstack.com/tools/cloud-services-hub/amazon-personalize)**: CloudWatch receives Personalize recommendation-service metrics, including request counts, latency, and errors. These help monitor the operational health of recommendation workloads.
- **[Amazon Polly](https://blowstack.com/tools/cloud-services-hub/amazon-polly)**: CloudWatch collects Polly request metrics, including successful requests, errors, latency, and synthesized characters. You can monitor speech-generation usage and failures.
- **[Amazon Q](https://blowstack.com/tools/cloud-services-hub/amazon-q)**: CloudWatch integrates with Amazon Q Developer operational investigations to analyze incidents using relevant telemetry. Investigations can correlate metrics, logs, and resource changes to suggest possible causes.
- **[Amazon Q Business](https://blowstack.com/tools/cloud-services-hub/amazon-q-business)**: CloudWatch receives Q Business operational metrics and supported data-source synchronization logs. These help diagnose connector ingestion failures and monitor application requests.
- **[Amazon QuickSight](https://blowstack.com/tools/cloud-services-hub/amazon-quicksight)**: CloudWatch collects QuickSight dashboard, visual, and dataset-ingestion metrics. You can monitor dashboard load performance and alarm on failed dataset refreshes.
- **[Amazon RDS Proxy](https://blowstack.com/tools/cloud-services-hub/amazon-rds-proxy)**: CloudWatch collects RDS Proxy connection, latency, and capacity metrics and receives enabled diagnostic logs. You can compare client connections with database connections to investigate pooling problems.
- **[Amazon Redshift](https://blowstack.com/tools/cloud-services-hub/amazon-redshift)**: CloudWatch collects Redshift cluster and serverless metrics, including query performance and resource utilization. Configured database audit logging can publish connection, user, and activity logs to CloudWatch Logs.
- **[Amazon Rekognition](https://blowstack.com/tools/cloud-services-hub/amazon-rekognition)**: CloudWatch collects Rekognition request counts, response times, throttling, and errors. Alarms can identify service failures or sustained throttling in image and video analysis workloads.
- **[Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53)**: CloudWatch receives Route 53 health-check metrics and configured DNS query logs. CloudWatch alarms can also supply the health status used by Route 53 health checks.
- **[Amazon SageMaker](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker)**: CloudWatch collects SageMaker training, processing, endpoint, and monitoring metrics and logs. You can alarm on inference latency, endpoint errors, or model-monitoring violations.
- **[Amazon SageMaker Data Wrangler](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker-data-wrangler)**: CloudWatch receives logs and metrics from SageMaker processing jobs that execute exported Data Wrangler flows. These help investigate failed transformations and monitor processing-resource utilization.
- **[Amazon SageMaker Ground Truth](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker-ground-truth)**: CloudWatch receives Ground Truth labeling-job metrics and supported execution logs. You can track labeling progress and investigate failures in labeling workflows.
- **[Amazon Security Lake](https://blowstack.com/tools/cloud-services-hub/amazon-security-lake)**: CloudWatch receives Security Lake operational metrics for data collection and processing. These help identify ingestion problems and monitor the health of the security data lake.
- **[Amazon Simple Email Service (Amazon SES)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-email-service-(amazon-ses))**: CloudWatch collects SES sending, bounce, complaint, and delivery metrics. SES configuration sets can publish selected email-event metrics to CloudWatch for more detailed monitoring.
- **[Amazon Simple Notification Service (Amazon SNS)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-notification-service-(amazon-sns))**: CloudWatch alarms can publish notifications to SNS topics when their state changes. CloudWatch also monitors SNS delivery metrics and receives configured message-delivery status logs.
- **[Amazon Simple Queue Service (Amazon SQS)](https://blowstack.com/tools/cloud-services-hub/amazon-simple-queue-service-(amazon-sqs))**: CloudWatch collects SQS queue metrics such as message counts, oldest-message age, and in-flight messages. Alarms can detect growing backlogs or messages accumulating in a dead-letter queue.
- **[Amazon Textract](https://blowstack.com/tools/cloud-services-hub/amazon-textract)**: CloudWatch collects Textract request, latency, throttling, and error metrics. These help monitor document-processing workloads and detect API capacity constraints.
- **[Amazon Timestream](https://blowstack.com/tools/cloud-services-hub/amazon-timestream)**: CloudWatch collects Timestream ingestion, query, storage, and error metrics. You can monitor rejected records, query latency, and resource consumption.
- **[Amazon Timestream for InfluxDB](https://blowstack.com/tools/cloud-services-hub/amazon-timestream-for-influxdb)**: CloudWatch receives Timestream for InfluxDB instance metrics for resource utilization and database health. Alarms can identify sustained CPU, memory, or storage pressure.
- **[Amazon Transcribe](https://blowstack.com/tools/cloud-services-hub/amazon-transcribe)**: CloudWatch collects Transcribe usage, success, latency, and error metrics for supported transcription operations. These help detect transcription failures and throttling.
- **[Amazon Translate](https://blowstack.com/tools/cloud-services-hub/amazon-translate)**: CloudWatch collects Translate request counts, character counts, latency, and errors. You can track translation usage and alarm on failed or throttled requests.
- **[Amazon Verified Permissions](https://blowstack.com/tools/cloud-services-hub/amazon-verified-permissions)**: CloudWatch collects Verified Permissions authorization metrics, including request volume, latency, and errors. These help monitor authorization-service performance.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: CloudWatch Logs can receive VPC Flow Logs for network-traffic analysis. CloudWatch also monitors supported VPC resources and provides network observability features for investigating connectivity and performance.
- **[Amazon WorkSpaces](https://blowstack.com/tools/cloud-services-hub/amazon-workspaces)**: CloudWatch collects WorkSpaces availability, connection, and session-performance metrics. Dashboards and alarms help identify unhealthy desktops and connection problems.
- **[Amazon WorkSpaces Applications](https://blowstack.com/tools/cloud-services-hub/amazon-appstream-2)**: CloudWatch collects WorkSpaces Applications fleet-capacity and streaming-session metrics. You can alarm on insufficient session capacity or failed user connections.
- **[Amazon WorkSpaces Secure Browser](https://blowstack.com/tools/cloud-services-hub/amazon-workspaces-web)**: CloudWatch collects WorkSpaces Secure Browser portal and session metrics. These help monitor session demand and identify connection or availability problems.
- **[AWS Amplify](https://blowstack.com/tools/cloud-services-hub/aws-amplify)**: CloudWatch collects Amplify Hosting request and error metrics and receives supported application runtime logs. You can investigate server-side rendering failures and monitor hosted applications.
- **[AWS App Runner](https://blowstack.com/tools/cloud-services-hub/aws-app-runner)**: CloudWatch receives App Runner service metrics, deployment logs, and application logs. You can monitor request latency, HTTP errors, and container resource utilization.
- **[AWS AppConfig](https://blowstack.com/tools/cloud-services-hub/aws-appconfig)**: AppConfig monitors configured CloudWatch alarms during configuration deployments and can automatically roll back when an alarm enters the ALARM state. This can stop a configuration rollout that increases application errors.
- **[AWS Application Migration Service](https://blowstack.com/tools/cloud-services-hub/aws-application-migration-service)**: CloudWatch receives Application Migration Service replication metrics, including replication lag and backlog. These help identify source servers that are not keeping up with migration replication.
- **[AWS AppSync](https://blowstack.com/tools/cloud-services-hub/aws-appsync)**: CloudWatch collects AppSync request, latency, and error metrics and receives configured GraphQL execution logs. Enhanced metrics provide additional visibility into resolvers and data sources.
- **[AWS Audit Manager](https://blowstack.com/tools/cloud-services-hub/aws-audit-manager)**: Audit Manager can collect CloudWatch alarm information as automated evidence. This lets assessments document whether monitored resources have the required operational controls.
- **[AWS Auto Scaling](https://blowstack.com/tools/cloud-services-hub/aws-auto-scaling)**: CloudWatch metrics and alarms support scaling plans and target-tracking policies managed by AWS Auto Scaling. Capacity can adjust automatically as the selected utilization metric changes.
- **[AWS Backup](https://blowstack.com/tools/cloud-services-hub/aws-backup)**: CloudWatch collects Backup job and recovery-point metrics and receives supported backup and restore logs. Alarms can identify failed backup jobs or unsuccessful restore tests.
- **[AWS Batch](https://blowstack.com/tools/cloud-services-hub/aws-batch)**: CloudWatch Logs receives Batch job container output through configured logging drivers. Container Insights can provide additional visibility into supported Batch compute environments.
- **[AWS Billing and Cost Management](https://blowstack.com/tools/cloud-services-hub/aws-billing-and-cost-management)**: CloudWatch exposes estimated-charge metrics when billing alerts are enabled. You can create billing alarms that notify an SNS topic when estimated charges exceed a threshold.
- **[AWS Certificate Manager (ACM)](https://blowstack.com/tools/cloud-services-hub/aws-certificate-manager-(acm))**: CloudWatch receives ACM certificate-expiration metrics, including DaysToExpiry. Alarms can warn about certificates approaching expiration.
- **[AWS Chatbot](https://blowstack.com/tools/cloud-services-hub/aws-chatbot)**: CloudWatch alarm notifications can reach configured chat channels through AWS Chatbot and SNS. Teams can receive operational alerts alongside their incident discussions.
- **[AWS Clean Rooms](https://blowstack.com/tools/cloud-services-hub/aws-clean-rooms)**: CloudWatch Logs receives enabled Clean Rooms query logs. These records help investigate failed analyses and inspect query execution activity.
- **[AWS Client VPN](https://blowstack.com/tools/cloud-services-hub/aws-client-vpn)**: CloudWatch collects Client VPN endpoint metrics and receives enabled client connection logs. You can investigate failed connections and monitor active VPN usage.
- **[AWS Cloud Map](https://blowstack.com/tools/cloud-services-hub/aws-cloud-map)**: CloudWatch receives supported Cloud Map service-discovery metrics. These help monitor discovery requests and identify errors or throttling.
- **[AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation)**: CloudFormation provisions CloudWatch resources such as alarms, dashboards, log groups, and subscription filters. CloudFormation rollback triggers can also monitor CloudWatch alarms during stack operations.
- **[AWS CloudHSM](https://blowstack.com/tools/cloud-services-hub/aws-cloudhsm)**: CloudWatch collects CloudHSM metrics for HSM health, capacity, and activity. CloudHSM also publishes HSM audit logs to CloudWatch Logs.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: CloudTrail records supported CloudWatch API activity for auditing. Trails can also deliver AWS API activity to CloudWatch Logs, where metric filters and alarms can detect selected security events.
- **[AWS CodeBuild](https://blowstack.com/tools/cloud-services-hub/aws-codebuild)**: CloudWatch receives CodeBuild build logs and metrics for build duration, success, and failure. Logs Insights can help investigate recurring build errors.
- **[AWS CodeDeploy](https://blowstack.com/tools/cloud-services-hub/aws-codedeploy)**: CodeDeploy can monitor CloudWatch alarms during deployments and stop or roll back deployments when configured alarms trigger. This helps prevent a release from continuing after application health deteriorates.
- **[AWS CodePipeline](https://blowstack.com/tools/cloud-services-hub/aws-codepipeline)**: CodePipeline stage conditions can evaluate CloudWatch alarms before allowing a release to proceed. A triggered alarm can block a stage or cause configured rollback behavior.
- **[AWS Compute Optimizer](https://blowstack.com/tools/cloud-services-hub/aws-compute-optimizer)**: Compute Optimizer analyzes CloudWatch utilization metrics to generate resource-sizing recommendations. Additional memory metrics collected by the CloudWatch agent can improve supported recommendations.
- **[AWS Config](https://blowstack.com/tools/cloud-services-hub/aws-config)**: Config records supported CloudWatch resource configurations and evaluates rules concerning alarms and log groups. CloudWatch also receives Config operational metrics for monitoring configuration recording and delivery.
- **[AWS Control Tower](https://blowstack.com/tools/cloud-services-hub/aws-control-tower)**: Control Tower configures CloudWatch Logs delivery for its supported organization-level CloudTrail logging setup. This supports centralized monitoring of API activity across governed accounts.
- **[AWS Data Exchange](https://blowstack.com/tools/cloud-services-hub/aws-data-exchange)**: CloudWatch receives supported Data Exchange API asset metrics. Providers can monitor subscriber API request activity, latency, and errors.
- **[AWS Database Migration Service (AWS DMS)](https://blowstack.com/tools/cloud-services-hub/aws-database-migration-service-(aws-dms))**: CloudWatch collects DMS replication-instance and task metrics and receives enabled task logs. You can monitor replication latency, resource pressure, and migration errors.
- **[AWS DataSync](https://blowstack.com/tools/cloud-services-hub/aws-datasync)**: CloudWatch collects DataSync transfer metrics and receives configured task logs. These help investigate skipped files, verification failures, and transfer-performance problems.
- **[AWS DeepRacer](https://blowstack.com/tools/cloud-services-hub/aws-deepracer)**: CloudWatch Logs receives DeepRacer training and simulation logs. These help analyze reward behavior and troubleshoot reinforcement-learning training runs.
- **[AWS DevOps Agent](https://blowstack.com/tools/cloud-services-hub/aws-devops-agent)**: CloudWatch telemetry can supply operational evidence to DevOps Agent through configured observability access. The agent can use relevant metrics, logs, and traces when investigating incidents.
- **[AWS Direct Connect](https://blowstack.com/tools/cloud-services-hub/aws-direct-connect)**: CloudWatch collects Direct Connect connection and virtual-interface metrics, including traffic rates and connection state. Alarms can detect link failures or approaching bandwidth limits.
- **[AWS Directory Service](https://blowstack.com/tools/cloud-services-hub/aws-directory-service)**: CloudWatch Logs can receive forwarded AWS Managed Microsoft AD security logs. CloudWatch also collects supported directory performance metrics for monitoring directory health.
- **[AWS Distro for OpenTelemetry](https://blowstack.com/tools/cloud-services-hub/aws-distro-for-opentelemetry)**: CloudWatch receives metrics and logs through supported AWS Distro for OpenTelemetry collectors and exporters. Instrumented applications can use this collection path for Container Insights and application observability.
- **[AWS Elastic Beanstalk](https://blowstack.com/tools/cloud-services-hub/aws-elastic-beanstalk)**: CloudWatch receives Elastic Beanstalk environment metrics, enhanced-health metrics, and configured instance logs. Alarms can detect unhealthy deployments or application-resource pressure.
- **[AWS Elastic Disaster Recovery](https://blowstack.com/tools/cloud-services-hub/aws-elastic-disaster-recovery)**: CloudWatch receives Elastic Disaster Recovery replication metrics such as lag and backlog. You can alarm when replication falls behind recovery objectives.
- **[AWS Entity Resolution](https://blowstack.com/tools/cloud-services-hub/aws-entity-resolution)**: CloudWatch receives supported Entity Resolution workflow metrics. These help track processing activity and identify workflow execution failures.
- **[AWS Fargate](https://blowstack.com/tools/cloud-services-hub/aws-fargate)**: CloudWatch collects metrics and logs from workloads running on Fargate through ECS or EKS integrations. Container Insights adds task or pod resource telemetry without requiring management of underlying hosts.
- **[AWS Fault Injection Service](https://blowstack.com/tools/cloud-services-hub/aws-fault-injection-simulator-(aws-fis))**: Fault Injection Service uses CloudWatch alarms as experiment stop conditions. If an alarm indicates unacceptable application impact, the experiment stops automatically.
- **[AWS Firewall Manager](https://blowstack.com/tools/cloud-services-hub/aws-firewall-manager)**: CloudWatch receives Firewall Manager policy-compliance metrics. Alarms can identify resources that fall out of compliance with centrally managed security policies.
- **[AWS Global Accelerator](https://blowstack.com/tools/cloud-services-hub/aws-global-accelerator)**: CloudWatch collects Global Accelerator traffic, connection, and endpoint-health metrics. These help identify unhealthy endpoints and changes in accelerator traffic.
- **[AWS Glue](https://blowstack.com/tools/cloud-services-hub/aws-glue)**: CloudWatch receives Glue job logs, job metrics, and observability metrics. You can investigate failed ETL stages, data skew, and resource bottlenecks.
- **[AWS Glue DataBrew](https://blowstack.com/tools/cloud-services-hub/aws-glue-databrew)**: CloudWatch Logs receives DataBrew job execution logs. These help diagnose recipe-job and profile-job failures.
- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: IAM policies control access to CloudWatch metrics, dashboards, alarms, and logs. IAM roles also authorize services and agents to publish telemetry or perform configured alarm actions.
- **[AWS IoT Core](https://blowstack.com/tools/cloud-services-hub/aws-iot-core)**: CloudWatch collects IoT Core connection, messaging, and rules-engine metrics and receives enabled IoT logs. IoT rules can also send selected messages directly to CloudWatch Logs or CloudWatch metrics.
- **[AWS IoT Device Defender](https://blowstack.com/tools/cloud-services-hub/aws-iot-device-defender)**: CloudWatch receives IoT Device Defender audit and Detect metrics. Alarms can notify operators about audit failures or abnormal device behavior.
- **[AWS IoT Device Management](https://blowstack.com/tools/cloud-services-hub/aws-iot-device-management)**: CloudWatch receives supported IoT Device Management job and fleet-indexing metrics. Fleet metrics can publish aggregated device information to CloudWatch for dashboards and alarms.
- **[AWS IoT Greengrass](https://blowstack.com/tools/cloud-services-hub/aws-iot-greengrass)**: The Greengrass log manager component can upload component logs to CloudWatch Logs. A CloudWatch metrics component can publish device and application metrics from Greengrass cores.
- **[AWS IoT SiteWise](https://blowstack.com/tools/cloud-services-hub/aws-iot-sitewise)**: CloudWatch receives SiteWise ingestion, query, and processing metrics and configured service logs. These help identify industrial-data ingestion failures and asset-processing problems.
- **[AWS Key Management Service (AWS KMS)](https://blowstack.com/tools/cloud-services-hub/aws-key-management-service-(aws-kms))**: CloudWatch Logs can encrypt log-group data with customer-managed KMS keys. CloudWatch alarm actions can also use KMS-encrypted SNS topics when the necessary key permissions are configured.
- **[AWS Lake Formation](https://blowstack.com/tools/cloud-services-hub/aws-lake-formation)**: CloudWatch receives supported Lake Formation operational metrics. These help monitor data-access activity and identify errors in permission-controlled access.
- **[AWS Launch Wizard](https://blowstack.com/tools/cloud-services-hub/aws-launch-wizard)**: Launch Wizard can configure CloudWatch Application Insights for supported deployed applications. CloudWatch then collects application telemetry and helps detect problems in the deployed workload.
- **[AWS License Manager](https://blowstack.com/tools/cloud-services-hub/aws-license-manager)**: CloudWatch receives License Manager license-usage metrics. You can create alarms when tracked license consumption approaches configured limits.
- **[AWS Managed Services (AMS)](https://blowstack.com/tools/cloud-services-hub/aws-managed-services-(ams))**: AMS uses CloudWatch metrics, logs, and alarms to monitor managed resources. Alarm events feed its operational monitoring and incident-management processes.
- **[AWS Network Firewall](https://blowstack.com/tools/cloud-services-hub/aws-network-firewall)**: CloudWatch collects Network Firewall traffic and rule-action metrics and can receive configured flow, alert, and TLS logs. These support investigation of blocked traffic and suspicious network activity.
- **[AWS Organizations](https://blowstack.com/tools/cloud-services-hub/aws-organizations)**: CloudWatch uses Organizations integrations for organization-wide telemetry configuration and cross-account observability onboarding. Administrators can apply supported observability settings across member accounts.
- **[AWS Outposts](https://blowstack.com/tools/cloud-services-hub/aws-outposts)**: CloudWatch receives Outposts capacity and connectivity metrics. You can monitor available local capacity and service-link health.
- **[AWS Private Certificate Authority](https://blowstack.com/tools/cloud-services-hub/aws-private-certificate-authority)**: CloudWatch collects Private CA certificate-issuance and operational metrics. These support monitoring of private certificate authority activity and failures.
- **[AWS PrivateLink](https://blowstack.com/tools/cloud-services-hub/aws-privatelink)**: CloudWatch supports PrivateLink interface endpoints for private access to supported monitoring and logging APIs. CloudWatch also collects PrivateLink endpoint and endpoint-service metrics.
- **[AWS Resilience Hub](https://blowstack.com/tools/cloud-services-hub/aws-resilience-hub)**: Resilience Hub recommends CloudWatch alarms for application resilience monitoring and provides templates to deploy them. It can assess whether relevant alarms are implemented for an application.
- **[AWS Resource Groups and Tag Editor](https://blowstack.com/tools/cloud-services-hub/aws-resource-groups-and-tag-editor)**: CloudWatch Application Insights can use Resource Groups to identify the resources belonging to an application. It then configures monitoring and correlates telemetry across those resources.
- **[AWS Security Hub](https://blowstack.com/tools/cloud-services-hub/aws-security-hub)**: Security Hub security controls evaluate supported CloudWatch configurations, including alarm actions and log-group retention. Findings identify monitoring settings that do not meet the selected security standards.
- **[AWS Security Token Service (AWS STS)](https://blowstack.com/tools/cloud-services-hub/aws-security-token-service-(aws-sts))**: CloudWatch cross-account dashboard access uses STS role assumption to read authorized telemetry in another account. Temporary credentials preserve the permissions defined by the cross-account role.
- **[AWS Service Catalog](https://blowstack.com/tools/cloud-services-hub/aws-service-catalog)**: CloudWatch Application Insights integrates with Service Catalog AppRegistry applications to discover application resources and configure monitoring. This links provisioned application inventories with operational dashboards and problem detection.
- **[AWS Shield](https://blowstack.com/tools/cloud-services-hub/aws-shield)**: CloudWatch receives Shield Advanced DDoS detection and attack metrics. Alarms can notify responders when an attack is detected against a protected resource.
- **[AWS Site-to-Site VPN](https://blowstack.com/tools/cloud-services-hub/aws-site-to-site-vpn)**: CloudWatch collects VPN tunnel state and traffic metrics and can receive enabled VPN tunnel logs. These help diagnose tunnel negotiation failures and connectivity interruptions.
- **[AWS Step Functions](https://blowstack.com/tools/cloud-services-hub/aws-step-functions)**: CloudWatch collects Step Functions execution metrics and receives configured workflow execution logs. You can alarm on failed or timed-out executions and inspect state-level activity.
- **[AWS Storage Gateway](https://blowstack.com/tools/cloud-services-hub/aws-storage-gateway)**: CloudWatch collects Storage Gateway throughput, cache, storage, and health metrics and receives supported gateway logs. Alarms can identify cache pressure or gateway errors.
- **[AWS Systems Manager](https://blowstack.com/tools/cloud-services-hub/aws-systems-manager)**: CloudWatch alarms can create Systems Manager OpsItems or initiate supported automation actions. Systems Manager can install and configure the CloudWatch agent and send command or session logs to CloudWatch Logs.
- **[AWS Transfer Family](https://blowstack.com/tools/cloud-services-hub/aws-transfer-family)**: CloudWatch collects Transfer Family activity metrics and receives configured server, connector, and workflow logs. These help investigate authentication failures and unsuccessful file transfers.
- **[AWS Transit Gateway](https://blowstack.com/tools/cloud-services-hub/aws-transit-gateway)**: CloudWatch collects Transit Gateway and attachment metrics for traffic and packet drops. Transit Gateway Flow Logs can also be delivered to CloudWatch Logs for traffic analysis.
- **[AWS Trusted Advisor](https://blowstack.com/tools/cloud-services-hub/aws-trusted-advisor)**: CloudWatch receives supported Trusted Advisor check-status metrics. Alarms can notify operators when monitored checks report warning or error conditions.
- **[AWS User Notifications](https://blowstack.com/tools/cloud-services-hub/aws-user-notifications)**: User Notifications can select CloudWatch alarm state-change events and deliver notifications through configured channels. Alarm thresholds remain managed in CloudWatch while notification routing is managed separately.
- **[AWS Verified Access](https://blowstack.com/tools/cloud-services-hub/aws-verified-access)**: CloudWatch Logs can receive Verified Access access logs, and CloudWatch collects supported endpoint metrics. These help investigate denied requests and application-access failures.
- **[AWS WAF](https://blowstack.com/tools/cloud-services-hub/aws-waf)**: CloudWatch collects WAF allowed, blocked, and counted request metrics and can receive web ACL logs. You can use dashboards and Logs Insights to investigate traffic matched by particular rules.
- **[AWS X-Ray](https://blowstack.com/tools/cloud-services-hub/aws-x-ray)**: CloudWatch integrates X-Ray traces with application metrics and logs for distributed troubleshooting. Application Signals and related views can connect elevated latency or errors with affected service traces.
- **[EC2 Image Builder](https://blowstack.com/tools/cloud-services-hub/ec2-image-builder)**: CloudWatch Logs receives Image Builder build and test execution logs. These help diagnose failed image components and validation steps.
- **[Elastic Load Balancing (ELB)](https://blowstack.com/tools/cloud-services-hub/elastic-load-balancing-(elb))**: CloudWatch collects load-balancer metrics such as request counts, target response times, connection errors, and healthy-target counts. Alarms can identify unhealthy targets or increased application failures.
- **[Red Hat OpenShift Service on AWS (ROSA)](https://blowstack.com/tools/cloud-services-hub/red-hat-openshift-service-on-aws-(rosa))**: CloudWatch Logs can receive ROSA application, infrastructure, and audit logs through configured OpenShift log forwarding. This centralizes cluster logs for retention, searches, and alarms.
- **[VMware Cloud on AWS](https://blowstack.com/tools/cloud-services-hub/vmware-cloud-on-aws)**: The CloudWatch agent can collect operating-system metrics and logs from supported virtual machines running in VMware Cloud on AWS. This provides guest-level monitoring alongside telemetry from other AWS workloads.

## What is Amazon CloudWatch

Amazon CloudWatch is a versatile monitoring and observability service designed by AWS (Amazon Web Services) to help IT professionals, developers, site reliability engineers (SREs), and DevOps teams track and manage the health, performance, and overall activity of their AWS resources and applications, both on AWS infrastructure and on-premises. Serving as a central component of AWS's extensive ecosystem, CloudWatch provides a detailed view into operational health in real-time by collecting monitoring and operational data in the form of logs, metrics, and events, making it an indispensable tool for maintaining the performance and smooth operation of applications and services.

At its core, CloudWatch aggregates data in a detailed, programmatic manner, which enables users to gain insights, set alarms, visualize logs and metrics, troubleshoot issues, and discover patterns. This comprehensive coverage allows for the proactive management of the operational health of AWS resources such as Amazon EC2 instances, Amazon DynamoDB tables, and Amazon RDS DB instances, among others. One of the pivotal features of CloudWatch is its ability to monitor resource utilization, system-wide performance changes, and operational health in a unified manner. For example, it can track CPU usage, disk reads and writes, and network traffic across a fleet of EC2 instances. This capacity for close monitoring aids in the prevention of potential issues by setting alarms that notify users when thresholds are crossed or unexpected patterns emerge.

Application Signals provides standardized application metrics and application-centric health views without requiring custom instrumentation. Its optional complete transaction-span visibility adds search and analytics beyond sampled transactions.

Container Insights with OpenTelemetry collects EKS metrics through open-source receivers and publishes them through the OTLP endpoint. It provides container-level CPU, memory, disk, network, and GPU visibility, with PromQL queries and automatic dashboards.

Classic Container Insights offers an optional enhanced-observability mode with container-level ECS and EKS metrics, Kubernetes state metrics, and EKS control-plane metrics. Without enhanced observability, it provides aggregated cluster- and service-level metrics.

Database Insights Standard Mode combines database metrics, SQL query analytics, and logs for Aurora and RDS. It includes up to seven days of detailed database and per-query metric history, with configurable retention from one to 24 months beyond that.

Cross-account observability lets a monitoring account view and query metrics and logs from source accounts without copying the data.

CloudWatch Synthetics runs customizable endpoint tests around the clock and alerts when behavior differs from expectations, covering checks such as availability, latency, transactions, and multi-step user workflows.

Real User Monitoring covers both web and mobile applications: web telemetry includes page-load delays and web vitals, while mobile telemetry uses OpenTelemetry spans and events.

X-Ray traces provide an end-to-end view of requests traveling through distributed applications, helping developers analyze and debug production behavior.

PromQL alarms have a non-adjustable quota of 15,000 per account per Region.

CloudWatch Omni provides an additional observability experience through an IDE extension for VS Code, Kiro, and Cursor and a standalone web UI for operations teams. Web users authenticate with enterprise SSO through IAM Identity Center and do not need AWS credentials, AWS Console access, or an AWS account.

Moreover, CloudWatch is not limited to predefined metrics and logs; it also allows users to publish their own custom metrics, offering flexibility that covers a wide range of use cases, from tracking application-level operations to specific business indicators. Through its dashboard, CloudWatch enables users to visualize these metrics in a comprehensible manner, facilitating easy digestion of data points and trends over time. This can be crucial for capacity planning, ensuring that applications and services are adequately provisioned to meet demand without overspending.

Alongside classic CloudWatch metrics, CloudWatch natively ingests OpenTelemetry metrics and supports PromQL queries, allowing existing Prometheus dashboards and alerting workflows to use their existing queries.

Metric centralization creates physical metric copies in a destination account so alarms, dashboards, and queries can operate locally without cross-account calls.

A single cross-account metric stream can include metrics from multiple AWS accounts within one AWS Region.

In addition to monitoring, CloudWatch Logs provide a centralized repository for storing log information, including system logs, application logs, and any custom log data, with the ability to define filters and set alarms on log patterns. This capability is integral for troubleshooting, as it aids in pinpointing the root causes of operational problems quickly. CloudWatch Events (now part of Amazon EventBridge) further expands its capabilities by allowing AWS resources to automatically react to system-wide changes through a stream of real-time data from AWS services, transforming and responding dynamically to operational changes across the AWS landscape.

Logs Insights supports log queries with aggregations, filters, and regular expressions, as well as time-series visualization, drill-down into individual events, and export of query results to CloudWatch dashboards.

Contributor Insights continuously analyzes time-series data to identify the top contributors influencing system performance.

To sum up, Amazon CloudWatch plays a critical role in ensuring that AWS-based applications run smoothly and efficiently. By providing detailed insights into applications and system operation, it not only helps in proactive issue detection and resolution but also aids in understanding and optimizing system performance, leading to more robust, reliable, and efficient application deployments. Its integration capabilities, coupled with the depth of insights it provides, make CloudWatch a cornerstone in managing cloud operations effectively.

## Concepts related to Amazon CloudWatch

- [A/B Testing](https://blowstack.com/tools/cloud-concepts-hub/ab-testing): A/B testing is a controlled experiment that randomly assigns comparable users or requests to two variants and measures which performs better against predefined criteria.
- [Access Control](https://blowstack.com/tools/cloud-concepts-hub/access-control): Access control determines which identities can perform which actions on which resources under specified conditions.
- [ADKAR Model](https://blowstack.com/tools/cloud-concepts-hub/adkar-model): The ADKAR Model is Prosci’s individual change-management framework for building Awareness, Desire, Knowledge, Ability, and Reinforcement to sustain organizational change.
- [Adversarial Robustness](https://blowstack.com/tools/cloud-concepts-hub/adversarial-robustness): Adversarial robustness is an AI system’s ability to maintain acceptable behavior when attackers deliberately manipulate its inputs, data, or interactions.
- [Agentic AI](https://blowstack.com/tools/cloud-concepts-hub/agentic-ai): Agentic AI is an approach to building AI systems that pursue goals by selecting actions, using tools, and adapting their next steps within defined boundaries.
- [Agile Development](https://blowstack.com/tools/cloud-concepts-hub/agile-development): Agile development is an iterative, incremental approach to software delivery that adapts plans through frequent feedback, collaboration, and working software.
- [AI Agents](https://blowstack.com/tools/cloud-concepts-hub/ai-agents): AI agents are software systems that use artificial intelligence to select and carry out actions toward a goal within defined permissions and constraints.
- [Algorithmic Bias](https://blowstack.com/tools/cloud-concepts-hub/algorithmic-bias): Algorithmic bias is a systematic tendency of an automated system to produce unfairly favorable or unfavorable outcomes for particular people or groups.
- [All-at-Once Deployment](https://blowstack.com/tools/cloud-concepts-hub/all-at-once-deployment): All-at-once deployment releases a new application version to the entire targeted environment in a single deployment batch rather than through staged updates.
- [Anomaly Detection](https://blowstack.com/tools/cloud-concepts-hub/anomaly-detection): Anomaly detection identifies data or events that deviate from expected patterns and warrant investigation.
- [Answer Relevance](https://blowstack.com/tools/cloud-concepts-hub/answer-relevance): Answer relevance measures how directly and appropriately a generated response addresses a user's question, intent, and conversational context.
- [API Gateway Pattern](https://blowstack.com/tools/cloud-concepts-hub/api-gateway-pattern): The API Gateway Pattern places a controlled entry point between clients and backend services to centralize request routing and shared API policies.
- [API Versioning](https://blowstack.com/tools/cloud-concepts-hub/api-versioning): API versioning is the practice of identifying and managing distinct API contracts so interfaces can evolve without unexpectedly breaking consumers.
- [Approximate Nearest Neighbor Search](https://blowstack.com/tools/cloud-concepts-hub/approximate-nearest-neighbor-search): Approximate Nearest Neighbor Search uses indexes to find vectors close to a query vector while trading guaranteed exact results for lower search cost and latency.
- [Architecture Reviews](https://blowstack.com/tools/cloud-concepts-hub/architecture-reviews): Architecture reviews are structured evaluations of a workload’s design and operation against business requirements, architectural principles, and established best practices.
- [Asynchronous Inference](https://blowstack.com/tools/cloud-concepts-hub/asynchronous-inference): Asynchronous inference is a model-serving pattern that accepts prediction requests without keeping the caller waiting for the model’s result.
- [Automation Bias](https://blowstack.com/tools/cloud-concepts-hub/automation-bias): Automation bias is the tendency to trust automated recommendations or outputs too readily, reducing independent judgment and verification.
- [AWS Cloud Adoption Framework (AWS CAF)](https://blowstack.com/tools/cloud-concepts-hub/aws-cloud-adoption-framework-(aws-caf)): AWS Cloud Adoption Framework (AWS CAF) is guidance for building the organizational and technical capabilities needed to adopt cloud technology and achieve business outcomes.
- [Backpressure](https://blowstack.com/tools/cloud-concepts-hub/backpressure): Backpressure is feedback from a constrained downstream component that causes upstream components to slow or pause production.
- [Benefits Realization](https://blowstack.com/tools/cloud-concepts-hub/benefits-realization): Benefits Realization is the process of turning an investment’s intended outcomes into measurable, sustained business value.
- [Bias-Variance Tradeoff](https://blowstack.com/tools/cloud-concepts-hub/bias-variance-tradeoff): The bias-variance tradeoff is the balance between a model’s systematic prediction error and its sensitivity to the training data, which influences how well it generalizes.
- [Blue-Green Deployment](https://blowstack.com/tools/cloud-concepts-hub/blue-green-deployment): Blue-green deployment releases a new application version into a separate environment and then redirects production traffic from the current environment to the new one.
- [Blue-Green Deployments](https://blowstack.com/tools/cloud-concepts-hub/blue-green-deployments): Blue-green deployments release application changes by preparing a separate production-ready environment and switching traffic from the current environment to the new one.
- [Canary Deployment](https://blowstack.com/tools/cloud-concepts-hub/canary-deployment): Canary deployment releases a new application or model version to a small portion of production traffic before expanding exposure after validation.
- [Canary Testing](https://blowstack.com/tools/cloud-concepts-hub/canary-testing): Canary testing validates a candidate configuration by exposing it to a small share of production traffic before deciding whether to expand or reverse the rollout.
- [Capability Maturity Model](https://blowstack.com/tools/cloud-concepts-hub/capability-maturity-model): A Capability Maturity Model is a framework for assessing how consistently an organization performs a capability and identifying the improvements needed to make it repeatable, measurable, and continuously optimized.
- [Capacity Planning](https://blowstack.com/tools/cloud-concepts-hub/capacity-planning): Capacity planning is the process of estimating workload demand and arranging sufficient resources to meet performance, growth, and resilience requirements within cost constraints.
- [Catastrophic Forgetting](https://blowstack.com/tools/cloud-concepts-hub/catastrophic-forgetting): Catastrophic forgetting is the substantial loss of previously learned capabilities when a model is trained on new tasks or data.
- [Champion/Challenger Testing](https://blowstack.com/tools/cloud-concepts-hub/championchallenger-testing): Champion/challenger testing compares a currently accepted model with candidate replacements to determine whether a challenger should become the new production standard.
- [Change Impact Assessment](https://blowstack.com/tools/cloud-concepts-hub/change-impact-assessment): Change Impact Assessment identifies how a proposed change will affect people, processes, technology, and business outcomes so teams can prepare, communicate, and manage the transition.
- [Chaos Engineering](https://blowstack.com/tools/cloud-concepts-hub/chaos-engineering): Chaos engineering is the practice of running controlled failure experiments to test how systems and operational teams respond to disruption.
- [CI/CD](https://blowstack.com/tools/cloud-concepts-hub/cicd): CI/CD is a software engineering approach that continuously integrates code changes and automates their validation and delivery or deployment.
- [Circuit Breaker](https://blowstack.com/tools/cloud-concepts-hub/circuit-breaker): A circuit breaker is a resilience pattern that temporarily blocks calls to a failing dependency and permits controlled probes before restoring normal traffic.
- [Classification Metrics](https://blowstack.com/tools/cloud-concepts-hub/classification-metrics): Classification metrics quantify how well a model assigns examples to discrete categories by comparing its predictions with known labels.
- [Code Refactoring](https://blowstack.com/tools/cloud-concepts-hub/code-refactoring): Code refactoring is the restructuring of existing source code to improve its internal design without changing its externally observable behavior.
- [Composite Availability](https://blowstack.com/tools/cloud-concepts-hub/composite-availability): Composite availability is the end-to-end availability of a system determined by its required dependencies, redundant components, and failure relationships.
- [Concurrency](https://blowstack.com/tools/cloud-concepts-hub/concurrency): Concurrency is the ability of a system to keep multiple tasks in progress during overlapping periods of time.
- [Connection Pooling](https://blowstack.com/tools/cloud-concepts-hub/connection-pooling): Connection pooling maintains a reusable set of network connections so applications can borrow them instead of establishing a new connection for every operation.
- [Content-Based Routing](https://blowstack.com/tools/cloud-concepts-hub/content-based-routing): Content-based routing directs a request or message to a destination by evaluating its payload, attributes, or derived meaning.
- [Context Pruning](https://blowstack.com/tools/cloud-concepts-hub/context-pruning): Context pruning is the selective removal of low-value information from a foundation model’s input while preserving the information needed to complete the task accurately.
- [Cost-Benefit Analysis](https://blowstack.com/tools/cloud-concepts-hub/cost-benefit-analysis): Cost-benefit analysis compares the expected benefits of a proposed solution with its full costs and risks to determine whether it is worth implementing.
- [Data Classification](https://blowstack.com/tools/cloud-concepts-hub/data-classification): Data classification is the process of categorizing information by sensitivity, business impact, and handling requirements so that appropriate security controls can be applied.
- [Data Drift](https://blowstack.com/tools/cloud-concepts-hub/data-drift): Data drift is a change in the statistical distribution of data over time or relative to a reference dataset that can affect a machine learning model’s performance.
- [Data Loss Prevention](https://blowstack.com/tools/cloud-concepts-hub/data-loss-prevention): Data Loss Prevention is the use of policies and controls to detect sensitive information and prevent its unauthorized disclosure, transfer, or use.
- [Data Profiling](https://blowstack.com/tools/cloud-concepts-hub/data-profiling): Data profiling is the systematic examination of a dataset’s structure, values, distributions, and relationships to understand its characteristics and identify potential quality problems.
- [Data Skew](https://blowstack.com/tools/cloud-concepts-hub/data-skew): Data skew is an uneven distribution of data or data-processing work across partitions, tasks, or nodes in a distributed system.
- [Dependency Mapping](https://blowstack.com/tools/cloud-concepts-hub/dependency-mapping): Dependency mapping identifies and documents the relationships that applications, infrastructure, data, and operational processes rely on to function.
- [Deployment Rollback](https://blowstack.com/tools/cloud-concepts-hub/deployment-rollback): Deployment rollback restores a previously validated application, infrastructure, or model release when a new deployment fails or causes unacceptable behavior.
- [Differential Testing](https://blowstack.com/tools/cloud-concepts-hub/differential-testing): Differential testing compares the behavior of multiple implementations, versions, or configurations on the same inputs to identify meaningful discrepancies.
- [Distributed Tracing](https://blowstack.com/tools/cloud-concepts-hub/distributed-tracing): Distributed tracing follows a request across multiple application components to show how they interact, where time is spent, and where failures occur.
- [DNS Tunneling](https://blowstack.com/tools/cloud-concepts-hub/dns-tunneling): DNS tunneling carries non-DNS data inside DNS queries and responses, creating a communication channel through name-resolution infrastructure.
- [Elasticity](https://blowstack.com/tools/cloud-concepts-hub/elasticity): Elasticity is the ability to increase and decrease computing resources to match changes in workload demand.
- [End-to-End Testing](https://blowstack.com/tools/cloud-concepts-hub/end-to-end-testing): End-to-end testing validates a complete application journey, from its entry point through integrated components to the final response and observable effects.
- [Ensemble Learning](https://blowstack.com/tools/cloud-concepts-hub/ensemble-learning): Ensemble learning combines predictions or outputs from multiple models to produce a result that can outperform an individual model.
- [Environmental Sustainability](https://blowstack.com/tools/cloud-concepts-hub/environmental-sustainability): Environmental Sustainability is the practice of reducing the environmental impact of systems throughout their lifecycle while meeting required business and technical outcomes.
- [Epochs](https://blowstack.com/tools/cloud-concepts-hub/epochs): Epochs are complete passes through a training dataset, used to measure and control how long a machine learning model trains.
- [Error Budgets](https://blowstack.com/tools/cloud-concepts-hub/error-budgets): Error budgets quantify the amount of unreliability a service can tolerate within a defined period while still meeting its service-level objective.
- [EU AI Act](https://blowstack.com/tools/cloud-concepts-hub/eu-ai-act): The EU AI Act is a European Union regulation that establishes risk-based requirements for developing, supplying, and using artificial intelligence systems and general-purpose AI models.
- [Event-Driven Architecture](https://blowstack.com/tools/cloud-concepts-hub/event-driven-architecture): Event-driven architecture is a software design approach in which components publish events and other components react to them through loosely coupled communication.
- [Exception Handling](https://blowstack.com/tools/cloud-concepts-hub/exception-handling): Exception handling is the controlled detection and management of runtime failures so a program can recover, release resources, or terminate with useful diagnostic information.
- [Executive Sponsorship](https://blowstack.com/tools/cloud-concepts-hub/executive-sponsorship): Executive sponsorship is active, accountable support from a senior leader who authorizes resources, aligns stakeholders, and removes organizational barriers to a strategic initiative.
- [Factual Accuracy](https://blowstack.com/tools/cloud-concepts-hub/factual-accuracy): Factual accuracy is the degree to which an output’s verifiable claims agree with reliable evidence and the relevant real-world facts.
- [Feature Flags](https://blowstack.com/tools/cloud-concepts-hub/feature-flags): Feature flags are configurable controls that let applications enable, disable, or vary behavior without changing the deployed code.
- [Feedback Loops](https://blowstack.com/tools/cloud-concepts-hub/feedback-loops): Feedback loops are repeatable processes that use observations, user input, and outcomes to evaluate and improve a system’s behavior.
- [Fine-Tuning](https://blowstack.com/tools/cloud-concepts-hub/fine-tuning): Fine-tuning adapts a pretrained model to a particular task, domain, or behavior by performing additional training on selected data.
- [First-Mover Advantage](https://blowstack.com/tools/cloud-concepts-hub/first-mover-advantage): First-mover advantage is the competitive benefit an organization can gain by entering a market or applying a valuable innovation before its rivals.
- [Fluency](https://blowstack.com/tools/cloud-concepts-hub/fluency): Fluency is the degree to which generated language reads naturally, with correct grammar, clear phrasing, and smooth sentence flow.
- [Graceful Degradation](https://blowstack.com/tools/cloud-concepts-hub/graceful-degradation): Graceful degradation is the deliberate preservation of essential service when failures or resource constraints require reduced functionality, performance, or output quality.
- [Growth Mindset](https://blowstack.com/tools/cloud-concepts-hub/growth-mindset): A growth mindset is the belief that abilities can develop through effective practice, feedback, learning, and support rather than remaining fixed.
- [Guiding Coalition](https://blowstack.com/tools/cloud-concepts-hub/guiding-coalition): A guiding coalition is a cross-functional group with the authority, credibility, and commitment to lead organizational change and sustain adoption.
- [Health Checks](https://blowstack.com/tools/cloud-concepts-hub/health-checks): Health checks are automated tests that determine whether a component is functioning and suitable for receiving work.
- [High availability](https://blowstack.com/tools/cloud-concepts-hub/high-availability): High availability is the design and operation of a system to remain accessible and usable despite component failures or maintenance.
- [High performance](https://blowstack.com/tools/cloud-concepts-hub/high-performance): High performance is the ability of a system to meet workload-specific response-time and processing-rate targets under expected operating conditions.
- [Horizontal Scaling](https://blowstack.com/tools/cloud-concepts-hub/horizontal-scaling): Horizontal scaling adjusts capacity by adding or removing servers, containers, or other processing units that share a workload.
- [Hypothesis Testing](https://blowstack.com/tools/cloud-concepts-hub/hypothesis-testing): Hypothesis testing uses sample data to evaluate whether evidence supports rejecting a defined claim about a population or system.
- [Inference Latency](https://blowstack.com/tools/cloud-concepts-hub/inference-latency): Inference latency is the elapsed time a deployed AI model takes to return a prediction or generated response after receiving a request.
- [Integration Testing](https://blowstack.com/tools/cloud-concepts-hub/integration-testing): Integration testing verifies that connected software components exchange data and work together correctly across their interfaces.
- [Interpretability-Performance Tradeoff](https://blowstack.com/tools/cloud-concepts-hub/interpretability-performance-tradeoff): The interpretability-performance tradeoff is the balance between how readily people can understand a model’s decisions and how well the model meets predictive and operational requirements.
- [IOPS](https://blowstack.com/tools/cloud-concepts-hub/iops): IOPS, or input/output operations per second, measures the rate at which a storage system completes read and write operations.
- [ISO/IEC 23053](https://blowstack.com/tools/cloud-concepts-hub/isoiec-23053): ISO/IEC 23053 is an international standard that provides a framework for describing artificial intelligence systems that use machine learning, including their components and functions.
- [Iterative Prompt Refinement](https://blowstack.com/tools/cloud-concepts-hub/iterative-prompt-refinement): Iterative prompt refinement is the repeated process of testing and revising instructions, context, and examples to improve a foundation model’s responses against defined requirements.
- [Jailbreaking](https://blowstack.com/tools/cloud-concepts-hub/jailbreaking): Jailbreaking is the deliberate manipulation of a foundation model to bypass its safety safeguards or behavioral restrictions.
- [Key Performance Indicators](https://blowstack.com/tools/cloud-concepts-hub/key-performance-indicators): Key Performance Indicators are measurable values used to determine whether an application, process, or organization is achieving its most important objectives.
- [Labor Productivity](https://blowstack.com/tools/cloud-concepts-hub/labor-productivity): Labor productivity is the amount of useful output produced per unit of human labor, commonly measured as quality-adjusted output per labor hour.
- [Latency](https://blowstack.com/tools/cloud-concepts-hub/latency): Latency is the elapsed time between a defined starting event and the corresponding response, completion, or availability of a result.
- [Leading Indicators](https://blowstack.com/tools/cloud-concepts-hub/leading-indicators): Leading indicators are measurable signals that precede an outcome and help predict whether an AI initiative will achieve its intended business value.
- [Learning Rate Schedules](https://blowstack.com/tools/cloud-concepts-hub/learning-rate-schedules): Learning rate schedules are rules that adjust an optimizer’s learning rate during training to balance progress, stability, and convergence.
- [Link Aggregation](https://blowstack.com/tools/cloud-concepts-hub/link-aggregation): Link aggregation combines multiple physical Ethernet links into one logical interface to increase aggregate capacity and tolerate individual link failures.
- [Load Testing](https://blowstack.com/tools/cloud-concepts-hub/load-testing): Load testing evaluates how a system performs under a defined workload to verify capacity, response times, reliability, and scaling behavior.
- [Log Normalization](https://blowstack.com/tools/cloud-concepts-hub/log-normalization): Log normalization converts differently structured log records into a consistent schema and representation so they can be searched, compared, and correlated.
- [Low-Rank Adaptation](https://blowstack.com/tools/cloud-concepts-hub/low-rank-adaptation): Low-Rank Adaptation is a parameter-efficient fine-tuning technique that customizes a pretrained model by training small, low-rank weight updates while keeping the original model weights frozen.
- [Message Queuing](https://blowstack.com/tools/cloud-concepts-hub/message-queuing): Message queuing is asynchronous communication in which producers place messages in a queue for consumers to retrieve and process independently.
- [Metric Cardinality](https://blowstack.com/tools/cloud-concepts-hub/metric-cardinality): Metric cardinality is the number of distinct time series created by metric names and their unique combinations of dimension or label values.
- [Migration Phases](https://blowstack.com/tools/cloud-concepts-hub/migration-phases): Migration phases are the stages used to assess readiness, prepare a cloud foundation, and move workloads into a validated operating environment.
- [Minimum Viable Product](https://blowstack.com/tools/cloud-concepts-hub/minimum-viable-product): A Minimum Viable Product is the smallest usable version of a product that delivers core value and tests important assumptions with real users.
- [Model Cascading](https://blowstack.com/tools/cloud-concepts-hub/model-cascading): Model cascading is a staged inference strategy in which models handle requests sequentially, often using a smaller model first and escalating difficult cases to a more capable model.
- [Model Drift](https://blowstack.com/tools/cloud-concepts-hub/model-drift): Model drift is a change over time in production data or its relationship to outcomes that can reduce a machine learning model’s predictive reliability.
- [Model Evaluation](https://blowstack.com/tools/cloud-concepts-hub/model-evaluation): Model evaluation is the systematic assessment of an AI model’s quality, risks, operational performance, and suitability for an intended use.
- [Model Retraining](https://blowstack.com/tools/cloud-concepts-hub/model-retraining): Model retraining is the process of training a new version of an existing machine learning model using updated or revised data to maintain or improve its performance.
- [Model Robustness](https://blowstack.com/tools/cloud-concepts-hub/model-robustness): Model robustness is an AI model’s ability to maintain acceptable performance under noisy inputs, meaningful operating changes, and deliberate attempts to disrupt its behavior.
- [Model Routing](https://blowstack.com/tools/cloud-concepts-hub/model-routing): Model routing selects the most suitable AI model for each request or task using capability, quality, cost, latency, and operational constraints.
- [Network Address Translation](https://blowstack.com/tools/cloud-concepts-hub/network-address-translation): Network Address Translation rewrites IP addresses, and sometimes transport-layer ports, as packets move between networks.
- [NIST AI Risk Management Framework](https://blowstack.com/tools/cloud-concepts-hub/nist-ai-risk-management-framework): The NIST AI Risk Management Framework is a voluntary, technology-neutral framework for identifying, assessing, and managing AI risks throughout the AI lifecycle.
- [Nondeterminism](https://blowstack.com/tools/cloud-concepts-hub/nondeterminism): Nondeterminism is the property of a system that allows repeated executions with the same apparent inputs to produce different results.
- [Operational Readiness Reviews](https://blowstack.com/tools/cloud-concepts-hub/operational-readiness-reviews): Operational Readiness Reviews are structured, evidence-based assessments of whether a workload and its supporting teams are ready to operate safely and reliably in production.
- [Output Validation](https://blowstack.com/tools/cloud-concepts-hub/output-validation): Output validation checks generated or returned data against security, structural, and business rules before it is displayed, stored, or used to perform an action.
- [Packet Loss](https://blowstack.com/tools/cloud-concepts-hub/packet-loss): Packet loss is the failure of transmitted network packets to reach their intended destination.
- [Parallel Execution](https://blowstack.com/tools/cloud-concepts-hub/parallel-execution): Parallel execution runs independent tasks at the same time to reduce the elapsed time needed to complete a larger workflow.
- [Payback Period](https://blowstack.com/tools/cloud-concepts-hub/payback-period): Payback Period is the time required for an investment’s cumulative net benefits to recover its initial cost.
- [Performance Benchmarking](https://blowstack.com/tools/cloud-concepts-hub/performance-benchmarking): Performance benchmarking is the repeatable measurement of a system under defined workloads to compare its behavior against a baseline, alternative configuration, or performance target.
- [Performance Profiling](https://blowstack.com/tools/cloud-concepts-hub/performance-profiling): Performance profiling measures how an application spends time and consumes resources to identify bottlenecks and guide targeted improvements.
- [Phased Rollout](https://blowstack.com/tools/cloud-concepts-hub/phased-rollout): Phased rollout is the controlled introduction of a capability to progressively larger groups or workloads, using evidence from each stage to decide whether to expand.
- [Population Stability Index](https://blowstack.com/tools/cloud-concepts-hub/population-stability-index): Population Stability Index is a numerical measure of how much a feature or prediction-score distribution has shifted from a reference population.
- [Precision@k](https://blowstack.com/tools/cloud-concepts-hub/precision@k): Precision@k measures the fraction of the top k retrieved results that are relevant to a query.
- [Price-Performance Ratio](https://blowstack.com/tools/cloud-concepts-hub/price-performance-ratio): Price-Performance Ratio measures the cost of delivering a defined level of useful performance under specified workload conditions.
- [Prompt Chaining](https://blowstack.com/tools/cloud-concepts-hub/prompt-chaining): Prompt chaining decomposes a complex task into connected model interactions, passing selected outputs from earlier steps into later prompts.
- [Prompt Compression](https://blowstack.com/tools/cloud-concepts-hub/prompt-compression): Prompt compression reduces the tokens sent to a foundation model while preserving the instructions and information needed for an effective response.
- [Prompt Injection](https://blowstack.com/tools/cloud-concepts-hub/prompt-injection): Prompt injection is an attack in which untrusted input attempts to make a generative AI model follow instructions that conflict with the application's intended behavior or security policy.
- [Proof of Concept](https://blowstack.com/tools/cloud-concepts-hub/proof-of-concept): A proof of concept is a bounded experiment that tests whether an idea is feasible before an organization commits to broader implementation.
- [Psychological Safety](https://blowstack.com/tools/cloud-concepts-hub/psychological-safety): Psychological safety is a shared belief that people can ask questions, raise concerns, admit mistakes, and challenge ideas without humiliation or unfair punishment.
- [Publish-Subscribe Messaging](https://blowstack.com/tools/cloud-concepts-hub/publish-subscribe-messaging): Publish-subscribe messaging is an asynchronous communication pattern in which publishers send messages to a topic or broker that distributes them to interested subscribers.
- [Quality Gates](https://blowstack.com/tools/cloud-concepts-hub/quality-gates): Quality gates are explicit pass-or-fail checkpoints that use evidence to determine whether a change can advance through a delivery workflow.
- [ReAct](https://blowstack.com/tools/cloud-concepts-hub/react): ReAct is an agent design pattern that interleaves reasoning, tool actions, and observations so a foundation model can solve problems using external evidence.
- [Real-Time Inference](https://blowstack.com/tools/cloud-concepts-hub/real-time-inference): Real-time inference applies a deployed machine learning model to incoming requests and returns predictions quickly enough for an application to use immediately.
- [Recall@k](https://blowstack.com/tools/cloud-concepts-hub/recall@k): Recall@k measures the fraction of all known relevant items that a retrieval system returns within its first k results.
- [Red Teaming](https://blowstack.com/tools/cloud-concepts-hub/red-teaming): Red teaming is an authorized, adversarial assessment that simulates realistic attacks to uncover weaknesses in a system and its defenses.
- [Regression Testing](https://blowstack.com/tools/cloud-concepts-hub/regression-testing): Regression testing checks that changes to a system do not break previously accepted behavior or degrade established quality standards.
- [Resource Efficiency](https://blowstack.com/tools/cloud-concepts-hub/resource-efficiency): Resource efficiency is the practice of meeting workload requirements with the least necessary compute, storage, networking, and energy consumption.
- [Resource Utilization](https://blowstack.com/tools/cloud-concepts-hub/resource-utilization): Resource utilization is the amount or proportion of available computing capacity that a workload uses over a given period.
- [Response Streaming](https://blowstack.com/tools/cloud-concepts-hub/response-streaming): Response streaming delivers a response incrementally as output becomes available instead of waiting for the entire response to finish.
- [Return on Investment](https://blowstack.com/tools/cloud-concepts-hub/return-on-investment): Return on investment (ROI) measures the net financial benefit of an investment relative to its total cost over a defined period.
- [Right-Sizing](https://blowstack.com/tools/cloud-concepts-hub/right-sizing): Right-sizing is matching cloud resource types, configurations, and capacity to workload requirements without unnecessary cost or unacceptable performance risk.
- [Rightsizing](https://blowstack.com/tools/cloud-concepts-hub/rightsizing): Rightsizing is matching the type, size, and quantity of cloud resources to workload requirements while meeting performance and availability targets at an appropriate cost.
- [Risk Appetite](https://blowstack.com/tools/cloud-concepts-hub/risk-appetite): Risk appetite is the amount and type of risk an organization is willing to accept while pursuing its objectives.
- [Runbooks](https://blowstack.com/tools/cloud-concepts-hub/runbooks): Runbooks are documented, repeatable procedures that guide people or automation through operational tasks and recovery actions.
- [Schema Validation](https://blowstack.com/tools/cloud-concepts-hub/schema-validation): Schema validation checks whether data conforms to an explicitly defined structure, including required fields, data types, and permitted values.
- [Service Level Indicators](https://blowstack.com/tools/cloud-concepts-hub/service-level-indicators): Service Level Indicators are quantitative measurements of how well a service delivers the reliability and performance its users require.
- [Service Level Objectives](https://blowstack.com/tools/cloud-concepts-hub/service-level-objectives): Service level objectives are measurable targets for the reliability and performance of a service over a defined evaluation period.
- [Shadow Testing](https://blowstack.com/tools/cloud-concepts-hub/shadow-testing): Shadow testing evaluates a candidate system using copies of live production requests while only the established production system returns responses to users.
- [Small Language Models](https://blowstack.com/tools/cloud-concepts-hub/small-language-models): Small language models are language models with relatively compact parameter counts and resource requirements, selected to perform suitable tasks efficiently.
- [SQL Injection](https://blowstack.com/tools/cloud-concepts-hub/sql-injection): SQL injection is an application vulnerability in which untrusted input changes the structure or meaning of a database query.
- [Stage-Gate Process](https://blowstack.com/tools/cloud-concepts-hub/stage-gate-process): A stage-gate process divides an initiative into phases separated by evidence-based decisions to proceed, scale, pause, rework, or terminate.
- [Status Quo Bias](https://blowstack.com/tools/cloud-concepts-hub/status-quo-bias): Status quo bias is the tendency to favor an existing situation or established practice over alternatives because it is familiar, rather than because evidence shows it is better.
- [Stress Testing](https://blowstack.com/tools/cloud-concepts-hub/stress-testing): Stress testing deliberately pushes a system beyond its expected operating load or constrains its resources to evaluate failure behavior, capacity limits, and recovery.
- [Structured Outputs](https://blowstack.com/tools/cloud-concepts-hub/structured-outputs): Structured outputs constrain a foundation model’s responses to an explicit, machine-readable format or schema so applications can process them reliably.
- [Subgroup Analysis](https://blowstack.com/tools/cloud-concepts-hub/subgroup-analysis): Subgroup analysis evaluates AI data, predictions, and outcomes separately for defined groups to reveal differences hidden by overall metrics.
- [Task Completion Rate](https://blowstack.com/tools/cloud-concepts-hub/task-completion-rate): Task Completion Rate is the percentage of attempted tasks that achieve a predefined successful outcome.
- [TCP Congestion Control](https://blowstack.com/tools/cloud-concepts-hub/tcp-congestion-control): TCP Congestion Control is the set of sender-side mechanisms that adapt TCP transmission to available network capacity and congestion signals.
- [Technology Adoption Lifecycle](https://blowstack.com/tools/cloud-concepts-hub/technology-adoption-lifecycle): The Technology Adoption Lifecycle describes how a technology spreads through adopter groups with different motivations, risk tolerances, and requirements for proven value.
- [Temporal Aggregation](https://blowstack.com/tools/cloud-concepts-hub/temporal-aggregation): Temporal aggregation combines timestamped observations within defined time intervals into summary values such as counts, sums, averages, or percentiles.
- [Threat Modeling](https://blowstack.com/tools/cloud-concepts-hub/threat-modeling): Threat modeling is a structured process for identifying how a system could be attacked and selecting controls and monitoring to reduce the resulting risks.
- [Time Series](https://blowstack.com/tools/cloud-concepts-hub/time-series): A time series is a sequence of observations indexed by time that represents how a measured quantity changes.
- [Time-Series Data](https://blowstack.com/tools/cloud-concepts-hub/time-series-data): Time-series data consists of observations associated with timestamps and analyzed to understand changes over time.
- [Timeouts](https://blowstack.com/tools/cloud-concepts-hub/timeouts): Timeouts are enforced time limits on how long an application waits for an operation before treating it as unsuccessful or taking another action.
- [Token Budgeting](https://blowstack.com/tools/cloud-concepts-hub/token-budgeting): Token Budgeting is the practice of allocating, estimating, and controlling foundation-model token usage to meet cost, context-window, latency, and quality requirements.
- [Trace Sampling](https://blowstack.com/tools/cloud-concepts-hub/trace-sampling): Trace sampling selects which distributed requests have their tracing data recorded or retained, balancing diagnostic coverage against telemetry cost and overhead.
- [Traffic Shaping](https://blowstack.com/tools/cloud-concepts-hub/traffic-shaping): Traffic shaping regulates the rate and timing of packet transmission by buffering traffic and scheduling its release to match a defined bandwidth policy.
- [Trajectory Evaluation](https://blowstack.com/tools/cloud-concepts-hub/trajectory-evaluation): Trajectory evaluation assesses the sequence of observable steps a foundation-model application takes to complete a task, rather than judging only its final answer.
- [Underfitting](https://blowstack.com/tools/cloud-concepts-hub/underfitting): Underfitting occurs when a machine learning model fails to learn enough of the meaningful patterns in its training data to make sufficiently accurate predictions.
- [User Satisfaction](https://blowstack.com/tools/cloud-concepts-hub/user-satisfaction): User satisfaction is the degree to which an application meets users’ expectations and perceived needs during an interaction or task.
- [Workload Predictability](https://blowstack.com/tools/cloud-concepts-hub/workload-predictability): Workload predictability is the degree to which an application's future resource demand, usage duration, and operating schedule can be anticipated.
