How mongulu-cm/mtchoun-mouh works
Main Components Identification
a) Frontend Layer:
• Static website hosted on S3 (evident from the html directory and deployment instructions)
• Registration interface (mtchoun-mouhregistration.html)
• Error handling page (error.html)
b) Backend Layer:
• AWS Lambda functions (visible in infra/api):
• Registration handler
• Scan handler
• Notification handler
c) Data Storage:
• DynamoDB for user registration data
• S3 for static website hosting
d) External Services:
• Consulate website (data source)
• Email notification service
• Monitoring services (Matomo, Sentry, CloudWatch)
[User Browser] → [CloudFront/S3 (Static Website)]
• ↓
[API Gateway] → [Lambda Functions]
• ↓
• [DynamoDB Tables]
• ↓
[External Consulate Website] ← [Scan Lambda Function]
• ↓
• [Email Notification Service]
Key Flows to Highlight
a) Registration Flow:
• User submission → API Gateway → Register Lambda → DynamoDB
b) Scanning Flow:
• Scheduled trigger → Scan Lambda → Consulate Website → DynamoDB → Notify Lambda → Email Service
c) Monitoring Flow:
• All components → CloudWatch Logs
• Frontend → Matomo Analytics
• Error tracking → Sentry
Important Details
• AWS Region information (from terraform configs)
• Security groups and IAM roles
• API Gateway endpoints
• CloudWatch logging points
• Error handling paths
Technical Stack Callouts
• Python for Lambda functions
• Terraform for infrastructure
• HTML/CSS for frontend
• AWS services (Lambda, API Gateway, DynamoDB, S3)
• Monitoring tools (Matomo, Sentry, CloudWatch)