Apple obviously doesn't want companies like AWS to be renting Mac Minis as some sort of VDI solution. That's consistent with the (shitty) practices of Microsoft with respect to Windows, which confines Windows 10 hosting to Azure services.
Given the nature of Mac, an AWS MacOS service is unique in that it's very clear who the manufacturer of the underlying hardware is. Apple, given it's control-freak nature wanted to have a model that accommodated both their needs and the provided a clear, multi-provider model to do what developers need.
Windows 10 hosting is not confined to azure services, you can even bring your own license to AWS, or host your own terminal services, or run your own virtual apps, or literally anything.
I was imprecise in my wording. You cannot bring a shared Windows 10 virtual desktop to any provider that is not Microsoft Azure. Azure uses a delivery model based on tech for education customers that allowed 4-5 K-12 students to work from 1 PC via thin clients, and that model is only available on Azure. (And it's really cheap.)
If you do BYOL of Windows 10 on a non-Azure cloud service, you need to meet specific Microsoft EA requirements, and you must run on dedicated hardware. If you look at the AWS BYOL model for Workspaces, it very similar in cost to the Apple on AWS model. (https://aws.amazon.com/workspaces/pricing)
Apple obviously doesn't want companies like AWS to be renting Mac Minis as some sort of VDI solution. That's consistent with the (shitty) practices of Microsoft with respect to Windows, which confines Windows 10 hosting to Azure services.
Given the nature of Mac, an AWS MacOS service is unique in that it's very clear who the manufacturer of the underlying hardware is. Apple, given it's control-freak nature wanted to have a model that accommodated both their needs and the provided a clear, multi-provider model to do what developers need.