All articles
HIPAAHealthcareGuides

HIPAA-Compliant Hosting on AWS, Azure and Google Cloud

How HIPAA-compliant hosting works on AWS, Azure and Google Cloud: getting the BAA, eligible services, shared responsibility and the settings you must own.

By the Clarigo Editorial Team · November 18, 2026 7 min read

Share
Short answer: HIPAA-compliant hosting means three things together: a business associate agreement (BAA) with the cloud provider, protected health information (PHI) kept only in the services that BAA covers, and your own configuration of encryption, access control, logging and backups. AWS, Microsoft Azure and Google Cloud all offer a BAA and all say there is no HIPAA certification for a cloud. The provider secures the infrastructure; everything you build on it is your responsibility.

"Is AWS HIPAA compliant?" is the wrong question. No cloud is HIPAA compliant on your behalf. A cloud can be used in a HIPAA-compliant way, and the difference is the work this article describes.

It is general information, not legal advice. Provider terms and service lists change, so check each provider's current page, linked below, before you commit.

Why the cloud provider needs a BAA

Under HIPAA, a vendor that creates, receives, maintains or transmits PHI for a covered entity is a business associate, and a vendor doing the same for a business associate is a subcontractor business associate. Microsoft's Azure HIPAA documentation states it plainly: when a covered entity uses a cloud service provider, the provider becomes a business associate, and when a business associate subcontracts with a cloud provider to handle PHI, the provider also becomes a business associate.

So if your product stores PHI for clinics, the chain is: clinic, then you (business associate), then the cloud provider (your subcontractor). Each link needs a BAA. Note also Microsoft's answer to a common question: your SaaS customers do not need their own BAA with Microsoft. They sign a BAA with you.

There is no HIPAA certification for clouds

All three providers say the same thing in their own words:

  • AWS states that there is no HIPAA certification for a cloud service provider, and describes aligning its HIPAA risk program with FedRAMP and NIST SP 800-53.
  • Microsoft states that there is currently no HHS-approved certification program through which a cloud provider could demonstrate HIPAA compliance, and points to mappings such as NIST SP 800-66, NIST's guide to implementing the HIPAA Security Rule.
  • Google states that HHS does not offer a certification program for HIPAA compliance.

Treat any "HIPAA-certified hosting" claim as marketing. What you can verify is the BAA, the covered service list and your own controls.

How the BAA works on each provider

AWSMicrosoft AzureGoogle Cloud
How you get the BAAReview and accept it in AWS Artifact in the consoleIncluded by default through the Microsoft Product Terms and Data Protection Addendum for customers that are covered entities or business associates; no separate contractReview and accept it following Google's instructions; you first confirm your HIPAA role
Which services are coveredOnly services listed as HIPAA eligible in the BAA; see the HIPAA Eligible Services ReferenceServices in Microsoft's audit-scope list for HIPAA BAA coverageGoogle Cloud infrastructure and the products named on its HIPAA page
Who is responsible for complianceShared, under the AWS Shared Responsibility ModelYou are responsible for your own compliance program; Microsoft does not inspect or approve your appsShared between you and Google; you secure your environment and applications
Official pageAWS HIPAA complianceAzure HIPAA offeringGoogle Cloud HIPAA

We have deliberately not copied the service lists here. They change, and the provider's page is the only list that counts.

HIPAA-eligible services: the rule that catches teams out

On the AWS HIPAA page, AWS says you may use any AWS service in an account designated for HIPAA, but should only process, store and transmit PHI in the services listed as HIPAA eligible. Microsoft and Google Cloud work the same way through their own covered-service lists, and Google notes limits on some products.

This is where real projects slip. A team builds the core app on covered services, then adds a new analytics tool, a managed search index, an AI service or a third-party monitoring product, and PHI starts flowing into something the BAA does not cover. Build a simple gate into your process: before any new service receives production data, check it against the current list and record the result.

Shared responsibility: what the provider does and what you do

The provider secures the data centres, hardware, network backbone and the managed services themselves. You own everything you configure: identities, network rules, encryption settings, logging, backups, your application code and your people. The HIPAA Security Rule technical safeguards in 45 CFR 164.312 apply to you whichever cloud you choose.

What you must configure

Encryption

Encryption is an addressable specification in the Security Rule, which means you implement it where reasonable and appropriate or document an equivalent. In the cloud it is almost always reasonable. Encrypt storage volumes, databases, object storage and backups at rest; force TLS on every endpoint, including internal service-to-service traffic; and decide who controls the keys, with key access logged and limited.

Access control

The rule requires unique user identification and an emergency access procedure, with automatic logoff as addressable. In practice: no shared root or admin accounts, single sign-on with multi-factor authentication, least-privilege roles, separate accounts or projects for production, short-lived credentials for engineers, and a documented break-glass process that alerts when used.

Logging and audit

Audit controls must record and examine activity in systems containing PHI. Turn on the provider's control-plane audit logs, keep your application's own record-level access log, send both to a separate, write-protected location, and keep PHI out of the log lines themselves. Logs that nobody reviews do little, so set alerts for unusual access and exports.

Backups and disaster recovery

The administrative safeguards in 45 CFR 164.308 make a data backup plan, a disaster recovery plan and an emergency mode operation plan required parts of the contingency plan. Back up automatically, encrypt the backups, copy them to a second region or account, and test a full restore on a schedule. A backup you have never restored is a hope, not a plan.

Everything around the cloud

  • No PHI in development or test environments unless they are secured like production.
  • Patch and scan operating systems, containers and dependencies.
  • Use the provider's compliance tooling. Microsoft, for example, offers an Azure Policy initiative mapped to HIPAA and HITRUST controls; such tools give a partial view, not a verdict.
  • Sign BAAs with the services around the cloud that see PHI: email, SMS, video, error tracking and AI model providers.

Common mistakes we see

  • Signing the BAA and stopping there. The agreement is the first step. Without the configuration work above, the environment is not protected.
  • PHI in a service the BAA does not cover. It usually arrives through a convenience feature: a managed search index, a reporting tool, an AI service or a third-party add-on from a marketplace.
  • PHI in logs and error reports. Request bodies, stack traces and debug output end up in log storage and in monitoring tools that may sit outside the BAA.
  • Copies of production data in test. A developer restores a backup into a staging account to reproduce a bug, and that account has none of the production controls.
  • Backups nobody has restored. The backup job reports success for months; the first real restore fails on a missing key or a changed schema.
  • One shared admin account. It defeats unique user identification and makes the audit log meaningless.
  • Assuming the provider's attestations cover your app. FedRAMP, ISO 27001 or CSA STAR results describe the provider's controls, not yours.

Each of these is cheap to prevent at the start and expensive to discover in an audit or after an incident.

A setup checklist

  1. Confirm your HIPAA role (covered entity or business associate) and sign or accept the provider's BAA.
  2. Create a dedicated production account or project for PHI.
  3. List every service that will hold PHI and check each against the covered list.
  4. Turn on encryption, audit logging and backups before any real data arrives.
  5. Set up identity with SSO, MFA and least privilege.
  6. Write down the contingency plan and test a restore.
  7. Run and document a risk analysis, and repeat it when the architecture changes.

Our HIPAA-compliant cloud hosting service runs this checklist for you, and a HIPAA compliance assessment reviews an existing environment. If you are choosing a provider, our AWS consulting, Google Cloud and Microsoft teams can help, and DevOps and cloud migration covers moving an existing system.

How we run our own products

Clarigo EHR is a cloud EHR built on these controls: encryption, role-based access, HL7 and FHIR interfaces, and an AI scribe that drafts notes for clinicians to sign. Clarigo Clinic OS keeps a full audit trail and signs a BAA before any patient data is touched.

About Clarigo Infotech

Clarigo Infotech is an AI-first software and app development company in Indore, India. Since 2016, our in-house senior team has delivered 600+ projects for clients in 20+ countries. Our HIPAA-trained team has HL7 and FHIR integration experience, and we offer 24/7 support. Senior engineers typically cost US$25 to US$49 per hour, a first version (MVP) is usually live in roughly 25 to 30 days, and you own the source code. Planning HIPAA hosting? Talk to our cloud team.

Frequently asked questions

Is AWS, Azure or Google Cloud HIPAA compliant?

+

None of them makes you compliant. Each offers a business associate agreement and a list of services covered by it, and each states that there is no HIPAA certification for cloud providers. You become compliant by keeping PHI in covered services and configuring encryption, access, logging and backups correctly.

How do I get a BAA from AWS, Azure or Google Cloud?

+

On AWS you review and accept the BAA in AWS Artifact. On Azure it is included by default through the Microsoft Product Terms and Data Protection Addendum for covered entities and business associates. On Google Cloud you review and accept it following Google's instructions after confirming your HIPAA role.

What are HIPAA-eligible services?

+

They are the cloud services a provider's BAA covers. AWS, for example, says you may use any service in a HIPAA account but should only process, store and transmit PHI in services listed as HIPAA eligible. Check each provider's current list before sending PHI to a new service.

Do my customers need their own BAA with the cloud provider?

+

Usually not. Microsoft's documentation says that customers of a healthcare SaaS product on Azure sign a BAA with the SaaS provider, not with Microsoft. You then hold the BAA with the cloud provider as your subcontractor.

Is encryption required for HIPAA hosting?

+

Encryption is an addressable specification in the Security Rule, so you must implement it where reasonable and appropriate or document an equivalent measure. For cloud storage, databases, backups and network traffic, encryption is the practical standard.

From our own work

Projects our team has delivered that relate to this article.

About the author

Clarigo Editorial Team

Written by the team at Clarigo Infotech, an AI-first software and app development company in Indore, India. Since 2016 our in-house team has delivered 600+ projects for clients in 20+ countries, and our articles draw on that work. Read about the company, or see our case studies and portfolio.

Found this useful? Share it with your team.

Planning something like this?

Get a free consultation. A senior engineer replies within one working day with a scoped plan.

How should we contact you?

No obligation. We reply within one working day.

Keep reading