Healthcare · United States
A US digital orthodontics provider running on AWS needed stronger governance, security, monitoring and disaster recovery to work toward HIPAA and SOC 2 readiness. Saints & Masters separated accounts, upgraded EKS and Karpenter, added CloudTrail, WAF, CloudWatch and RDS backups, documented a Pilot Light DR plan and set up ongoing managed services.
The client is a healthcare technology company that offers digital orthodontic treatment. Its business and application workloads run on AWS. Because it handles patient data, the company works toward HIPAA and SOC 2 readiness, which requires strong governance, audit visibility and documented operating processes. The containerized platform needed more maturity in account governance, security hardening, platform version support, monitoring, database backup and disaster recovery readiness.
Management, Production and Staging responsibilities were not clearly separated. Administrative access needed tighter, least-privilege control, operating processes varied across accounts, and visibility of infrastructure and security activity was limited.
The VPN server on Amazon EC2 needed stronger host-level security and tighter network traffic controls. Inbound and forwarding firewall policies were not restrictive enough, unnecessary traffic reached the VPN access point, there was no central audit trail of AWS API activity, and web-facing applications had no web application firewall.
The Amazon EKS cluster and the Karpenter autoscaler were running versions in extended support, which raised operating risk and support costs.
Saints & Masters worked with the client to modernize its AWS environment into a more controlled, secure and closely monitored platform, without disrupting the existing applications.
The environment was organized around separate Management, Production and Staging accounts, each with clear administrative boundaries and a structured model for infrastructure management and change control.
The Amazon EKS cluster and Karpenter were upgraded from extended-support versions to the latest stable releases, improving supportability and reducing the risk of running old versions.
Amazon CloudWatch dashboards and alarms track server health and alert the team when defined operating thresholds are crossed.
Automated backups with defined retention periods were enabled on the relevant Amazon RDS databases. A Pilot Light disaster recovery strategy was documented, with failover procedures and a reusable DR template. Planning targets are an RTO of 4 hours and an RPO of 1 hour.
These controls work together to support compliance activities and future audit evidence: audit logging, monitoring, web protection, access control, backup retention, DR documentation and structured change management.
Amazon EKS, Karpenter, Amazon RDS / Aurora, AWS WAF, AWS CloudTrail, Amazon CloudWatch