Skip to content

Add AWS migration plan for directory-pipeline#7

Merged
hadro merged 1 commit into
mainfrom
claude/directory-pipeline-aws-plan-ccbt3a
Jun 15, 2026
Merged

Add AWS migration plan for directory-pipeline#7
hadro merged 1 commit into
mainfrom
claude/directory-pipeline-aws-plan-ccbt3a

Conversation

@hadro

@hadro hadro commented Jun 15, 2026

Copy link
Copy Markdown
Owner

Adds docs/aws-migration-plan.md — a plan to run the directory-pipeline entirely on AWS infrastructure.

Highlights:

  • LLM: replace Gemini with Amazon Bedrock (Claude), tiered Sonnet default / Opus fallback, via a thin provider adapter in utils/gemini.pyutils/llm.py so call sites change only their imports.
  • Geocoding: replace Google Maps with Amazon Location Service.
  • Auth: IAM roles (no API keys); S3-backed artifact storage via a sync wrapper (not s3fs).
  • Topology: Phase 1 single GPU EC2 for validation → Phase 2 AWS Batch (GPU) + Step Functions for hundreds of volumes in parallel.
  • Cost estimate: ~$70/500-page volume standard, ~$40 optimized (batch + caching + Spot); ~$110 if Opus were primary.

https://claude.ai/code/session_017sVGN7dXqU4irqqzMhSWMK


Generated by Claude Code

Plan to run the pipeline entirely on AWS: Amazon Bedrock (Claude,
tiered Sonnet default / Opus fallback) replacing Gemini, Amazon
Location replacing Google Maps, IAM-based auth, S3-backed storage,
and a two-phase topology (single GPU EC2 → AWS Batch + Step Functions).
Includes a per-volume cost estimate.

https://claude.ai/code/session_017sVGN7dXqU4irqqzMhSWMK
@hadro hadro merged commit 5f17a99 into main Jun 15, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants