Overview of Project ☁️

Scenario

MediCare Hub is a lightweight medical application used by clinics to manage patient records and appointment tracking. Originally hosted using traditional infrastructure, it lacked fault tolerance and high availability. Any single EC2 or database failure could lead to downtime and loss of access to critical medical data.

To ensure reliability and resilience, the application is now being lifted and shifted to AWS, using best practices from the Reliability Pillar of the AWS Well-Architected Framework. The goal is to build an infrastructure that auto-recovers from failures and continues to serve users even during disruptions like instance crashes or Availability Zone (AZ) outages.

Your Role

In this project, you’ll take on the role of a Solutions Architect focused on reliability engineering. Your mission is to rearchitect the app’s infrastructure to ensure it remains available and self-healing, even in the event of failures while still being cost-efficient and scalable.

You’ll deploy a highly available web application stack across multiple AZs, with intelligent DNS routing and health checks, all monitored via CloudWatch.

What You'll Learn

This hands-on project will help you master:

• Designing fault-tolerant Multi-AZ architectures
• Auto-scaling EC2 instances with health checks and recovery
• Configuring DNS failover using Route 53 health checks
• Setting up Multi-AZ RDS for database resilience
• Setting up Shared Storage with EFS

Steps To Be Performed 👩‍💻

We'll go through the following steps in the next few lessons.

1. Set up EC2 Launch Template with UserData to install the medical app
2. Deploy an Auto Scaling Group across two Availability Zones
3. Configure an Application Load Balancer (ALB) to distribute traffic
4. Launch a Multi-AZ RDS database for resilient data storage
5. Set up Route 53 DNS with health checks and failover behavior

Services Used 🛠

• Amazon EC2 – Auto Scaling app instances across multiple AZs
• Application Load Balancer (ALB) – Distribute traffic and monitor instance health
• Amazon RDS (Multi-AZ) – Highly available relational database
• Amazon Route 53 – DNS routing with health checks and failover
• Amazon S3 – Backup for DNS Failover
• Amazon EFS – Shared storage across EC2 instances

Estimated Time & Cost ⚙️

• Estimated time: ~3 to 4 hours
• Cost: ~$2–5

➡️ Architectural Diagram

This is the architectural diagram for the project:

➡️ Final Result

By the end of this project, you will have transformed MediCare Hub into a resilient, production-grade application infrastructure on AWS.

Key reliability features achieved:

• Multi-AZ EC2 and RDS deployment for fault tolerance
• Auto-healing EC2 instances using health checks and ASG
• Route 53 DNS failover to maintain app availability
• Optional enhancements like EFS, backup S3 failover, and alerts

You’ve not only improved uptime, you’ve aligned with the Reliability Pillar of the AWS Well-Architected Framework, making MediCare Hub ready for real-world operations.