0369a74ac1
- Architecture comparison (OpenClaw daemon vs AgentCore serverless) - Component compatibility analysis - Fargate analysis - AgentCore rebuild plan (Telegram, zero always-on compute) - Memory strategy: AgentCore Memory + factbase as structured KB - Serverless relay patterns per channel - All open questions resolved - OpenClaw feature delta March→May 2026 - Build phases and cost estimates
16 lines
1013 B
Markdown
16 lines
1013 B
Markdown
# OpenClaw on AWS AgentCore — Research Project
|
|
|
|
Research into the feasibility of running [OpenClaw](https://github.com/openclaw/openclaw) on [AWS Bedrock AgentCore Runtime](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agents-tools-runtime.html).
|
|
|
|
## Files
|
|
|
|
- `architecture-comparison.md` — Side-by-side architecture comparison
|
|
- `compatibility-analysis.md` — Detailed component-by-component compatibility analysis
|
|
- `offload-requirements.md` — What needs to move to external services
|
|
- `feasibility-verdict.md` — Bottom-line assessment for AgentCore
|
|
- `fargate-analysis.md` — ECS Fargate deployment analysis (the better fit)
|
|
- `agentcore-memory-research.md` — AgentCore Memory deep dive + MEMORY.md replacement analysis
|
|
- `agentcore-rebuild.md` — What's reusable in an AgentCore-native rebuild
|
|
- `serverless-relay-patterns.md` — Lambda/webhook patterns per channel (Discord deep dive)
|
|
- `build-plan.md` — **START HERE**: full build plan, open questions, phases, cost estimate
|