HIPAA Compliant Hosting on AWS: Eligible Services and Who Secures What

AWS can host protected health information, but no AWS account is HIPAA compliant on its own. You accept the AWS BAA, keep PHI in the eligible services, and own the safeguards on your side of the shared responsibility line.

In short

  • To host protected health information on AWS you accept the AWS Business Associate Addendum in AWS Artifact, and then keep PHI only in the services on AWS's HIPAA Eligible Services Reference.
  • AWS secures the infrastructure that runs its services, while you secure what you build on it: the guest operating system, application code, firewall rules, encryption choices and who can access what.
  • The HIPAA Security Rule still applies to you in full, so you need your own risk analysis, access controls, encryption decisions and activity monitoring, configured inside those eligible services.

HIPAA compliant hosting on AWS means three things: your account or organization has accepted the AWS Business Associate Addendum (BAA), protected health information (PHI) lives only in services on AWS's HIPAA Eligible Services Reference, and you have configured those services to meet the HIPAA Security Rule. AWS itself says there is no HIPAA certification for a cloud service provider. Signing the BAA makes AWS your business associate for the infrastructure, and making your application compliant is still your work.

This guide is for CTOs and engineering leads moving a health product onto AWS, or checking an existing setup before a customer security review. It covers the BAA, the eligible services list, the shared responsibility split and the Security Rule safeguards that stay with you. The sources are AWS documentation and the regulation text, linked at the end.

Is AWS HIPAA compliant?

Not in the way the question usually means. AWS's HIPAA page states plainly that there is no HIPAA certification for a cloud service provider such as AWS. What AWS offers instead is a standard BAA, which is the contract HIPAA requires when a business associate handles PHI, and a list of services it has made eligible to create, receive, process, maintain or transmit PHI under that contract. AWS says it aligns its HIPAA risk management program with FedRAMP and NIST 800-53.

So the accurate claim is narrower: AWS can be part of a HIPAA compliant system if you sign its BAA, stay inside the eligible services and do your own share of the work. No hosting provider can make you compliant by itself.

How do you sign the AWS BAA?

You do it yourself in AWS Artifact, the console area for compliance reports and agreements. AWS's HIPAA page says to sign in to AWS Artifact to review, accept and manage the status of the BAA for your account. If you do not have permission, an administrator has to grant IAM access to Artifact.

  • Account agreement: accepting the BAA for a single account designates that account as one that can legally process PHI.
  • Organization agreement: if you use AWS Organizations, you can accept the BAA on behalf of every account in the organization. AWS's Artifact guide says all existing and subsequent member accounts are automatically covered.
  • Review and termination: Artifact also shows whether an agreement is accepted, lets you read its terms, and lets you terminate it and activate it again later.

Which one to choose depends on how you separate workloads. Keeping PHI in a dedicated set of accounts means development sandboxes and marketing sites never fall under the agreement by accident. An organization-wide BAA is simpler, but it means every account you create later is treated as able to process PHI, so your controls have to follow.

What has to be in the BAA chain if you sell software to providers?

If you are a software vendor serving hospitals or clinics, you are usually the business associate, and AWS is your subcontractor. AWS's HIPAA page notes that when a SaaS partner on AWS serves covered entities, those entities sign a BAA with the partner, not necessarily with AWS. You then hold the AWS BAA for your own accounts.

The Security Rule spells out what these contracts must say. Under 45 CFR 164.308(b)(1), a covered entity may let a business associate create, receive, maintain or transmit electronic PHI only if it obtains satisfactory assurances that the information will be safeguarded. Under 164.314(a), the business associate contract must require the associate to comply with the Security Rule, to make sure its subcontractors that handle electronic PHI agree to the same through their own contract, and to report security incidents, including breaches of unsecured PHI. Section 164.314(a)(2)(iii) applies the same requirements between a business associate and its subcontractor.

Which AWS services are HIPAA eligible?

The HIPAA Eligible Services Reference is the only list that counts, and it changes. At the time of writing, its last update was dated November 16, 2026. AWS says it adds eligible services based on customer demand and that customers can request new ones. Examples on the list include:

  • Compute and containers: Amazon EC2, AWS Lambda, Amazon ECS, Amazon EKS, AWS Fargate and Elastic Load Balancing.
  • Storage and backup: Amazon S3, Amazon EBS, Amazon EFS and AWS Backup.
  • Databases and analytics: Amazon RDS, Amazon Aurora, Amazon DynamoDB, Amazon Redshift, Amazon Athena, AWS Glue, Amazon OpenSearch Service and Amazon Kinesis Data Streams.
  • AI and machine learning: Amazon Bedrock, Amazon SageMaker, Amazon Comprehend Medical, Amazon Textract, Amazon Transcribe and AWS HealthLake.
  • Security and identity: AWS KMS, Amazon Cognito, Amazon GuardDuty, Amazon Inspector, Amazon Macie, AWS Secrets Manager, AWS WAF and AWS Shield.
  • Management and networking: AWS CloudTrail, Amazon CloudWatch, AWS Systems Manager, Amazon API Gateway, Amazon VPC and Amazon Route 53.

