Amazon CloudWatch Application Signals now supports integration with Kiro powers

Amazon CloudWatch Application Signals now supports integration with Kiro powers

Today, AWS announces Amazon CloudWatch Application Signals integration with Kiro powers, enabling developers and operators to investigate application health issues faster with AI agent-assisted workflows in Kiro. Kiro Powers is a repository of curated and pre-packaged Model Context Protocol (MCP) servers, steering files, and hooks validated by Kiro partners to accelerate specialized software development and deployment use cases.

Kiro power for Amazon CloudWatch Application Signals packages the Application Signals MCP server with targeted observability guidance, giving the Kiro agent instant context for service health monitoring, SLO compliance, and investigation workflows. With Kiro power for Application Signals, developers can now accelerate troubleshooting their distributed applications in minutes instead of spending hours, directly in their IDE. For example, developers triaging an SLO or isolating an impacted service or operation, the Kiro power will dynamically load the relevant guidance and operational signals, so AI agents receive only the context needed for the specific task at hand.

Amazon CloudWatch Application Signals Kiro power Kiro power is available within Kiro IDE and Kiro powers webpage for one-click installation in all AWS Regions. To learn more about Application signals MCP server, visit our documentation. Amazon CloudWatch Application Signals helps you monitor and improve application performance on AWS by automatically collecting application telemetry and enabling you to track application health, performance, and service relationships. To get started, see the Amazon CloudWatch Application Signals documentation.

Categories: general:products/amazon-cloudwatch

Source: Amazon Web Services



Latest Posts

Pass It On
Leave a Comment

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *