feat: add AWS DevOps Agent power for operational intelligence

[tipuq]

New Power: aws-devops-agent

Adds a Kiro Power for the AWS DevOps Agent — an AI-powered operational intelligence system accessed via the AWS MCP Server.

What it does

• Incident Investigation — automated root cause analysis (CloudWatch alarms, 503 errors, latency spikes)
• Cost Optimization — find expensive resources, recommend right-sizing
• Architecture Review — security, reliability, and cost analysis of IaC
• Topology Mapping — dependency graphs for AWS resources
• Knowledge Discovery — AWS docs, runbooks, and Agent SOPs

Files added

• aws-devops-agent/POWER.md — Full power documentation (36 DevOps Agent API operations, workflows, context injection patterns)
• aws-devops-agent/mcp.json — MCP server config (uses existing aws-mcp server via mcp-proxy-for-aws)
• aws-devops-agent/steering/steering.md — Tool selection rules, investigation workflow, error recovery
• Updated root README.md with the new power entry (alphabetically placed)

MCP Server

Uses the existing AWS MCP Server (aws-mcp) — no new MCP server needed. All 36 DevOps Agent operations are called via aws___call_aws.

Region Support

Defaults to us-east-1. DevOps Agent is available in 6 regions: us-east-1, us-west-2, ap-southeast-2, ap-northeast-1, eu-central-1, eu-west-1. The agent can monitor resources in any AWS region regardless of Agent Space region. Region note included in Setup section with link to Supported Regions.

Testing

• Verified power structure matches repo conventions (frontmatter format, steering subdirectory, README entry format)
• Follows patterns from existing powers (aws-mcp, datadog, cloudwatch-application-signals)

[nadetastic]

Should be "AWS"