AWS BYOL – License Mobility

After reading this about Azure we now come onto AWS!  Microsoft License Mobility – Amazon Web Services (AWS)

Like Azure’s Calculator, I was trying to find the cost estimates of BYOL Licenses with Software Assurance to AWS on Shared Services not Dedicated Hardware, this was proving fruitless , Because :
 
Microsoft license terms do not permit you to bring your own license (BYOL) based on your selection. Costs for Windows Server will be calculated as AWS License included running on shared tenancy. The on-premises Windows Server license purchased on or after October 1, 2019 can’t be utilized in AWS. Learn more 

This is due to the fact that Windows Server cannot be used with any cloud provided e.g. AWS post-October 1, 2019 – even in a dedicated environment. It also means that Windows Server licenses have never been eligible to be moved into a shared server environment – the only option for using your on-premises Windows Server licenses in the public cloud is via Microsoft’s Azure with Hybrid Rights.

Ontop of this, even if you did have licenses purchased Pre October 2019, you have to build the EC2 Instances from your media , you cannot use EC2 instances from AMI’s that have been built from AWS’s internal templates 

Amazon EC2 instances created from AWS AMIs can only leverage the AWS Default License Included purchasing option. However, instances that have been created from AMIs based on your own install media can leverage either the License Included or BYOL purchasing options. As a result, you may want to consider using imported AMIs for instances that are not currently leveraging BYOL, but may be candidates for BYOL in the future.

 
Costs for Windows Server will be calculated as AWS License included running on shared tenancy. The on-premises Windows Server license purchased on or after October 1, 2019 can’t be utilized in AWS. Learn more 
 
1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading...