CloudWatch Omni leaves the AWS console and ships an IDE extension
Victoria Shinder2 min readAWS announced the general availability of Amazon CloudWatch Omni on 23 September 2026, described as an evolution of CloudWatch: an AI-powered observability experience organised around teams and the applications they run, combining OpenTelemetry interoperability with CloudWatch's scale.
Three details in the announcement are worth separating from the framing.
It is not only a console tab. Omni ships as a standalone web experience with its own single sign-on for a team, and as a local IDE extension for VS Code, Cursor and Kiro. The extension is free and, in AWS's own words, needs no AWS account — it is for instrumenting, debugging and evaluating agents locally.
Its scope crosses accounts and clouds. You create spaces in central accounts to see telemetry across AWS accounts and regions as well as other clouds, including Azure workloads. Omni discovers services, maps dependencies and surfaces golden metrics on its own.
Availability is narrow at GA: US East (N. Virginia), US West (Oregon) and Europe (Ireland).
What it means
The IDE extension is the part that does not fit the usual shape of an AWS launch. An observability product that installs into an editor, runs without an account and evaluates agents locally is aimed at the moment before anything is deployed — which is where agent behaviour is actually debugged, and where CloudWatch has historically had nothing to say.
The cross-cloud line is the other one to note, and to read precisely. Reading Azure telemetry into an AWS-hosted pane is not the same as being cloud-neutral; the data lands in AWS and the bill is an AWS bill. What it does change is the argument for a separate observability vendor whose pitch was that it alone could see both.
We are not evaluating the AI part, because the announcement describes capabilities rather than results — the claim is that Omni helps evaluate quality and run experiments to validate fixes before shipping. Whether it does is a question for a team with a real incident, not for a launch post. Pricing and the product page are linked from the announcement; we have not tested any of it.