Closed-loop incident response: connect AWS DevOps Agent to OpenSearch

A walkthrough shows how to connect AWS DevOps Agent to Amazon OpenSearch Service observability data via the Model Context Protocol, so alerting monitors can trigger autonomous root-cause investigation instead of paging a human. It covers three MCP server hosting options (self-managed on ECS/NLB with VPC Lattice, Amazon Bedrock AgentCore, or the built-in OpenSearch 3.3+ MCP endpoint), registering the server as a Capability Provider, mapping IAM roles to OpenSearch fine-grained access control (FGAC) roles, wiring a Lambda webhook forwarder with HMAC signing between SNS alerts and the agent's Event Channel, and verifying the closed loop with a controlled failure injection. Cost adds roughly $70/month for the self-managed path, and security guidance emphasizes private VPC networking, TLS, and least-privilege FGAC scoping.

Source: https://aws.amazon.com/blogs/devops/closed-loop-incident-response-connect-aws-devops-agent-to-opensearch. 8 Sync News only summarizes and links out; content copyright belongs to the authors and original sources.