Amazon CloudWatch Application Signals adds GitHub Action and MCP server improvements

AWS Release Notes

AWS announces the general availability of a new GitHub Action and improvements to CloudWatch Application Signals MCP server that bring application observability into developer tools, making troubleshooting issues faster and more convenient.

New Features

• AWS GitHub Action: Catch breaching SLOs or critical service errors directly in GitHub workflows.
• CloudWatch Application Signals MCP server: Identify the exact file, function, and line of code responsible for latency, errors, or SLO violations.
• Instrumentation guidance: Ensure comprehensive observability coverage by modifying infrastructure-as-code to set up OTel-based application performance monitoring.

What to do

• Use @awsapm in GitHub Issues for intelligent, observability-based responses.
• Ask questions like "Which line of code caused the latency spike in my service?" with the improved MCP server.
• Visit the Application Observability for AWS GitHub Action documentation and the CloudWatch Application Signals MCP server documentation to get started.

Source: AWS release notes

If you need further guidance on AWS, our experts are available at AWS@westloop.io. You may also reach us by submitting the Contact Us form.