The rule that matters most is on AWS's HIPAA page: customers may use any AWS service in an account designated as a HIPAA account, but they should only process, store and transmit PHI in the HIPAA eligible services. In practice that means your architecture diagram needs a clear line around every place PHI can travel, including queues, caches, search indexes, log groups and analytics exports, and every service inside that line has to be on the list.

Watch for PHI in metadata. AWS's Bedrock data protection page, which repeats AWS's general guidance, strongly recommends never putting confidential or sensitive information into tags or free-form text fields such as a Name field, because that data may be used for billing or diagnostic logs. A patient name in an S3 object key, a resource tag or a CloudWatch alarm description is PHI in a place you did not plan for.

What does AWS secure, and what is left to you?

AWS describes the split as security of the cloud versus security in the cloud. AWS is responsible for protecting the infrastructure that runs all of its services: the hardware, software, networking and facilities. Your responsibility depends on which services you choose. With EC2, for example, AWS lists these as the customer's job:

  • Managing the guest operating system, including updates and security patches.
  • Any application software or utilities you install on the instances.
  • Configuring the AWS-provided firewall, called a security group, on each instance.
  • Managing your data, including encryption options.
  • Setting access permissions with AWS Identity and Access Management (IAM).

AWS also sorts controls into three groups. Inherited controls, such as physical and environmental protection of data centers, you take fully from AWS. Shared controls, such as patch management, configuration management, and awareness and training, apply at both the infrastructure layer and your layer. Customer-specific controls are yours alone. The more managed the service, the more AWS carries, but even with Lambda or Aurora the data, the access rules and the application logic stay with you.

Which Security Rule safeguards land on your side?

The technical safeguards in 45 CFR 164.312 map directly onto choices you make in AWS. Some implementation specifications are marked required and some addressable:

  • Access control: unique user identification and an emergency access procedure are required; automatic logoff and encryption and decryption of electronic PHI are addressable. On AWS this is IAM, your application's own user model, session timeouts and AWS KMS keys.
  • Audit controls: hardware, software or procedural mechanisms that record and examine activity in systems containing electronic PHI. AWS CloudTrail records API activity in your accounts; your application still has to record who viewed which patient record.
  • Integrity: protect electronic PHI from improper alteration or destruction, with an addressable mechanism to corroborate that it has not been altered.
  • Person or entity authentication: verify that whoever seeks access is who they claim to be.
  • Transmission security: guard against unauthorized access in transit, with addressable integrity controls and encryption. AWS's Bedrock documentation notes that AWS requires TLS 1.2 and recommends TLS 1.3 for communication with AWS resources.

AWS's general data protection advice lines up with these: protect account credentials, give each user only the permissions their job needs through IAM Identity Center or IAM, use multi-factor authentication on every account, log API and user activity with CloudTrail, and use AWS encryption services along with the default security controls. Amazon Macie, which is also on the eligible list, can help find sensitive data stored in S3.

Do you still need a risk analysis if you host on AWS?

Yes. Section 164.308(a)(1)(ii)(A) requires an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity and availability of the electronic PHI you hold, and 164.308(a)(1)(ii)(B) requires security measures sufficient to reduce those risks to a reasonable and appropriate level. Both are marked required. AWS's infrastructure controls feed into your analysis, but they do not replace it, because the risks that matter most for a health app usually sit in the application: broken access rules, PHI in logs, an export endpoint without authorization.

What does a sensible AWS setup for PHI look like?

There is no single blueprint, but the following checklist turns the sources above into decisions you can review. Use it as input to your own risk analysis, which you still have to do.

  • Accept the BAA in AWS Artifact for the accounts or organization that will hold PHI, and record who accepted it and when.
  • Keep PHI workloads in dedicated accounts, separate from development and experimentation.
  • Maintain an allowlist of services that may touch PHI, checked against the current HIPAA Eligible Services Reference before each new service is introduced.
  • Encrypt data at rest with AWS KMS keys you control, and require TLS for every connection.
  • Turn on multi-factor authentication for every human user and give each role the smallest set of permissions it needs.
  • Enable CloudTrail in every account and keep its logs where application engineers cannot alter them.
  • Keep identifiers out of tags, resource names, object keys and alarm descriptions.
  • Back up with AWS Backup and test restores, because availability is part of the Security Rule too.
  • Write down which controls you inherit from AWS, which are shared and which are yours, so an auditor or customer can follow the reasoning.

Can you run AI workloads on PHI in AWS?

Several AI services are on the eligible list, including Amazon Bedrock, Amazon SageMaker, Amazon Comprehend Medical, Amazon Transcribe and AWS HealthLake. For Bedrock, AWS documents that each model provider's models run in model deployment accounts owned and operated by the Bedrock service team, that model providers have no access to those accounts, and therefore that they have no access to Bedrock logs or to customer prompts and completions. The same rules apply as for any other service: PHI only in eligible services, and your own configuration of logging, encryption and access around them.

On our projects, we sign a BAA before anyone on the team sees PHI, scope access so that each clinician sees only their own patients, and run a penetration test before launch. Choosing eligible services is only the first step of that work.

Onix Systems has been building software since 2000 and has 370+ engineers. If you are planning a move to AWS or want a second opinion on an existing HIPAA setup, talk to one of our engineers. Our free five-day technical audit ends with a written report on your architecture, the BAA chain and the gaps worth fixing first.