How ellkinox/uptime-monitor works
Uptime Monitor serves a browser page through nginx and a load balancer. The browser requests status; the FastAPI endpoint refreshes a 30-second in-memory cache by checking configured websites, then returns the results and backend hostname. The README also documents separate frontend/backend containers on ECS Fargate, with nginx reaching the backend through Service Connect. Infrastructure links reflect documented deployment topology; source excerpts show the API and checking logic, but not the frontend or Terraform implementation details.
Main entry points: main.py Status API · nginx.conf nginx proxy · ecs.tf ECS Fargate · loadbalancer.tf Load balancer
Components 10
Web presentation
- nginx proxy
frontend/nginx.conf - Status page
frontend/index.html
Uptime monitoring
- Status API
backend/main.py - Result cache
backend/main.py - Website checker
backend/main.py
AWS deployment
- Load balancer
infra/loadbalancer.tf - ECS Fargate
infra/ecs.tf - VPC network
infra/network.tf
Other components
- Visitor browser
- Monitored websites
Connections 12
- Visitor browser → Load balancer: requests page
README.md - Load balancer → nginx proxy: routes traffic
README.md - nginx proxy → Status page: serves page
README.md - Visitor browser → nginx proxy: requests status
README.md - nginx proxy → Status API: forwards /api
README.md - Status API → Result cache: reads and refreshes
backend/main.py - Status API → Website checker: checks expired results
backend/main.py - Website checker → Monitored websites: requests URLs
backend/main.py - Status API → Visitor browser: returns status JSON
backend/main.py - ECS Fargate → nginx proxy: runs frontend
README.md - ECS Fargate → Status API: runs backend
README.md - VPC network → ECS Fargate: hosts services