Technical Deep Dive

Architecture, workflows, and AWS service integration for the Healthcare Appointment Booking System.

Architecture

The system uses a **highly available cloud architecture**:

Patients access the app through a **public-facing ALB**.
**Flask backend** runs on **EC2 instances** in private subnets, handling CRUD operations for appointments.
**RDS (Postgres/MySQL) Multi-AZ** stores patient and doctor data securely.
**NAT Gateway** allows private instances to pull updates and connect to SSM for management.
**CloudWatch** monitors logs, metrics, and triggers alarms for errors.

Optional: Include a diagram showing ALB → EC2 (Flask) → RDS → CloudWatch.

Secure **IAM least-privilege roles** for EC2, RDS, and ALB.
**Auto Scaling EC2 instances** for high availability.
**Multi-AZ RDS** for database resiliency.
Frontend is **responsive HTML/Bootstrap**, allowing patients to book, cancel, or reschedule appointments.
Deployed using **Infrastructure-as-Code** (Terraform/CloudFormation optional).

View the full repository and backend examples:

GitHub Repo