Ask HN: Possible issue impacting AWS Cloudwatch logs availability?
Users report that AWS CloudWatch Logs in the Console shows "There are no log groups" despite log groups existing, affecting at least us-east-1 and us-west-2. The AWS Health Dashboard does not list this issue, while other CloudWatch resources like dashboards and alarms appear normal.
Background
- AWS CloudWatch Logs is a service where developers store and monitor log data from their applications and servers; "Log Groups" are containers that organize these logs.
- The Hacker News post reports that the Log Groups listing in the AWS Console is showing up empty ("no log groups") in the US East (N. Virginia) and US West (Oregon) regions, even though logs should exist. Other CloudWatch features (dashboards, alarms) appear unaffected.
- AWS has an official health dashboard (status.aws.amazon.com) that was not showing any incident at the time of posting — meaning the issue was either unrecognized, a frontend/UI bug rather than a backend outage, or an emerging problem not yet declared.
- This matters because CloudWatch Logs is a critical observability tool; if it appears empty, engineers cannot search or access their logs, which can break troubleshooting, incident response, and compliance processes.