daniel
|
38905bb1e9
|
Phase 0: CDK stack + Lambdas + AgentCore Runtime 1 scaffold
- CDK TypeScript stack (AgentClawStack):
- S3 workspace bucket with BucketDeployment seed
- DynamoDB session-store (actor_id → session_id, TTL)
- SQS FIFO message queue (serialized per actor)
- Lambda: tg-ingest (webhook validation, typing action, SQS enqueue)
- Lambda: agent-runner (SQS → InvokeAgentRuntime, session management)
- API Gateway HTTP: POST /telegram → tg-ingest
- AgentCore Runtime 1 IAM execution role
- CDK outputs: WebhookUrl, WorkspaceBucketName, Runtime1RoleArn
- Runtime 1 (Python + Strands + BedrockAgentCoreApp):
- main.py: entrypoint, Strands agent, tool wiring
- channels/: ChannelAdapter Protocol + TelegramAdapter (decoupled)
- tools/: web_search (Brave), web_fetch, read/write_workspace_file, send_message
- prompt_builder.py: loads SOUL.md/AGENTS.md/USER.md from S3 (cached)
- Lambdas:
- tg-ingest: validate X-Telegram-Bot-Api-Secret-Token, send typing, enqueue FIFO
- agent-runner: session lookup/create in DDB, bundle batched messages, InvokeAgentRuntime
- workspace/: seed files (SOUL.md, AGENTS.md, USER.md, IDENTITY.md, HEARTBEAT.md)
NOTE: AgentCore Runtime 1 creation via CfnResource deferred — deploy CDK first,
create runtime manually with the output Role ARN, then redeploy with runtime1Arn context param.
|
2026-05-04 09:00:23 -05:00 |
|