#cloudwatch
237 lines of boto3 that audit CloudWatch Logs metric filters for pattern gaps and alarm coverage, per log group. Advanced sysadmin territory. #AWS #CloudWatch #Python https://www.valtersit.com/python/cloudwatch-log-metric-filter-auditor/
CloudWatch Log Metric Filter Auditor
www.valtersit.com
November 14, 2026 at 5:50 PM
Announcing Accelerated Compute Insights for Amazon CloudWatch

https://aws.amazon.com/about-aws/whats-new/2026/11/accelerated-compute-insights-cloudwatch/
November 13, 2026 at 9:25 PM
"From Zero to Monitoring: Setting Up AWS CloudWatch Alarms for EC2" by Amir Khan

From Zero to Monitoring: Setting Up AWS CloudWatch Alarms for EC2
Learn how to monitor Amazon EC2 instances using AWS CloudWatch. This beginner-friendly guide explains EC2 performance metrics, CPU utilization alarms, and Amazon SNS email notifications with a practical step-by-step approach.
community.aws
November 15, 2026 at 11:00 AM
[AWS CLI v2.40.2] api-change/cloudwatch
CloudWatch メトリックスデータクエリ定義の保存、取得、一覧表示、削除のサポートが追加されました。
https://docs.aws.amazon.com/cli/latest/reference/cloudwatch/
#AWS
November 12, 2026 at 9:38 PM
💻 「OpenTelemetryで変わった新時代のCloudWatchメトリクス監視」というタイトルでLT登壇しました

JAWS-UG千葉支部でLT登壇し、OpenTelemetryによるCloudWatchメトリクス監視の変化を紹介した。
・Classic metricsは問題なく使用可能、カスタムメトリクスはOpenTelemetry metric…

📰 出典: DevelopersIO
▶ 要約を読む topiatsume.pages.dev/summary/2d…
#OpenTelemetry #CloudWatchメトリクス #テクノロジー
「OpenTelemetryで変わった新時代のCloudWatchメトリクス監視」というタイトルでLT登壇しました #jawsugchiba #jawsug #toukatsu_dev【AI要約】
JAWS-UG千葉支部でLT登壇し、OpenTelemetryによるCloudWatchメトリクス監視の変化を紹介した。(トピあつめ)
topiatsume.pages.dev
November 15, 2026 at 8:30 AM
"CloudWatch alarms and missing data: set treatMissingData on purpose in CDK" by Juan Naranjo

#amazon-cloudwatch #aws-cdk #observability
CloudWatch alarms and missing data: set treatMissingData on purpose in CDK
An alarm with no data points can sit in INSUFFICIENT_DATA. What the four treatMissingData options do, and how to set one in CDK, checked with cdk synth.
community.aws
November 14, 2026 at 9:00 PM
Amazon CloudWatch now offers accelerated compute insights for monitoring and optimizing AI inference workloads running on GPUs in Amazon EKS clusters.
Announcing Accelerated Compute Insights for Amazon CloudWatch
Amazon CloudWatch now offers accelerated compute insights for monitoring and optimizing AI inference workloads running on GPUs in Amazon EKS clusters.
aws-news.com
November 13, 2026 at 6:05 PM
AWS CloudWatch Alarms and SNS: Get Notified When Something Goes Wrong
In the last two posts I set up several accounts and a way for people to sign in. Now the question every real environment hits: when something goes wrong, **who finds out, and how fast?** The basic answer on AWS is a **CloudWatch alarm** that sends a message through **Amazon SNS**. ## What each service does * **Amazon CloudWatch** collects metrics, such as CPU use or estimated charges, and can watch them with alarms. * **CloudWatch alarm** compares a metric to a threshold and moves between three states: **OK** , **ALARM** and **INSUFFICIENT_DATA**. * **Amazon SNS** (Simple Notification Service) sends a message to everyone subscribed to a **topic** , by email, SMS or other targets. ## The building blocks Term | What it is | Notes ---|---|--- **Metric** | A number measured over time | Example: CPUUtilization or EstimatedCharges **Alarm** | A rule on one metric | Threshold, period and number of periods **SNS topic** | A channel for messages | Alarms publish to it **Subscription** | Who receives the topic | An email subscription must be confirmed **Alarm action** | What the alarm does on a state change | Often: publish to an SNS topic ## Why a topic and not a direct email * One topic can notify a whole team, and you can add people without touching the alarm. * The same topic can be reused by many alarms. * Later you can add other targets, such as a chat tool or a Lambda function. ## Hands-on: a billing alert in your own account 1. Sign in with a user that can open the Billing console, and turn on **Receive CloudWatch billing alerts** in Billing preferences. 2. Switch the Region to **US East (N. Virginia)** , because billing metrics are only published there. 3. Open **SNS** , create a **Standard** topic named `billing-alerts`, and add an **Email** subscription with your address. 4. Open the email and choose **Confirm subscription**. Until you do, nothing is delivered. 5. Open **CloudWatch** , then **Alarms** , then **Create alarm**. Select the metric **Billing > Total Estimated Charge** and set a threshold such as 5 USD. 6. For the alarm action choose **In alarm** , send to the `billing-alerts` topic, and create the alarm. 7. Test the notification path with the CLI: `aws cloudwatch set-alarm-state --alarm-name <your-alarm> --state-value ALARM --state-reason "test"` and check that the email arrives. ## Common mistakes * Forgetting to confirm the email subscription. * Creating the billing alarm in a Region other than US East (N. Virginia). * Setting the threshold so high that the alarm never fires. * Sending alerts to one personal inbox that nobody else watches. ## Key takeaways * An alarm watches a metric, SNS delivers the message. * Use a topic so you can add people and targets later. * Confirm subscriptions and test the path on purpose. * Start with a billing alarm in every new account. Tomorrow I'll look at how to see who did what in your account, with AWS CloudTrail. _Part of #120DaysOfAWS._
dev.to
November 15, 2026 at 4:43 PM
It is super convenient when you are dealing with long lists of links, like CloudWatch Log streams pages. Just right click it to open the detail view in the right frame.
November 13, 2026 at 3:38 PM
Announcing Accelerated Compute Insights for Amazon CloudWatch

CloudWatch now offers accelerated compute insights for monitoring AI inference workloads in Amazon EKS clusters. It provides fleet-level visibility into GPU usage, identifies idle accelerators, and optimizes costs.
November 13, 2026 at 6:03 PM
Two huge QoL Pre:Invent launches in CloudWatch and IAM:

1️⃣ Amazon CloudWatch Logs announces account-level retention policies: buff.ly/9qENizB
2️⃣ AWS STS now supports cross-partition federation for AWS identities: buff.ly/vCvncOL

The first item has only been on my wishlist for about 11 years 😅
Amazon CloudWatch Logs announces account-level retention policies
Amazon CloudWatch Logs now supports account-level retention policies to manage log data retention across all or specific log groups in an AWS account.
buff.ly
November 10, 2026 at 1:15 PM
📰 New article by Aayushi Mittal

Diagnose Amazon Aurora MySQL performance using CloudWatch Database Insights

#AWS #Databases
Diagnose Amazon Aurora MySQL performance using CloudWatch Database Insights
When an Aurora MySQL or Amazon RDS for MySQL database slows down, it can be hard to tell why. This post shows how to read DB load in Amazon CloudWatch Database Insights, interpret the most common MySQL wait events, and turn each into a concrete action, so you can fix the real bottleneck instead of scaling up to a larger instance.
aws.amazon.com
November 11, 2026 at 4:51 PM
"Finding slow builds, flaky tests and bad deploys with OpenTelemetry" by Joe A

#open-telemetry #aws-cloudwatch #observability #ci-cd #devops
Finding slow builds, flaky tests and bad deploys with OpenTelemetry
One OpenTelemetry trace per CI run, stored in CloudWatch, shows why builds are slow, which tests flake and what broke.
community.aws
November 15, 2026 at 6:00 AM
Announcing Accelerated Compute Insights for Amazon CloudWatch

AWS finally tells you which GPUs you're paying for are sitting idle. "No additional charge" except for the CloudWatch metrics that'll cost more than the compute. At least they admit you needed this visibility all along.
November 13, 2026 at 6:03 PM
When a CloudWatch alarm fires, the agent pulls CloudWatch logs and metrics (optionally also Datadog or Grafana), checks GitHub or GitLab for what was just deployed and sends root cause plus mitigation steps to Slack or PagerDuty. Not a raw log dump, which is already nice.
November 14, 2026 at 8:03 AM
AWS Security Hub CSPM findings can now be ingested into Amazon CloudWatch Logs, enabling on-call engineers to correlate security findings with performance metrics in a unified operational dashboard.
Bring AWS Security Hub CSPM findings into your Amazon CloudWatch on-call workflow
AWS Security Hub CSPM findings can now be ingested into Amazon CloudWatch Logs, enabling on-call engineers to correlate security findings with performance metrics in a unified operational dashboard.
aws-news.com
November 13, 2026 at 4:21 PM
📢 New #updates · 13 Nov #9.4

· Gumroad v2026.11.13.4 — Monitoring go_web requests and 5xx errors in CloudWatch
November 13, 2026 at 11:16 AM
AWS DevOps Agent skill profiles CloudWatch Logs estates at scale using Sandbox to run analysis code without standing infrastructure.
Profile your Amazon CloudWatch Logs estate with an AWS DevOps Agent skill in sandbox, no infrastructure to deploy
AWS DevOps Agent skill profiles CloudWatch Logs estates at scale using Sandbox to run analysis code without standing infrastructure.
aws-news.com
November 12, 2026 at 8:38 PM
That no one else is complaining about how AWS changed how it authorizes access to cloudwatch for log delivery in the past day tells me either we’re the first to be hit by the change or no one else is alerting on AccessDenied events within their prod environments like good children should be
November 13, 2026 at 12:13 AM