Amazon Web Services (AWS) Healthcare HIPAA Review
SCORE: 9.6/10Vendor: Amazon Web Services, Inc. · Pricing: Pay-as-you-go (BAA included free)
Who It's For & Best Use Case:
Best for healthcare startups & scalable cloud infrastructure
Notable Gaps & Compliance Caveats:
- ⚠ Default configurations (e.g. unencrypted S3 buckets) are NOT HIPAA compliant out of the box.
- ⚠ Requires AWS Artifact click-through execution before storing any ePHI.
- ⚠ IAM least-privilege policies must be manually configured and enforced.
Amazon Web Services, Inc. Shared Responsibility Warning
CRITICAL COMPLIANCE NOTICEExecuting a BAA with Amazon Web Services, Inc. does not make your organization automatically HIPAA compliant. The vendor only secures the cloud infrastructure; your team is legally liable under 45 CFR § 164 for proper client-side configuration:
- ▪ Sign the AWS Business Associate Addendum in AWS Artifact before provisioning resources.
- ▪ Enable AWS CloudTrail across all regions and send logs to an encrypted, write-once S3 bucket.
- ▪ Enforce default server-side encryption with AWS KMS customer-managed keys (CMKs) on S3, EBS, and RDS.
- ▪ Disable all public access blocks on S3 buckets containing ePHI.
- ▪ Implement AWS GuardDuty and AWS Config rules for HIPAA conformance pack monitoring.