Adding support for EC2Launch used by 2016 and 2019 images

Author: RobBiddle

Private/UserDataEC2Launch.xml

@@ -0,0 +1,11 @@
+<powershell> # XML Tag for EC2ConfigService
+
+# Run Sysprep via EC2Launch scripts
+# https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ec2launch.html#ec2launch-sysprep
+
+Set-Location "$env:ProgramData\Amazon\EC2-Windows\Launch\Scripts"
+$command = '.\InitializeInstance.ps1 -Schedule'
+Invoke-Expression -Command $command
+$command = '.\SysprepInstance.ps1'
+Invoke-Expression -Command $command
+</powershell>

Public/New-PackerBaseAMI.ps1

@@ -146,6 +146,11 @@ function New-PackerBaseAMI {
         }
 
         # Build the Packer Template
+        if ($BaseOS -match '2016|2019') {
+            $UserDataFile = "$(Split-Path (Get-Module PackerBaseAMI).Path -Parent)\Private\UserDataEC2Launch.xml"
+        } else {
+            $UserDataFile = "$(Split-Path (Get-Module PackerBaseAMI).Path -Parent)\Private\UserData.xml"
+        }
         $builders = [PSCustomObject]@{
             type                  = "amazon-ebs"
             communicator          = "none"
@@ -157,7 +162,7 @@ function New-PackerBaseAMI {
             instance_type         = "t2.medium"
             source_ami            = $AmiToPack.ImageId
             ami_name              = $NewAMIName
-            user_data_file        = "$(Split-Path (Get-Module PackerBaseAMI).Path -Parent)\Private\UserData.xml"
+            user_data_file        = $UserDataFile
         }
         $PackerTemplate = [PSCustomObject]@{
             builders = @($builders)