Feature/agentcore ops review - #80
Open
pamvas wants to merge 2 commits into
Open
Conversation
…ew Adds a read-only operational review skill for Amazon Bedrock AgentCore, covering Runtime Resilience, Gateway Health, Memory & Knowledge Effectiveness, and Resource Utilization, plus cross-pillar runtime observability. Adds a parameter-gated (EnableAgentCoreOpsReview) IAM policy block granting the read-only bedrock-agentcore control-plane set and ec2:DescribeSubnets; observability-only mode needs no additions.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds
agentcore-ops-review, a read-only operational review skill for Amazon Bedrock AgentCore, aligned with the AWS Well-Architected Framework. It discovers a customer's AgentCore estate — runtimes, endpoints, versions, memories, gateways and targets, browsers, code interpreters, and workload identities — and assesses it across four check areas plus cross-pillar runtime observability:AWS/Bedrock-AgentCoreCloudWatch namespaceThe skill is entirely read-only: no
Create*/Update*/Delete*, noInvokeAgentRuntimedata-plane calls, and it reads no memory record content, prompts, or responses. Incomplete signals (missing permissions, no queryable metric) degrade to a documented "visibility limit" rather than producing a false finding.IAM / two modes.
bedrock-agentcore:is not in the standardAIDevOpsAgentAccessPolicy. The skill supports an observability-only mode (CloudWatch only, no additions) and a full control-plane mode (read-onlybedrock-agentcore:List/Get set +ec2:DescribeSubnets). This PR adds a parameter-gated policy block (EnableAgentCoreOpsReview) tocloudformation/devops-agent-skill-policies.yaml, following the existing per-skill convention, so the control-plane permissions are opt-in.Differentiation. Complements
bedrock-adoption-readiness(foundation-model workloads) — this skill reviews the AgentCore runtime/memory/gateway layer. The observability-configuration boundary is deferred toagentcore-observability-setup; this skill consumes that telemetry for posture and does not re-report wiring gaps.Files:
skills/agentcore-ops-review/— SKILL.md, README.md (with non-production disclaimer), CHANGELOG.md,references/(check definitions, report template, sample IAM policies),evals/,.skilleval.yamlcloudformation/devops-agent-skill-policies.yaml— opt-inEnableAgentCoreOpsReviewparameter, condition, policy, and summaryType of change
Testing
Manual (DevOps Agent, live account): Uploaded to an Agent Space (Chat + Evaluation) with the full control-plane policy attached. Ran natural-language prompts (without naming the skill) and confirmed via the reasoning trace that the skill activated and executed the checks. Against a real estate (2 runtimes, 6 memories, 1 gateway, 1 browser, 1 code interpreter, 3 workload identities) it correctly flagged a Critical gateway finding (READY but zero targets, no policy engine), a 239-day idle runtime, ~22% estate utilization, and strategy-aware memory findings. Unreadable memory record counts and absent runtime metrics were reported as visibility limits — not false findings — confirming graceful degradation.
Agent Skill Eval:
skill-eval audit→ 98/100, Grade A, 0 critical, 0 warning (the single INFO, STR-016 README-alongside-SKILL.md, is suppressed via.skilleval.yamlper this repo's convention, as the README is required). Functional (5 cases / 18 assertions) and trigger (3 no-trigger + activation) checks pass; the trigger set correctly abstains on unrelated and foundation-model queries. A fullskill-eval reportreport.jsonwith"passed": truewill be attached once run with the Claude CLI.License confirmation