Closed-loop incident response: connect AWS DevOps Agent to OpenSearch
The AWS DevOps Blog describes connecting AWS DevOps Agent to Amazon OpenSearch Service data through an MCP server, so that OpenSearch alerts trigger the agent to query logs and traces and correlate them with CloudTrail and CloudWatch. The post presents three hosting options: self-managed on ECS Fargate behind an NLB with VPC Lattice, Amazon Bedrock AgentCore, and the built-in MCP endpoint on OpenSearch 3.3+. The source text is cut off before the registration and verification steps are complete.
What changes for platform teams
Platform teams running OpenSearch alerting could route alerts to an agent that investigates automatically, but they would need to set up a hosted MCP server, a private network connection, and FGAC role mappings that control what the agent can read. The source describes this as a walkthrough and does not report measured results.
Read the original at AWS DevOps Blog ↗
written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules