AWS Bedrock AgentCore Adapter
Deploy prompt packs to AWS Bedrock AgentCore with a single command.
What is the AgentCore Adapter?
Section titled “What is the AgentCore Adapter?”The AgentCore adapter is a deploy provider plugin for PromptKit. It translates your compiled .pack.json into AWS Bedrock AgentCore resources — runtimes, tool gateways, A2A wiring, Cedar policies, memory, and observability configuration.
What It Creates
Section titled “What It Creates”| Pack Concept | AWS Resource | Adapter Resource Type |
|---|---|---|
| Agent prompt | AgentCore Runtime | agent_runtime |
| Pack tool | Gateway Tool target (MCP) | tool_gateway |
| Validators / tool policy | Cedar Policy Engine + Policy | cedar_policy |
| Agent member (multi-agent) | A2A endpoint wiring | a2a_endpoint |
| Memory config | AgentCore Memory | memory |
| Eval with metric | CloudWatch metrics config | (env var injection) |
Key Features
Section titled “Key Features”- Multi-agent support — One runtime per agent member, with A2A discovery wired automatically
- Dry-run mode — Preview what would be deployed without calling AWS APIs
- Resource tagging — Pack metadata and custom tags on all created resources
- Cedar policies — Auto-generated from validators and tool policy definitions
- CloudWatch integration — Metrics config and dashboard generated from eval definitions
- Structured errors — Classified errors with remediation hints
Quick Start
Section titled “Quick Start”# arena.yamldeploy: provider: agentcore agentcore: region: us-west-2 runtime_role_arn: arn:aws:iam::123456789012:role/AgentCoreRuntime runtime_binary_path: /path/to/promptkit-runtime model: claude-3-5-haiku-20241022# Preview the deployment planpromptarena deploy plan
# Deploypromptarena deploy
# Check healthpromptarena deploy status
# Tear downpromptarena deploy destroyHow It Works
Section titled “How It Works”The adapter runs as a subprocess, receiving JSON-RPC requests from the PromptKit CLI. It calls the AWS Bedrock AgentCore SDK to create and manage resources, then returns an opaque state blob containing ARNs and metadata for subsequent operations.
Runtime Architecture
Section titled “Runtime Architecture”The deployed runtime serves two protocols simultaneously:
| Port | Protocol | Purpose |
|---|---|---|
| 8080 | HTTP | External callers — POST /invocations accepts {"prompt": "..."} payloads |
| 9000 | A2A | Agent-to-agent communication — full A2A JSON-RPC protocol |
The HTTP bridge on port 8080 translates simple invocation requests into A2A message/send calls on port 9000. For multi-agent deployments, agents communicate directly via A2A.
Documentation
Section titled “Documentation”Tutorials
Section titled “Tutorials”- First AgentCore Deployment — Deploy a single-agent pack (15 minutes)
- Multi-Agent Deployment — Deploy a multi-agent pack with A2A wiring (20 minutes)
How-To Guides
Section titled “How-To Guides”- Configure the Adapter — All configuration options explained
- Use Dry-Run Mode — Preview deployments without side effects
- Add Resource Tags — Tag resources with custom metadata
- Set Up Observability — CloudWatch metrics, dashboards, and tracing
Explanation
Section titled “Explanation”- Resource Lifecycle — How resources are created, updated, and destroyed
- Security Model — IAM roles, Cedar policies, and A2A authentication
Reference
Section titled “Reference”- Configuration — Complete config schema and validation rules
- Resource Types — All managed resource types and their behavior
- Environment Variables — Variables injected into runtimes
Requirements
Section titled “Requirements”- AWS account with Bedrock AgentCore access
- IAM role with permissions to manage AgentCore resources
- PromptKit CLI with the deploy framework
- A compiled
.pack.json(viapackc)
See Also
Section titled “See Also”- Deploy Overview — PromptKit’s deploy framework
- Adapter Architecture — How adapters work
- Protocol Reference — JSON-RPC protocol spec