Menu
just want to ask, if anyone faced to deploying Azure Stack into Amazon AWS.
Because of very specific reason in very specific country with very specific customer, we can not use Azure services in this country. But customer is ok with using Amazon AWS.
So the idea is to deploy Azure Stack into Amazon AWS to avoid rewriting whole app.
Do you ever even heard about this? Is it possible? What difficulties can arise?
542
If you already use Azure DevOps, the AWS Toolkit for Azure DevOps makes it easy to deploy your code to AWS using either AWS Elastic Beanstalk or AWS CodeDeploy. No changes to your existing build/release pipeline or processes are required to integrate with AWS Services. You can even deploy serverless applications and .
The second way you can connect your AWS and Azure environments is to build private lines to the two hyperscalers by buying dedicated circuits from your telco provider.
Using both for a single application is possible, but there are drawbacks: There is inter-cloud latency – When communication passes from AWS to Azure or the reverse, there will be greater latency. Some applications will be able to tolerate this, but not all, especially if traffic is high.
Azure Stack HCI solution overview - Azure Stack HCI | Microsoft Learn. This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
It is not possible to deploy Azure Stack onto Amazon AWS because one of the Requirements is SLAT support which is a form of hardware virtualisation.
The basic premise of Azure Stack is that you have a bunch of Hyper-v servers that emulate the Azure Cloud. The hardware that you use to create the Hyper-v servers needs specific capabilities in the underlying processor (basically to do with how resources are allocated, allowing the hypervisor to give direct access to hardware resources rather than emulating them, which is very processor intensive)
While it is entirely possible to have nested hypervisors (that is a hypervisor running within a hypervisor) AWS intentionally disable the processor capabilities that allow it, so that you cannot run a hypervisor within their EC2 instances. This is a business (and perhaps technical) decision on Amazon's part (and every other cloud operator)
54
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
