CNV-70111: Add details about license-compliant windows VMs

_topic_maps/_topic_map.yml

@@ -4788,6 +4788,8 @@ Topics:
     File: virt-creating-vms-from-templates
   - Name: Configuring IBM Secure Execution virtual machines on IBM Z and IBM LinuxONE
     File: virt-configuring-ibm-secure-execution-vms-ibm-z
+  - Name: Creating AWS EC2 Windows License Included (LI) compliant VMs
+    File: virt-creating-vms-aws-li-windows
 - Name: Advanced VM creation
   Dir: creating_vms_advanced
   Topics:

_topic_maps/_topic_map_rosa.yml

@@ -1745,6 +1745,8 @@ Topics:
     File: virt-creating-vms-from-instance-types
   - Name: Creating VMs from templates
     File: virt-creating-vms-from-templates
+  - Name: Creating AWS EC2 Windows License Included (LI) compliant VMs
+    File: virt-creating-vms-aws-li-windows
 - Name: Advanced VM creation
   Dir: creating_vms_advanced
   Topics:

_topic_maps/_topic_map_rosa_hcp.yml

@@ -1591,6 +1591,8 @@ Topics:
     File: virt-creating-vms-from-instance-types
   - Name: Creating VMs from templates
     File: virt-creating-vms-from-templates
+  - Name: Creating AWS EC2 Windows License Included (LI) compliant VMs
+    File: virt-creating-vms-aws-li-windows
 - Name: Advanced VM creation
   Dir: creating_vms_advanced
   Topics:

modules/virt-create-aws-li-windows-vm-web-console.adoc

@@ -0,0 +1,29 @@
+// Module included in the following assemblies:
+//
+// * virt/creating_vm/virt-creating-vms-aws-li-windows.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="virt-create-aws-li-windows-vm-web-console_{context}"]
+= Creating a license-compliant AWS EC2 Windows VM by using the web console
+
+[role="_abstract"]
+You can create license-compliant Windows virtual machines (VMs) by enabling the `dedicatedCpuPlacement` attribute. This attribute is enabled by default on instance types from the `d1` family. In the {product-title} web console, you can create a compliant VM by selecting from a list of available bootable volumes.
+
+.Procedure
+
+. In the {product-title} web console, go to *Virtualization* -> *Catalog*. The *InstanceTypes* tab opens by default.
+
+. Click *Add volume* to create a Windows boot source. You can create a Windows boot source by uploading a new volume or by using an existing persistent volume claim (PVC), a volume snapshot, or a `containerDisk` volume.
+
+. In the *Volume metadata* section, select a preference with a name that begins with `windows` and is followed by the Windows version of your choice. For example, `windows.11.virtio`. Click *Save*.
+
+. Select a bootable volume from the list. If the list is truncated, click *Show all* to display the entire list. The bootable volume table contains the previously uploaded boot source.
+
+. In the *User provided* tab, select an instance type with a name that begins with `d1`. For example, `d1.2xmedium` for a Windows 11 VM.
+
+. Optional: You can mount a Windows driver disk by completing the following steps:
+.. Click *Customize VirtualMachine*.
+.. On the *VirtualMachine details* page, click *Storage*.
+.. Select the *Mount Windows drivers* disk checkbox.
+
+. Click *Create VirtualMachine*.

virt/creating_vm/virt-creating-vms-aws-li-windows.adoc

@@ -0,0 +1,16 @@
+:_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
+[id="virt-creating-vms-aws-li-windows"]
+= Creating a license-compliant AWS EC2 Windows VM
+:context: virt-creating-vms-aws-li-windows
+
+toc::[]
+
+[role="_abstract"]
+If you are running Windows virtual machines (VMs) on {product-title} hosts, such as AMD64 bare metal EC2 instances with {aws-first} Windows License Included (LI) enabled, you must ensure that any VMs you create are compliant with licensing requirements.
+
+When you configure your Windows VMs correctly, they activate automatically with the {aws-short} Key Management Service (KMS), and run using optimized drivers for the underlying bare-metal hardware. Proper configuration also ensures that billing is correct.
+
+If you do not configure your Windows VMs so that they are license-compliant, they might fail to activate, suffer degraded system performance due to sub-optimal CPU pinning, and risk failing a licensing audit.
+
+include::modules/virt-create-aws-li-windows-vm-web-console.adoc[leveloffset=+1]