Shared EC2 — Develop/Staging Server
- Instance ID: i-0c851042b3e385682
- IP Address: 98.83.4.34
- Purpose: ALL Heru backends deploy here for develop/staging
- Region: us-east-1
Deployment Pipeline
1. Ephemeral EC2 agents execute tasks → create PRs
2. Amen Ra reviews and approves PRs
3. Merge to develop branch
4. Deploy backend to shared EC2 (98.83.4.34) via PM2
5. Deploy frontend to Amplify (develop branch)
6. n8n runs on ephemeral EC2 during development
7. Test, iterate, fix, repeat
8. ALL acceptance criteria pass → MVP READY
9. ONLY THEN → Create App Runner instance (production)
10. ONLY THEN → Bundle n8n into App Runner Docker container
Rules
- App Runner = PRODUCTION ONLY. Do NOT create App Runner infrastructure during development.
- The shared EC2 handles ALL develop/staging backends for ALL Herus (port management via
.claude/port-management.sh) - Each Heru gets a unique port on the shared EC2
- PM2 manages processes on the shared EC2
- nginx reverse proxy routes traffic by subdomain
Why: Creating App Runner during development wastes money. The shared EC2 is sufficient for testing. App Runner is the production deployment target ONLY when the MVP is signed off.
How to apply:
- When deploying a Heru’s develop backend: push to shared EC2 (98.83.4.34)
- When a client asks for production: ONLY after MVP sign-off, then create App Runner
- Every Heru checklist must include: “Deploy to shared EC2” BEFORE “Create App Runner”