HIPAA-Compliant AWS Infrastructure, Defined as Code
Deploy secure, modular, and battle-tested AWS environments utilizing Terraform blueprints. Engineered specifically to satisfy the HIPAA/HITECH Technical Safeguards with zero manual configuration.
$
Hardened to Meet CFR § 164.312 Safeguards
Every module in the stack corresponds directly to a technical safeguard mandated by the HIPAA Security Rule.
Data Isolation & Network Security
Deploy databases (RDS PostgreSQL) and compute workloads (ECS Fargate) solely in isolated private subnets. Enforce zero public routing. Secure external ingress through AWS WAFv2 and AWS Client VPN tunnel interfaces.
Encryption Everywhere
Enforce AES-256 Server-Side Encryption (SSE-KMS) backed by a Customer Managed Key (CMK) with automated annual rotation. Reject non-HTTPS traffic on S3 and mandate SSL/TLS on database channels.
Immutable Auditing & Monitoring
Capture management and S3 data-plane events using AWS CloudTrail. Centralize system activity in KMS-encrypted CloudWatch Log Groups, retaining records for a clinical-audit compliant 365 days.
Integrity & Disaster Recovery
Protect ePHI from accidental deletion or malicious modification. Enforce S3 Object Versioning alongside automated daily snapshot backups utilizing AWS Backup vaults with custom retention locks.
Hardened AWS Architecture Blueprint
Hover over the components in the interactive network topology diagram to examine their configuration details and regulatory mappings.
AWS VPC (Isolated Network)
Provides physical and logical network boundary isolation.
Hardened Security Rules
- Custom subnets with zero direct public routes
- VPC Flow Logs enabled for security analysis
- PrivateLink Endpoints route AWS API traffic internally
Modular Service Catalog
Explore the 13 modular, production-ready services included in the stack. Click on any module to view its exact technical security controls.
VPC (Virtual Private Cloud)
services/vpc
Logical network isolation for compute workloads and database clusters.
KMS (Key Management Service)
services/kms
Centralized Customer Managed Keys with automated rotation.
Amazon S3 (Simple Storage Service)
services/s3
Secure, versioned, and encrypted patient file storage.
RDS PostgreSQL (Database)
services/rds
Relational database service in multi-AZ groups with SSL forced.
Amazon HealthLake (FHIR Store)
services/healthlake
Standardized HL7 FHIR R4 clinical data storage.
ECS Fargate (Container Compute)
services/fargate
Serverless container execution inside isolated subnets.
AWS Client VPN (Secure Access)
services/vpn
Certificate-authenticated VPN tunnels for administrators.
AWS WAFv2 (Web ACL)
services/waf
Web Application Firewall shielding public Load Balancers.
AWS CloudTrail (Auditing)
services/cloudtrail
Administrative API and S3 data-plane audit logging.
CloudWatch (Encryption Logs)
services/cloudwatch
Centralized, encrypted logs with a 365-day retention policy.
Secrets Manager (Credentials)
services/secretsmanager
Secure storage and rotation of credentials and API keys.
AWS GuardDuty (Threat Intel)
services/guardduty
Intelligent scanning of flow logs and trails for anomalies.
AWS Backup (Disaster Recovery)
services/backup
Automated daily backups with custom vault locks.
Compliant Integration Templates
Examine production-ready, security-hardened configurations. Switch between infrastructure blueprints and application logic patterns.
Select Template
§ 164.312(a)(2)(iv) Encryption, § 164.312(c)(1) Integrity, § 164.312(e)(1) Transmission
Configures default KMS-SSE bucket encryption, blocks all public access paths, enforces object versioning, and denies non-HTTPS transport operations.
1# HIPAA-Compliant S3 Storage Service2# Aligns with: 164.312(a)(2)(iv) Encryption, 164.312(c)(1) Integrity, 164.312(e)(1) Transmission Security34resource "aws_s3_bucket" "phi" {5bucket = var.bucket_name6force_destroy = false78tags = {9Environment = var.environment10Compliance = "HIPAA"11}12}1314resource "aws_s3_bucket_public_access_block" "phi_block" {15bucket = aws_s3_bucket.phi.id1617block_public_acls = true18block_public_policy = true19ignore_public_acls = true20restrict_public_buckets = true21}2223resource "aws_s3_bucket_versioning" "phi_versioning" {24bucket = aws_s3_bucket.phi.id25versioning_configuration {26status = "Enabled"27}28}2930resource "aws_s3_bucket_server_side_encryption_configuration" "phi_encryption" {31bucket = aws_s3_bucket.phi.id3233rule {34apply_server_side_encryption_by_default {35kms_master_key_id = var.kms_key_arn36sse_algorithm = "aws:kms"37}38bucket_key_enabled = true39}40}4142resource "aws_s3_bucket_policy" "phi_policy" {43bucket = aws_s3_bucket.phi.id4445policy = jsonencode({46Version = "2012-10-17"47Statement = [48{49Sid = "EnforceTLSRequestsOnly"50Effect = "Deny"51Principal = "*"52Action = "s3:*"53Resource = [54aws_s3_bucket.phi.arn,55"${aws_s3_bucket.phi.arn}/*"56]57Condition = {58Bool = {59"aws:SecureTransport" = "false"60}61}62}63]64})65}
Managing the 18 PHI Identifiers
Under the HIPAA Privacy Rule, clinical data combined with any of these 18 identifiers constitutes Protected Health Information (PHI).
The 18 PHI Safeguards
To prevent accidental disclosures in application logs, error payloads, and diagnostic telemetries, these identifiers must be systematically scrubbed or replaced with database-generated UUIDs.