> If you are working with AWS your application and your whole organization is at the whims of Amazon.
Part of freedom is the freedom to do stupid things.
> You will not even be able to migrate if you are tied into those API's and services because they are not same across cloud providers.
VPCs, Instances, Load Balancers and Storage are roughly-equivalent everywhere and the differences between are mostly-trivial. For the rest of the "shinies" they offer, well, see above.
> You don't even own the data or compute resource hosted on such cloud services because just by a single notice from a government agency your account will be blocked without access to your own data or compute resources.
If you think this doesn't also apply to your physical racks in datacenters, you've got another thing coming. Ask Lavabit.
Design for this in your strategy. You can still "own" your data and have it hosted in the cloud too. There's no reason to have to be exclusive.
> In terms of technical freedom you will have less of it and will be tied into proprietary extensions, API and services offered by those cloud providers.
As mentioned before, stick to running in instances and you're no differently off than anywhere else you can operate.
> On the other hand for self-hosted infrastructure government notice will not block access to resources owned by you and data in those resources. You can respond to notice and continue using those resources until court rules.
Absolutely not. With a warrant, the authorities will come and take your shit. They have guns. You don't. Ask Lavabit. Ask The Pirate Bay. Ask any blockchain drug pusher.