-
Notifications
You must be signed in to change notification settings - Fork 1
Home
Background
A regional hospital, HealthCare North, recently faced an unexpected setback when their sole cloud engineer resigned without notice, leaving no documentation for their cloud environment. The hospital's website, a critical component for patient communication and information dissemination, is currently hosted on an expensive, traditional cloud server setup. The website is static but the current hosting solution incurs high costs and requires significant administrative oversight.
Business Problem
The absence of documentation and reliance on a single engineer have left HealthCare North vulnerable. The current website hosting solution is not only costly but also lacks efficient DevOps practices, leading to instances where untested changes caused website issues. HealthCare North seeks a more cost-effective, low-maintenance cloud solution that aligns with best DevOps practices to ensure website reliability and performance.
Project Objective
The primary goal is to transition HealthCare North's website from its current costly and high-maintenance cloud server setup to a more economical and efficient AWS service, specifically leveraging a static S3 website. This move aims to reduce costs and administrative overhead. Additionally, the hospital wants to establish sound DevOps practices, including a CI/CD pipeline with proper testing mechanisms, to avoid untested changes going live.