If you handle medical or health data, not all of Bedrock's AI features are approved for that use — you must check AWS's specific approved list before processing any health information through Bedrock.
This analysis describes what AWS Bedrock's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision creates a feature-level compliance boundary within a single service offering. Organizations subject to HIPAA must verify feature eligibility before using Bedrock to handle PHI, as non-eligible features lack BAA protections and therefore cannot lawfully process PHI under HIPAA requirements.
The updated terms now explicitly state that AWS IoT SiteWise Scenario Discovery is not designed for real-time vehicle control and cannot be used as the sole basis for determining vehicle safety or regulatory compliance. Organizations deploying this service must implement independent human monitoring and safety validation before using its outputs to support vehicle system decisions. The terms make clear that AWS assumes no responsibility for uses that violate these constraints.
View change record →The updated terms establish new restrictions on how AWS Capacity Reservations may be used. Specifically, customers purchasing On-Demand Capacity Reservations can no longer resell them to other parties, and AWS reserves the right to cancel the purchase or terminate running instances if the company suspects resale activity. For Capacity Blocks for ML, the grace period before instance termination increased from 30 minutes to 60 minutes for UltraServer instance types, allowing slightly more time to complete workloads. The Amazon Sidewalk qualification program was renamed and simplified, but the underlying security and operational requirements remain in effect.
View change record →The updated terms establish a formal framework for AWS Bedrock's free exploration services, clarifying the operational boundaries and responsibilities. AWS reserves the right to discontinue these services at any time without prior notice, meaning customers cannot rely on their continuation for production planning. Customers are solely responsible for testing, deploying, and maintaining any code, documents, or AI solutions AWS provides, including determining whether those solutions comply with applicable law. AWS retains the right to develop competing products based on content it creates during these engagements, though this does not override existing non-disclosure agreements. Customers are prohibited from requiring AWS personnel to sign additional terms as a condition of receiving free services, and any such documentation signed by AWS personnel is void.
View change record →Removal of this provision eliminates explicit guidance on HIPAA BAA eligibility for different Bedrock features, potentially shifting compliance responsibility entirely to customers to research AWS documentation.
View full change record →Healthcare businesses using unapproved Bedrock features to process patient health data face HIPAA enforcement exposure, which can result in significant financial penalties and reputational harm — with the risk borne entirely by the customer, not AWS.
How other platforms handle this
In assessing misuse, we consider factors such as evidence that a report was motivated by bias or hatred (e.g., based on protected characteristics such as race, sexual orientation, or gender identity) or other malicious intent.
We review account behavior and content that Members create, send, and publish in Mailchimp, including Campaigns and Websites.
We allow Content that names individuals in the highest positions in a company who have broad influence over the work environment, as long as the Content describes the individual's behavior or performance at work.
"Not all Amazon Bedrock features are covered under the AWS Business Associate Addendum. You should review the AWS HIPAA eligible services list to determine which Amazon Bedrock features may be used to process Protected Health Information.Excerpt from AWS Bedrock's AWS Service Terms
REGULATORY FRAMEWORK: This provision directly implicates HIPAA 45 CFR Parts 160 and 164 (Privacy and Security Rules), the HITECH Act (42 U.S.C.
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
Get the research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.
This provision creates a feature-level compliance boundary within a single service offering. Organizations subject to HIPAA must verify feature eligibility before using Bedrock to handle PHI, as non-eligible features lack BAA protections and therefore cannot lawfully process PHI under HIPAA requirements.
Healthcare businesses using unapproved Bedrock features to process patient health data face HIPAA enforcement exposure, which can result in significant financial penalties and reputational harm — with the risk borne entirely by the customer, not AWS.
ConductAtlas has identified this type of provision across 142 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by AWS Bedrock.