Feature/update deployment diagram aws infra - #69
Merged
Conversation
The diagram described an architecture that was never built (AWS API Gateway, a Grafana Alloy sidecar, a dedicated EC2 running Prometheus/ Loki/Tempo/Grafana). Replaced with what actually exists in reqsai-infra: Route 53 (tamci.app), ACM certificates, a CloudFront distribution with two origins (S3 for the SPA, the ALB for /api/* and /ws/*) plus a CloudFront Function blocking the default *.cloudfront.net domain, a VPC with public/private/database subnets, an ALB restricted to CloudFront's IP range only, ECS Fargate (1 vCPU/2GB, no sidecar), RDS Postgres+pgvector, and the supporting managed services (ECR, Secrets Manager, CloudWatch Logs). Also corrects the mobile app's traffic path: it now goes through CloudFront too, since the ALB's security group no longer accepts direct traffic from anywhere else.
Sections 4.3.4 (C4 deployment diagram narrative) and 7.1.4 (deployment configuration) described an architecture that was never built: AWS API Gateway, a Grafana Alloy sidecar, and a dedicated EC2 instance running Prometheus/Loki/Tempo/Grafana. Rewrites both to describe what actually exists: Route 53 + ACM for the custom domain, CloudFront fronting both the SPA (S3 origin) and the backend (/api/*, /ws/* on the ALB origin) under one origin with no CORS needed, a CloudFront Function blocking the default *.cloudfront.net domain, the ALB's security group restricted to CloudFront's IP range only, a single Fargate container (no sidecar) reading secrets from Secrets Manager, and CloudWatch Logs instead of a self-hosted observability stack. Left the Landing Page references and the historical sprint evidence sections untouched — those are either a different product or a record of what actually happened at the time, not something to retroactively rewrite.
jhosepmyr
requested review from
Eric396,
Kyrubi,
VarBus and
salimramirez
as code owners
July 10, 2026 04:40
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of Change
Section modified:
Motivation:
Type of Change
Checklist Before Requesting Review
develop(notmain)feature/*orbugfix/*feat:,fix:,docs:, etc.)CHANGELOG.mdhas been updated with the change madeassets/subfolder.pdf,.docx,.html)Screenshots or Evidence (optional)
Suggested Reviewers