CloudWatch adds SLOs
Amazon CloudWatch Application Signals now supports SLO capabilities, including console‑based SLO creation and tracking so teams can define and monitor service level objectives directly in CloudWatch dashboards and . That cuts a layer of tooling between ops and SLA measurement — useful if you’re tightening SLOs for production AI or customer‑facing services.
AWS announced on March 13, 2026 that Application Signals now includes three named console SLO features—SLO Recommendations, Service‑Level SLOs, and SLO Performance Report. aws.amazon.com Application Signals records standardized application metrics such as volume, latency, and errors and exposes SLI status inside a service list and an automatically discovered topology map. docs.aws.amazon.com The service supports both request‑based and period‑based SLO evaluations and documents SLO creation via the CreateServiceLevelObjective API, which can auto‑provision the AWSServiceRoleForCloudWatchApplicationSignals service‑linked role. docs.aws.amazon.com Request‑based SLOs were previously introduced in September 2024 and were made available in 28 commercial AWS Regions at that time, with the CA West (Calgary) Region excluded. aws.amazon.com The SLO Recommendations feature and SLO Performance Report are presented as console tools to generate suggested goals and snapshot reports for an SLO’s attainment and burn rate, according to AWS’s March 13 announcement. aws.amazon.com AWS engineers have published operational guidance and case notes showing real migrations: the Amazon Product Search team described moving its in‑house SLO and burn‑rate monitoring into Application Signals and using those alarms in production. aws.amazon.com Independent coverage notes that Application Signals bundles APM‑style telemetry and automatic instrumentation into CloudWatch—positioning the feature set as an option to replace third‑party APM vendors like Datadog, New Relic, or Dynatrace. teamaws.com
