Prescreening Infrastructure and Operations
Verified production path
Frontends
The participant frontend workflows deploy corp builds to S3. Live buckets include:
dmind-prescreening-frontendanddmind-prescreening-dev-frontenddmind-prescreening-tu-frontendanddmind-prescreening-tu-uat-frontenddmind-prescreening-mdcu-frontenddmind-prescreening-cpird-frontenddmind-prescreening-thpf-frontenddmind-prescreening-kku-frontenddmind-prescreening-thangrath-frontenddmind-prescreening-tsu-frontend
The staff dashboard is Amplify app mental-dashboard-frontend (d3mkycwgs5ucuo). Its production branch is main, auto-build is enabled, and dashboard.prescreening.dmind.app points to that branch. The configured production API base is https://api.prescreening.dmind.app/dashboard.
Backend
| Resource | Verified name/detail |
|---|---|
| ECS cluster | dmind-prescreening-backend |
| ECR repository | dmind-prescreening-backend |
| Production ALB | dmind-prescreening-prod (internet-facing) |
| Development ALB | dev-alb |
| Redis | dmind-prescreening-backend-prod |
| Main log group | /dmind-prescreening-backend |
| Corp log groups | TU, MDCU, KKU, THPF, Thangrath, and TSU names are present; Chula, Navy, and Somdet log-group namespaces remain. |
| Content bucket | dmind-prescreening |
| Alarm handler | dmind-prescreening-alarm-bot-handler Lambda |
Current environment mapping
This mapping was verified on 2026-08-19 in AWS account 564141170168, region ap-southeast-1, and Atlas project DMIND Production, cluster dmind-prescreen-backend-prod.
| Variant | Participant frontend bucket / release | Backend service / image | Atlas database | AI bundle |
|---|---|---|---|---|
| Main production | dmind-prescreening-frontend / v1.109.0 | dmind-prescreening-backend-prod / dmind-prescreening-backend:v1.13.0 | prescreen | 1_2_0 |
| Development | dmind-prescreening-dev-frontend / release not identified | dmind-prescreening-backend-dev / dmind-prescreening-backend:d9eb2512 | dmind | 1_2_0 |
| TU | dmind-prescreening-tu-frontend / v1.109.0 | dmind-prescreening-backend-tu-prod / dmind-prescreening-backend:v1.11.0 | tu | 1_2_0 |
| TU UAT | dmind-prescreening-tu-uat-frontend / release not identified | No backend identified | prescreen-uat | AI bundle not identified |
| MDCU | dmind-prescreening-mdcu-frontend / v1.109.0 | dmind-prescreening-backend-mdcu-prod / dmind-prescreening-backend:v1.11.0 | mdcu | 1_2_0 |
| CPIRD | dmind-prescreening-cpird-frontend / v1.109.0 | dmind-prescreening-backend-cpird-prod / dmind-prescreening-backend:v1.11.0 | cpird | 1_2_0 |
| THPF | dmind-prescreening-thpf-frontend / v1.109.0 | dmind-prescreening-backend-thpf-prod / dmind-prescreening-backend:v1.11.0 | thpf | 1_2_0 |
| KKU | dmind-prescreening-kku-frontend / v1.109.0 | dmind-prescreening-backend-kku-prod / dmind-prescreening-backend:v1.11.0 | kku | 1_2_0 |
| Thangrath | dmind-prescreening-thangrath-frontend / v1.113.0 | dmind-prescreening-backend-thangrath-prod / dmind-prescreening-backend:v1.12.0 | thangrath | 1_2_0 |
| TSU | dmind-prescreening-tsu-frontend / v1.111.0 | dmind-prescreening-backend-tsu-prod / dmind-prescreening-backend:v1.13.0 | tsu | 1_2_0 |
| Navy | No current frontend bucket | Retained inactive production/UAT services in cluster dmind-prescreening-backend-navy | navy | AI bundle not identified |
| Chula / Somdet | No current frontend bucket | No current backend service identified | chula / somdet | AI bundle not identified |
Each production tenant service has a separate target group behind dmind-prescreening-prod. Development runs in the shared ECS cluster behind dev-alb at api.dev.prescreening.dmind.app.
Configuration and secrets
- Feature configuration paths exist under
/dmind-prescreening/<variant>/feature-configfor main, dev, UAT, TU, MDCU, CPIRD, THPF, KKU, Thangrath, TSU, and Navy. - Backend secrets are separated into dev/prod and corp-specific secret names.
Repository workflow behavior
The participant frontend workflow builds a selected tag for a tenant, publishes the static artifact to that tenant's S3 bucket, and invalidates CloudFront. The backend production workflow creates a Git tag and publishes the ECR image; it does not update the ECS service. Publishing a backend image and activating it in ECS are separate operations.