AWS AmazonCloudWatch documentation change
Summary
Added documentation about un-instrumented service visibility, expanded filtering options (Platform, SLI Health, Account ID, instrumentation status), and enhanced audit findings/change event tracking capabilities
Security assessment
Changes focus on improving observability and operational monitoring capabilities rather than addressing security vulnerabilities. While audit findings help identify operational issues, there's no evidence of addressing specific security vulnerabilities or adding security-specific features.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/Services-page.md b/AmazonCloudWatch/latest/monitoring/Services-page.md index 89cbb06c9..c087d38db 100644 --- a//AmazonCloudWatch/latest/monitoring/Services-page.md +++ b//AmazonCloudWatch/latest/monitoring/Services-page.md @@ -10,0 +11,2 @@ Use the Services page to see a list of your services that are [enabled for Appli +For un-instrumented services, the Service overview page displays limited information with prominent calls-to-action to enable Application Signals instrumentation. + @@ -43,0 +46,8 @@ The advanced filtering options allows you to: + * Filter by Platform + + * Filter by SLI Health + + * Filter by Account ID (in cross-account observability setups) + + * Filter by instrumentation status (instrumented vs un-instrumented) + @@ -52,0 +63,2 @@ The advanced filtering options allows you to: +For un-instrumented services, the Service overview page displays limited information with prominent calls-to-action to enable Application Signals instrumentation. Un-instrumented services appear in the Services table even when they haven't been configured with Application Signals, helping you identify gaps in your observability coverage and prioritize which services to instrument next based on their position in your architecture. + @@ -80 +92,3 @@ You can visualize key operational performance indicators over time using a serie -The Audit findings section automatically detects and shows critical problems in your service's behavior, so you don't need to investigate manually. You can use the **Change events** section to identify how recent deployments affect your service behavior. +The Audit findings section automatically detects and shows critical problems in your service's behavior, so you don't need to investigate manually. Application Signals analyzes your applications to report significant observations and potential problems, simplifying root cause analysis. These automated findings consolidate relevant traces, eliminating the need to navigate through multiple clicks. The audit system helps teams quickly identify issues and their underlying causes, enabling faster problem resolution. + +You can use the Change events section to identify how recent deployments or configuration changes affect your service behavior. Application Signals automatically processes CloudTrail events to track change events across your application. Monitor configuration and deployment events for services and their dependencies, providing immediate context for operational analysis and troubleshooting. Application Signals automatically correlates deployment times with performance changes, helping you quickly identify if recent deployments contributed to service issues.