Yes Checked 2026-10-20. AWS makes a BAA available to every AWS account through AWS Artifact, and Amazon Bedrock and Amazon Bedrock AgentCore are listed as HIPAA Eligible Services. The main exclusion is any AWS service that is not on the HIPAA Eligible Services list. This directory is published by Chanty, Inc.; Chanty has no relationship to this vendor entry.
Short answer
A BAA for Amazon Bedrock and Amazon Bedrock AgentCore is available on all AWS accounts. PHI may be processed only in HIPAA Eligible Services, and only after the AWS BAA has been accepted. For teams building AI agents, AgentCore is the listed service to check, alongside Bedrock itself.
HIPAA status here is a matter of BAA terms, listed services and your own configuration. It is not a product property, and AWS does not offer a HIPAA certification for Bedrock. For definitions of BAA and PHI, see the HIPAA glossary (BAA, PHI). For other tools, see Is it HIPAA compliant? All vendors.
Which plans include a BAA
| Plan | BAA | How it is obtained | Extra cost |
|---|---|---|---|
| All AWS accounts | Available | Review and accept the AWS BAA in AWS Artifact in the AWS Management Console | Not published by the vendor |
No excluded plans are listed in the sources, so this table has a single row.
What the BAA covers and what it excludes
Covered (listed as HIPAA Eligible Services):
- Amazon Bedrock
- Amazon Bedrock AgentCore
Excluded:
- AWS services that are not on the HIPAA Eligible Services list.
This matters most in a pipeline. A clinic assistant that reads intake notes, calls a model through Bedrock and writes results to storage is only as covered as its weakest link. Every other service that touches the PHI must itself be on the eligible list, or be covered some other way. Check each one by name rather than assuming the BAA follows the data. The parent-level vendor check is at Is AWS HIPAA compliant?.
Security controls the vendor publishes
| Control | Published status |
|---|---|
| Encryption in transit | Yes |
| Encryption at rest | Yes |
| Audit log | Yes |
| Access controls | Not published by the vendor |
| SSO | Not published by the vendor |
| Data residency | Not published by the vendor |
| SOC 2 | Yes |
| HITRUST | Not published by the vendor |
| ISO 27001 | Yes |
This table reports what the sources state. It does not describe algorithms, key management or regions, because the sources do not.
How to use Amazon Bedrock with PHI
- Accept the BAA first. Review and accept the AWS BAA in AWS Artifact before any PHI enters the account. Testing with real patient notes "just to see" comes before the BAA only if you accept the exposure.
- Use only HIPAA Eligible Services. Check the AWS HIPAA Eligible Services Reference for each service you plan to use.
- Confirm every service in the pipeline. Storage, queues, logging and any front-end that handles the same data must be on the list too.
- Configure access and logging. Decide who can call the models and agents, and review the audit log your account produces. Access-control details are not published in the sources, so document your own settings.
- Set internal policies and train staff. Define which workflows may send PHI to an AI model, and who approves new ones.
- Record the vendor in your inventory. Note the BAA date, the services in scope and the owner.
- Re-check status on a schedule. Eligibility lists change, so confirm against the live list at each review.
Compliance depends on the signed BAA, your configuration and your policies together. The BAA alone does not make an organization compliant.
Alternatives with a BAA
Listed for reference, not ranked. Browse more in HIPAA-compliant software by category.
- Microsoft Azure: conditional.
- OpenAI ChatGPT and API: conditional.
- Anthropic Claude: conditional; BAA from the Enterprise plan.
- Doximity GPT: yes; BAA on the Member plan (free).
- Fireflies.ai: conditional; BAA from the Enterprise plan.
Sources
- HIPAA Eligible Services Reference – Amazon Web Services (AWS) — Trust center, checked 2026-10-20. "not to use these HIPAA Eligible Services for any purpose or in any manner involving Protected Health Information"
- HIPAA Compliance – Amazon Web Services (AWS) — BAA page, checked 2026-10-20. "To review, accept, and manage the status of the BAA for your account, sign in to AWS Artifact in the AWS Management Console."
- Secure Gen AI Apps – Amazon Bedrock Security and Privacy – AWS — Trust center, checked 2026-10-20. "Bedrock is in scope for common compliance standards including ISO, SOC, CSA STAR Level 2, is HIPAA eligible"
- Secure Gen AI Apps – Amazon Bedrock Security and Privacy – AWS — Trust center, checked 2026-10-20. "Your data is encrypted in transit and at rest."
Changes
No changes recorded since first verification on 2026-10-20. See recent changes in vendor HIPAA status.
FAQ
Is Amazon Bedrock HIPAA eligible?
Yes. AWS lists Amazon Bedrock as a HIPAA Eligible Service. PHI may be processed in it only after the AWS BAA is accepted. Source checked 2026-10-20.
How do I get a BAA for Amazon Bedrock?
The BAA is available to every AWS account. Review and accept it in AWS Artifact in the AWS Management Console. AWS does not publish an extra cost for it.
Does the AWS BAA cover Amazon Bedrock AgentCore for AI agents?
Yes. Amazon Bedrock AgentCore is listed as a HIPAA Eligible Service alongside Amazon Bedrock. Other services your agents use must be on the list as well.
Is data in Amazon Bedrock encrypted?
AWS's published sources state encryption in transit and encryption at rest. They do not describe end-to-end encryption, and details on algorithms and key management are not published in the sources.