I regret that I cannot answer this question in the way you have phrased it, because you can't just check a box and say that a cloud host is suddenly HIPAA compliant or not. There are various procedural safeguards which you'll need, the absence of which will make any technical safeguards irrelevant from a compliance perspective. For example, one of the requirements is that you have a nominated HIPAA officer, another is that you have a written policy to discipline employees who abuse patient health information. You need both of these things regardless of whether your host makes certain aspects of compliance with the Security Rule easier.

About those things: HIPAA was apparently drafted by Congressional aides, not by technologists, so the Security Rule establishes a bunch of checkboxes which have eff all relevance to my main concerns as a systems engineer about application security.

For example, HIPAA and the assorted guidance is, as far as I know, totally silent on what this:

Do you have procedures for creating, changing, and safeguarding passwords?

actually means when the bcrypt hits the road. I'm pretty sure that "Yes, we do. We enforce 8 character maximum passwords, they have to be changed every 3 weeks and 1 day except when the anniversary date falls on a Tuesday, and they are secured in our database by ROT13, an advanced encryption technology." is facially compliant as long as you have written it down somewhere. There is very little in terms of either best practices or safe harbors.

This is a long way to say that you probably can't take an application and HIPAA-ify it by writing a check to a hosting provider.

Given that you have the procedural and technical safeguards in place, I'm personally of the opinion (and feel free to check with your lawyer) that the right words, procedures, and application-level security features make it possible to host HIPAA-compliant applications on most common cloud providers.

I am not a lawyer, this is not legal advice, yadda yadda.