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 remove the explicit reference to a Data Processing Addendum governing Anthropic data transfers, though the requirement to obtain opt-in consent for Anthropic model use remains in place. For Kiro users, the revised language now explicitly states that abuse detection includes retention and potential human review of inputs and outputs when selecting certain models. Users of Anthropic models on Bedrock should verify opt-in consent mechanisms in service documentation to understand data handling practices.
View change record →The updated terms establish a new project-based service structure for AWS (new) users, effective August 17, 2026, with new rules governing team member access and content ownership. Users who enable spend limits agree that AWS may suspend their account or project access upon reaching their limit, and may permanently close the account or project if not reactivated within an unspecified timeframe. Contributed content by team members becomes the project owner's property and is subject to a nonexclusive irrevocable license granted to all project members. You can configure AI services opt-out policies through AWS Settings; project owners can manage team member permissions and access controls.
View change record →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 →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.