0

I'm working on a project that requires the use of existing MSDN licenses to stand up Windows Server EC2 instances and, from what I understand, to remain license compliant these need to be provisioned on dedicated instances and/or hosts. I plan to use MSDN licenses for Windows Server, SQL and Dynamics.

As I'm unable to use Amazon provided base AMIs in conjunction with MSDN licenses, this suggests I need to create my own AMI. The AWS documentation suggests using AWS Server Migration Service to migrate on-prem servers (and their licenses) to AWS. However, I'd prefer to stand up these new instances from clean builds. Is there a recommended procedure for importing a base Windows Server AMI into AWS?

PhilH
  • 1

2 Answers2

0

MSDN licence is tied to your physical location, aka where you wrote it in the invoice. Those licences can be used for lab only too.

That enforcement will be done only in an audit in my own opinions, but its a risk you take

For the location restriction its wrote there, I just found the french text.

yagmoth555
  • 17,495
0

Had confirmation from Microsoft that MSDN licenses are support on dedicated Instances and dedicated Hosts, which ties up with the advice from AWS.

AWS advised that easiest method is to used dedicated instances and PAYG licensing for Windows Server using the AWS provided AMI. Any additional software apart from Windows Server, we would install under our MSDN license. If we were to opt for dedicated hosts, then we could use our MSDN license for Windows Server, but would need to build an image and import it into AWS, rather than use the provided AMIs.

PhilH
  • 1