MIKE-04: deploy isolated AWS staging environment
From the PR description
MIKE-04: AWS Staging Access
AWS ALB URL
http://atlas-mike-staging-alb-1821218227.us-east-1.elb.amazonaws.com
Functional Credentials
- Email: admin@atlasgov.com
- Password: AtlasStaging2026!
Status
- Infrastructure provisioned: partial
- Application operational: yes
- Login operational: yes
- Sprint status: in progress
What's Working
- Backend health endpoint
- Supabase Auth (GoTrue) - signup, login, health
- Kong API gateway routing
- PostgREST running
- User created and login tested with JWT
- ALB native hostname over HTTP (no external domain)
- Zero references to external domains in code
Commits
- feat(infra): isolated AWS staging infrastructure
- feat(storage): S3 through ECS IAM roles
- feat(containers): hardened production images
- feat(supabase): self-hosted auth and API services
- feat(deploy): OIDC staging deployment
- test(config): AWS IAM storage mode tests
- docs(sprint): checkpoint documentation
Our analysis
Provision isolated AWS staging access — read the full analysis →
Think the analysis missed something the PR description covers?
Capture this PR into my fork
Download a Markdown prompt that tells Claude how to port every
commit in this PR into your working tree. Run it via
claude -p < capture-pull-6.md from
inside the repo you want the changes in.