AWS Bedrock HIPAA Eligible BAA – What Healthcare Organizations Need to Know

Amazon Bedrock is a HIPAA-eligible AWS service that healthcare organizations can use for workloads involving electronic protected health information (ePHI), provided an AWS Business Associate Addendum (BAA) is in place and the environment is configured according to HIPAA requirements. This makes AWS Bedrock a practical foundation for healthcare AI applications that need access to sensitive patient or clinical information.

HIPAA eligibility does not mean an application becomes HIPAA compliant automatically. AWS secures the underlying cloud infrastructure while the organization remains responsible for its application architecture, access controls, data handling, monitoring and other safeguards under the AWS Shared Responsibility Model.

Is Amazon Bedrock HIPAA eligible?

Yes. As of September 2026, Amazon Bedrock appears on the official AWS list of HIPAA Eligible Services. AWS states that services on this list are eligible to create, receive, process, maintain or transmit ePHI subject to the shared responsibility model.

This distinction matters.

AWS does not offer a blanket statement that every application built with Bedrock is automatically HIPAA compliant. AWS also states that there is no HIPAA certification for cloud service providers such as AWS. Instead, organizations must build and operate their workloads in accordance with their own HIPAA obligations.

For example, a healthcare provider might use Bedrock to create an internal assistant that helps authorized employees find information from clinical documents. Bedrock can form part of that architecture, but the healthcare provider still needs to control who can access the application, where ePHI moves, how activity is logged and which connected services process the information.

What is the AWS BAA for Amazon Bedrock?

A Business Associate Addendum is a contract between AWS and a customer that addresses AWS’s responsibilities when protected health information is handled through eligible AWS services.

AWS states that it offers a standard BAA to customers. The agreement addresses the safeguards AWS applies to PHI and defines permitted uses and disclosures based on the services AWS provides.

Organizations can review, accept and manage their AWS BAA through AWS Artifact in the AWS Management Console. AWS Artifact can also be used to manage agreements across applicable AWS Organizations accounts.

The BAA needs to be addressed before PHI is processed through Amazon Bedrock. AWS specifically states that covered entities and business associates should not use HIPAA Eligible Services with PHI without first entering into an AWS business associate agreement.

Signing the BAA is therefore an important contractual step, but it is not the end of the implementation process.

Does an AWS BAA make Amazon Bedrock HIPAA compliant?

No. A signed AWS BAA does not automatically make your Bedrock application HIPAA compliant.

Think of the BAA as one requirement within a much larger compliance program. AWS is responsible for controls associated with the cloud infrastructure while customers remain responsible for how their applications and data are configured and used.

A company could have an AWS BAA in place and still create unnecessary HIPAA risk through poor application design.

For example, an organization could give too many employees access to a healthcare AI assistant. Another could place ePHI in application logs without appropriate controls. A development team could also connect Bedrock to another service without confirming whether that service is suitable for handling ePHI.

Each component of the architecture needs to be reviewed according to the data it receives, stores or transmits.

How should you build a HIPAA-focused Amazon Bedrock environment?

Start by mapping where PHI enters the application and every system it touches afterward.

A Bedrock application may connect to APIs, databases, document repositories, logging systems, authentication services and other AWS resources. If ePHI moves through those components, their HIPAA eligibility and configuration become part of the compliance discussion.

AWS states that customers may use other AWS services in a HIPAA-designated account but PHI should only be processed, stored or transmitted using HIPAA Eligible Services.

Access should also follow the principle of least privilege. Users and applications should receive only the permissions required to perform their jobs. AWS Identity and Access Management policies can help control which identities are allowed to invoke Bedrock resources and access supporting data.

Encryption should be considered across the full data path. That includes stored information and information moving between systems.

Logging and monitoring are equally important. Healthcare organizations need enough visibility to investigate suspicious behavior, operational problems and unauthorized access without unnecessarily exposing sensitive information inside logs.

What healthcare applications can be built with Amazon Bedrock?

Amazon Bedrock can support generative AI applications where organizations need controlled access to healthcare information.

One example is an internal knowledge assistant. A hospital may have thousands of approved policies, procedures and operational documents. Employees can spend considerable time searching across multiple repositories for the correct information. A Bedrock-based application can provide a conversational interface over approved sources while the surrounding architecture controls user access.

Another example is document summarization. Healthcare teams often work with lengthy records and administrative documents. Generative AI can assist with producing summaries for authorized workflows, provided the output is reviewed appropriately for the use case.

Bedrock can also support applications for contact centers, administrative workflows, document classification and internal employee assistance.

The key question is not simply whether Bedrock can perform the task. The organization must determine what data the application receives, who can access its responses and what happens to the information after the model generates an output.

Why work with an AWS Bedrock consultant?

An experienced AWS Bedrock consultant can help connect the AI use case with the security and infrastructure decisions required for a healthcare environment.

The work should begin with architecture rather than prompt engineering.

A consultant can review how PHI enters the proposed application, identify which AWS services interact with it and determine where stronger access, encryption, logging or data-handling controls may be required.

This becomes particularly important when Bedrock connects to existing healthcare systems, APIs, databases or document repositories. A technically successful AI proof of concept may not be suitable for production if its data flows were never designed around healthcare requirements.

An AWS Bedrock consultant can also help teams establish separate environments, IAM permissions, monitoring practices, model access controls and deployment processes before the application reaches real users.

Compliance decisions should still involve the organization’s security, privacy and legal teams. The consultant’s role is to make sure the technical architecture supports those requirements.

What should you check before putting PHI into Amazon Bedrock?

Before deploying a healthcare Bedrock workload, confirm that the AWS BAA is active for the appropriate account or organization and verify Amazon Bedrock against the current AWS HIPAA Eligible Services Reference.

Then review every AWS service and external system that may receive ePHI.

Document how PHI enters the system, where it is processed, whether it is stored, who can retrieve it and how access is audited. IAM permissions should be restricted to legitimate business requirements and encryption should be configured according to the organization’s security policies.

Development and testing environments deserve the same attention. Using real patient information in poorly controlled development systems can introduce risk even when the production environment has stronger safeguards.

Finally, review the architecture whenever new models, services, integrations or data sources are introduced.

Is AWS Bedrock a good choice for HIPAA workloads?

Amazon Bedrock gives healthcare organizations access to generative AI capabilities within the AWS ecosystem while being listed as a HIPAA Eligible Service. That makes it a viable option for organizations that need AI applications capable of working with ePHI under an appropriate AWS BAA.

The important distinction is between HIPAA eligible and automatically HIPAA compliant.

Bedrock provides an eligible service and AWS provides the contractual BAA framework. Your organization remains responsible for building and operating the workload correctly.