agentcore-ops-review
Comprehensive operational review procedures for Amazon Bedrock
pamvas · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add aws/tools-for-devops-agent --skill agentcore-ops-review技能说明
name: agentcore-ops-review description: Comprehensive operational review procedures for Amazon Bedrock AgentCore resources aligned with the AWS Well-Architected Framework. Covers four check areas — Runtime Resilience, Gateway Health, Memory & Knowledge Effectiveness, and Resource Utilization & Operational Hygiene — plus runtime observability signals from CloudWatch. Use this skill when a user asks to review, audit, or assess Amazon Bedrock AgentCore workloads, perform an AgentCore operational readiness review, investigate agent runtime failures, audit memory/knowledge pipeline health, or review gateway resilience and resource hygiene. Triggers on requests like "AgentCore review", "AgentCore best practices audit", "review my AgentCore runtimes", "AgentCore health check", "audit my agent memory pipelines", or "ORR for AgentCore". metadata: author: pamvas version: "1.0.1" aws-devops-agent-skills.agent-types: "Chat tasks, Evaluation" aws-devops-agent-skills.aws-services: "Amazon Bedrock AgentCore" aws-devops-agent-skills.technical-domains: "Machine Learning, GenAI"
Bedrock AgentCore Operational Review
Use this skill when performing an operational review of Amazon Bedrock AgentCore resources, investigating agent runtime failures, auditing memory/knowledge pipeline health, or reviewing gateway resilience and resource hygiene.
Overview
This skill provides procedures for a review of AgentCore resources across four check areas mapped to the AWS Well-Architected Framework:
- Runtime Resilience (Reliability) — Failed/stuck runtimes and endpoints, single-AZ VPC placement, endpoint version drift, DEFAULT-endpoint-only deployments
- Gateway Health (Reliability) — Gateway status, target redundancy and health, policy engine attachment, target synchronization freshness
- Memory & Knowledge Effectiveness (Performance Efficiency) — Extraction pipeline errors, empty long-term memory, high ingestion error rate, provisioned-but-never-populated memories
- Resource Utilization & Operational Hygiene (Operational Excellence) — Idle resources, consolidation opportunities, low overall utilization
- Runtime Observability (cross-pillar) — Session counts, invocations, throttles, vCPU-hours, GB-hours per runtime
This is a READ-ONLY review. No modifications are made to any resource, and it never invokes an agent (InvokeAgentRuntime), reads no prompts or responses, and makes no other data-plane calls. One exception: for long-term memories the skill calls bedrock-agentcore:ListMemoryRecords (a data-plane API) solely to obtain a record count. That response can include a content field carrying extracted, potentially PII-bearing memory content; the skill uses only the count and never parses, logs, stores, or reproduces content. See "Memory record data handling" below.
Data Source Boundaries (IMPORTANT — IAM footprint)
The standard AIDevOpsAgentAccessPolicy covers bedrock:* read actions but does NOT include the bedrock-agentcore:* namespace. (Note: bedrock-agentcore-control is the SDK client name, not an IAM prefix — all control-plane actions such as ListAgentRuntimes, GetMemory, and ListGateways authorize under the single service prefix bedrock-agentcore:.) Two modes:
- Runtime-observability-only mode — relies exclusively on CloudWatch metrics (
cloudwatch:GetMetricData,cloudwatch:ListMetrics) against namespaceAWS/Bedrock-AgentCore. Requires nobedrock-agentcore:additions. When an account isn't using AgentCore, the namespace is simply empty ("no activity detected") — this is not a failure. - Full control-plane mode — adds read-only
bedrock-agentcore:control-plane List/Get actions andec2:DescribeSubnetsto enable the runtime/gateway/memory/utilization checks. It also uses one data-plane action,bedrock-agentcore:ListMemoryRecords, for the long-term-memory record count only (see "Memory record data handling" below). Seereferences/iam-policy-linked-account.json.
If a required permission is missing, the affected check degrades to a visibility limit (reported as "signal unavailable / check skipped") rather than failing the review or producing a false finding.
Memory record data handling: bedrock-agentcore:ListMemoryRecords is a data-plane API whose MemoryRecordSummary entries include a required content field — the extracted facts/preferences/summaries a long-term memory has stored, which can contain end-user PII. This skill calls it only to count records for AC-MEM-2 and never reads, parses, logs, stores, transforms, or reproduces the content field. If you prefer zero data-plane access, omit this action from the IAM policy: AC-MEM-2 then degrades to a visibility limit while all other memory checks (which use CloudWatch ingestion metrics) continue to work.
Seam with agentcore-observability-setup: This skill assesses operational posture from existing telemetry; it does not configure or validate observability wiring. Where telemetry is absent, this skill reports a visibility limit and defers the configuration gap to agentcore-observability-setup — that skill owns the observability-wiring finding (Transaction Search, OTEL/ADOT, log delivery, X-Ray resource policy), while this skill reports only the posture consequence. A customer running both should not see two overlapping findings on the same resource.
Step 1: Discover Account and Regions
- Call
sts:GetCallerIdentityto determine the account. - Discover AgentCore-active regions:
- Query Cost Explorer:
ce:GetDimensionValues(dimension SERVICE, last 30 days), match "Amazon Bedrock AgentCore". - Then
ce:GetCostAndUsagefor that service grouped by REGION; select top regions by UnblendedCost. - If no AgentCore spend is found, fall back to probing
cloudwatch:ListMetrics(namespaceAWS/Bedrock-AgentCore) in the customer's primary regions to detect activity.
- Query Cost Explorer:
- If no AgentCore acti