AWS Security ChangesHomeSearch

AWS connecthealth high security documentation change

Service: connecthealth · 2026-03-16 · Security-related high

File: connecthealth/latest/userguide/data-protection.md

Summary

Removed section about zero-persistence architecture and data residency configuration. Deleted explicit statement that patient data is not stored long-term.

Security assessment

Removal of data retention policies and data residency controls could indicate changes in PHI handling practices. Explicit security assertion about not storing patient data long-term was deleted, which may impact compliance with healthcare data protection requirements.

Diff

diff --git a/connecthealth/latest/userguide/data-protection.md b/connecthealth/latest/userguide/data-protection.md
index 6a6d4d756..5cebfbc74 100644
--- a//connecthealth/latest/userguide/data-protection.md
+++ b//connecthealth/latest/userguide/data-protection.md
@@ -5 +5 @@
-Data handled by Amazon Connect HealthEncryption at restEncryption in transitData residency and zero-persistence architecturePHI handlingCross-Region Inference (CRIS) disclosureService improvement and how to opt out
+Data handled by Amazon Connect HealthEncryption at restEncryption in transitPHI handlingCross-Region Inference (CRIS) disclosureService improvement and how to opt out
@@ -34 +34 @@ Amazon Connect Health handles a variety of data related to healthcare interactio
-  * **Patient data** — Patient information retrieved in real time from EHR systems or other external data sources during each interaction. This data is not stored long-term within the service.
+  * **Patient data** — Patient information retrieved in real time from EHR systems or other external data sources during each interaction.
@@ -70,6 +69,0 @@ When Amazon Connect Health integrates with AWS services, data is always encrypte
-## Data residency and zero-persistence architecture
-
-Amazon Connect Health employs a zero-persistence architecture for patient data. Patient information is retrieved in real time from EHR systems or other external data sources during each interaction and is not stored long-term within the service. Patient data is not retained beyond the duration of the active call session.
-
-Customers with data residency requirements can configure Amazon Connect and Amazon Connect Health to operate within their required AWS Regions.
-