AWS Security ChangesHomeSearch

AWS AmazonS3: HIPAA guidance: don't put PHI in S3 bucket or object names

Service: AmazonS3 · 2026-11-18 · Documentation medium

File: AmazonS3/latest/userguide/s3-compliance.md

Summary

Replaced the link to the HIPAA whitepaper with a link to the HIPAA Eligible Services reference, and added a note instructing users not to write protected health information (PHI) in bucket or object names, keeping PHI only in the object body.

Security assessment

The added note is a data-protection best practice: bucket and object names can appear in logs, URLs, inventory reports, and third-party tooling, so embedding PHI there risks unintended disclosure. It documents safe handling of sensitive data but does not reference or remediate any specific vulnerability, CVE, or incident.

Evidence

+For HIPAA compliance, do not write protected health information (PHI) in bucket or object names. PHI must reside only in the object body.

Diff

diff --git a/AmazonS3/latest/userguide/s3-compliance.md b/AmazonS3/latest/userguide/s3-compliance.md
index 44a39d2..721c9d1 100644
--- a//AmazonS3/latest/userguide/s3-compliance.md
+++ b//AmazonS3/latest/userguide/s3-compliance.md
@@ -32 +32 @@ Your compliance responsibility when using Amazon S3 is determined by the sensiti
-  * [Architecting for HIPAA Security and Compliance](https://docs.aws.amazon.com/whitepapers/latest/architecting-hipaa-security-and-compliance-on-aws/architecting-hipaa-security-and-compliance-on-aws.html) outlines how companies use AWS to help them meet HIPAA requirements.
+  * [HIPAA Eligible Services](https://aws.amazon.com/compliance/hipaa-eligible-services-reference/) provides a full list of HIPAA-eligible AWS services.
@@ -46,0 +47,4 @@ Your compliance responsibility when using Amazon S3 is determined by the sensiti
+Note
+
+For HIPAA compliance, do not write protected health information (PHI) in bucket or object names. PHI must reside only in the object body.
+