- HIPAA + SOC 2 readiness foundation with audit-grade logging and encryption controls.
- Repeatable multi-environment deployment using nested CloudFormation and GitHub Actions.
- Resilient request path from DNS to ECS with Multi-AZ data and queues.
Architecture overview
High-level diagram showing the main production flow, telemetry paths, and compliance-oriented services.
- Request path: Route 53 routes traffic through ALB to ECS services.
- Data layer: ECS services use Multi-AZ RDS, Redis cache, and SQS queues.
- Controls: IAM + KMS with CloudWatch/CloudTrail for monitoring and auditability.
SRE approach
- Network: VPC with public/private subnets, NAT gateways, and flow logs.
- Compute: ECS services behind an ALB with autoscaling.
- Data: Multi-AZ RDS, Redis, and SQS for resilient workloads.
- Encryption: KMS-backed encryption for S3 and data stores.
- Identity: Least-privilege IAM with scoped access policies.
- Auditability: CloudTrail retention, GuardDuty, Inspector, and alarms.
- IaC: Nested CloudFormation stacks for repeatable environments.
- CI/CD: GitHub Actions for deployments and infrastructure security checks.
- Ops: DNS automation and secure rotation procedures for services.
Results
The platform now has a compliance-ready foundation and a repeatable delivery path that reduces manual deployment work while improving visibility and incident readiness.
A secure, scalable infrastructure foundation aligned with HIPAA and SOC 2 readiness requirements.
Infrastructure codified in CloudFormation with CI/CD automation and centralized observability.
Project URL
Public marketing site and entry point to the authenticated app.
Lessons learned
Building Around Notes from scratch reinforced the value of modular infrastructure and compliance-first design. Aligning network, compute, and security controls early made it easier to scale features and meet HIPAA and SOC 2 readiness goals.
