jms · September 21, 2023 00:17 · Mar 3, 2022 · Mar 3, 2022 · Nov 28, 2020 · Nov 28, 2020
diff --git a/Amazon_AWS_Linux_2_on_KVM_qemu.md b/Amazon_AWS_Linux_2_on_KVM_qemu.md
@@ -12,7 +12,7 @@ edit:
 this seems to work to get the latest files  ( include the final slash ) 
 https://cdn.amazonlinux.com/os-images/latest/ 
 
-A google dork for this: 
+A google dork for older versions: 
 site:cdn.amazonlinux.com inurl:kvm inurl:os-images  
  ( remove the kvm term to see images,etc for virtualbox, kvm-arm64  and other hypervisors) 
 

diff --git a/Amazon_AWS_Linux_2_on_KVM_qemu.md b/Amazon_AWS_Linux_2_on_KVM_qemu.md
@@ -8,6 +8,14 @@ https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-linux-2-virtual-machi
 Instructions sample configs and cloud-init files for on on-premises images:
 https://cdn.amazonlinux.com/os-images/2.0.20201111.0/
 
+edit: 
+this seems to work to get the latest files  ( include the final slash ) 
+https://cdn.amazonlinux.com/os-images/latest/ 
+
+A google dork for this: 
+site:cdn.amazonlinux.com inurl:kvm inurl:os-images  
+ ( remove the kvm term to see images,etc for virtualbox, kvm-arm64  and other hypervisors) 
+
 
 KVM / qemu / virt-manager  instructions - 
 

diff --git a/Amazon_AWS_Linux_2_on_KVM_qemu.md b/Amazon_AWS_Linux_2_on_KVM_qemu.md
@@ -47,7 +47,7 @@ If the sha256sum checks out and the signature file is "Good" then proceed:
 
 
 _Note_ - the 2 local text files act as a "data source" named NoCloud - 
-Instead of IP addresses and usernames are NOT from AWS-EC2 or from DigitalOcean etc etc they can be added to the text files by hand.
+Instead of getting IP addresses and usernames from AWS-EC2 or from DigitalOcean etc, they are be added to the text files by hand.
 _See this:_
 https://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html
 
@@ -76,4 +76,4 @@ https://cloudinit.readthedocs.io/en/latest/topics/datasources.html
 "After the VM has booted, log in using one of the user accounts that is defined in the user-data configuration file. " 
 Disconnect the seed.iso after you log in supposedly 
 
-
+^Note:^ SSH password-auth is disabled. Unless you add an ssh-key to user-data then you will need to log-in via virt-manager directly to the console. 
diff --git a/Amazon_AWS_Linux_2_on_KVM_qemu.md b/Amazon_AWS_Linux_2_on_KVM_qemu.md
@@ -67,11 +67,11 @@ https://cloudinit.readthedocs.io/en/latest/topics/datasources.html
 
 #### Step 5 
  Create a new vm in virt-manager 
-   Select Import existing disk image and use the qcow VM file  ( amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2 )
-    "For OS type and Version, choose Linux and Red Hat Enterprise Linux 7.0 "
-    Create a _new_ CDROM custom storage 
-     Browse local and choose the _generated_ seed.iso as the cdrom 
-    Begin Installation.
+  - Select Import existing disk image and use the qcow VM file  ( amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2 )
+   - "For OS type and Version, choose Linux and Red Hat Enterprise Linux 7.0 "
+  - Create a _new_ CDROM custom storage 
+  - Browse local and choose the _generated_ seed.iso as the cdrom 
+  - Begin Installation.
 
 "After the VM has booted, log in using one of the user accounts that is defined in the user-data configuration file. " 
 Disconnect the seed.iso after you log in supposedly 

diff --git a/Amazon_AWS_Linux_2_on_KVM_qemu.md b/Amazon_AWS_Linux_2_on_KVM_qemu.md
@@ -13,6 +13,7 @@ KVM / qemu / virt-manager  instructions -
 
 #### Step 1 
  Download 2 files - the seed.iso and then the actual OS disk image.
+ The Seed.iso file is just for examples and you must generate a new one below with genisoimage. 
  For KVM/qemu/virt-manager the OS file is currently named amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2
  Here: 
  https://cdn.amazonlinux.com/os-images/2.0.20201111.0/kvm/
@@ -21,13 +22,20 @@ KVM / qemu / virt-manager  instructions -
  - Download "SHA256sums" file containing sha256 sums and download shasums signature file ( .gpg )
  - check sha256sum with something like this:
 
-     grep  \`sha256sum amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2\` SHA256SUMS
+       grep  \`sha256sum amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2\` SHA256SUMS
 
- - import this AWS  key:  0x11CF1F95C87F5B1A
+ - add/import the AWS  key:  0x11CF1F95C87F5B1A using for instance 
+
+       $ wget https://cdn.amazonlinux.com/_assets/11CF1F95C87F5B1A.asc 
+       $ gpg   --verbose --interactive  --import 11CF1F95C87F5B1A.asc
+
  - validate signature on the shasum signature file ( SHA256SUMS.gpg ) with gpg
+
+       gpg --verify SHA256SUMS.gpg SHA256SUMS
 
-If the sha256sum checks out and the signature file is valid then proceed:
-
+If the sha256sum checks out and the signature file is "Good" then proceed:
+ ( even if the key is 'not certified with a trusted.. ') 
+
 #### Step 3  ( NoCloud data source creation )
  Create two simple local text configuration files named 'meta-data' and 'user-data'
  meta-data is network settings and user-data sets up the ec2-user username account.
@@ -38,7 +46,8 @@ If the sha256sum checks out and the signature file is valid then proceed:
  Change the network settings to fit your local network IP addresses or DHCP.
 
 
-_Note_ - the 2 local text files act as a "data source" named NoCloud - that is the IP addresses and usernames are NOT taken from AWS-EC2 or from DigitalOcean etc etc. 
+_Note_ - the 2 local text files act as a "data source" named NoCloud - 
+Instead of IP addresses and usernames are NOT from AWS-EC2 or from DigitalOcean etc etc they can be added to the text files by hand.
 _See this:_
 https://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html
 
@@ -51,7 +60,7 @@ https://cloudinit.readthedocs.io/en/latest/topics/datasources.html
 
 
 #### Step 4 
- Generate a boot ISO using  seed.iso along with data-source files named 'meta-data' and 'user-data'  that you created:
+ Generate your own ISO image named seed.iso from the data-source files named 'meta-data' and 'user-data' that you created:
  That is to say - run the genisoimage command below:
 
      $ genisoimage -output seed.iso -volid cidata -joliet -rock user-data meta-data

diff --git a/Amazon_AWS_Linux_2_on_KVM_qemu.md b/Amazon_AWS_Linux_2_on_KVM_qemu.md
@@ -19,9 +19,9 @@ KVM / qemu / virt-manager  instructions -
 
 #### Step 2 ( or step 1.5 ) 
  - Download "SHA256sums" file containing sha256 sums and download shasums signature file ( .gpg )
- - check sha256sum 
+ - check sha256sum with something like this:
 
-    grep  \`sha256sum amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2\` SHA256SUMS
+     grep  \`sha256sum amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2\` SHA256SUMS
 
  - import this AWS  key:  0x11CF1F95C87F5B1A
  - validate signature on the shasum signature file ( SHA256SUMS.gpg ) with gpg

diff --git a/Amazon_AWS_Linux_2_on_KVM_qemu.md b/Amazon_AWS_Linux_2_on_KVM_qemu.md
@@ -20,7 +20,9 @@ KVM / qemu / virt-manager  instructions -
 #### Step 2 ( or step 1.5 ) 
  - Download "SHA256sums" file containing sha256 sums and download shasums signature file ( .gpg )
  - check sha256sum 
+
     grep  \`sha256sum amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2\` SHA256SUMS
+
  - import this AWS  key:  0x11CF1F95C87F5B1A
  - validate signature on the shasum signature file ( SHA256SUMS.gpg ) with gpg
 

diff --git a/Amazon_AWS_Linux_2_on_KVM_qemu.md b/Amazon_AWS_Linux_2_on_KVM_qemu.md
@@ -19,7 +19,8 @@ KVM / qemu / virt-manager  instructions -
 
 #### Step 2 ( or step 1.5 ) 
  - Download "SHA256sums" file containing sha256 sums and download shasums signature file ( .gpg )
- - check sha256sum `grep \`sha256sum amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2\` SHA256SUMS`
+ - check sha256sum 
+    grep  \`sha256sum amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2\` SHA256SUMS
  - import this AWS  key:  0x11CF1F95C87F5B1A
  - validate signature on the shasum signature file ( SHA256SUMS.gpg ) with gpg
 

diff --git a/Amazon_AWS_Linux_2_on_KVM_qemu.md b/Amazon_AWS_Linux_2_on_KVM_qemu.md
@@ -19,7 +19,7 @@ KVM / qemu / virt-manager  instructions -
 
 #### Step 2 ( or step 1.5 ) 
  - Download "SHA256sums" file containing sha256 sums and download shasums signature file ( .gpg )
- - check sha256sum `grep \\`sha256sum amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2\` SHA256SUMS `
+ - check sha256sum `grep \`sha256sum amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2\` SHA256SUMS`
  - import this AWS  key:  0x11CF1F95C87F5B1A
  - validate signature on the shasum signature file ( SHA256SUMS.gpg ) with gpg
 

diff --git a/Amazon_AWS_Linux_2_on_KVM_qemu.md b/Amazon_AWS_Linux_2_on_KVM_qemu.md
@@ -19,7 +19,7 @@ KVM / qemu / virt-manager  instructions -
 
 #### Step 2 ( or step 1.5 ) 
  - Download "SHA256sums" file containing sha256 sums and download shasums signature file ( .gpg )
- - check sha256sum `grep \` sha256sum amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2\` SHA256SUMS `
+ - check sha256sum `grep \\`sha256sum amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2\` SHA256SUMS `
  - import this AWS  key:  0x11CF1F95C87F5B1A
  - validate signature on the shasum signature file ( SHA256SUMS.gpg ) with gpg
 

diff --git a/Amazon_AWS_Linux_2_on_KVM_qemu.md b/Amazon_AWS_Linux_2_on_KVM_qemu.md
@@ -19,7 +19,7 @@ KVM / qemu / virt-manager  instructions -
 
 #### Step 2 ( or step 1.5 ) 
  - Download "SHA256sums" file containing sha256 sums and download shasums signature file ( .gpg )
- - check sha256sum `grep \`sha256sum amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2\` SHA256SUMS `
+ - check sha256sum `grep \` sha256sum amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2\` SHA256SUMS `
  - import this AWS  key:  0x11CF1F95C87F5B1A
  - validate signature on the shasum signature file ( SHA256SUMS.gpg ) with gpg
 

diff --git a/Amazon_AWS_Linux_2_on_KVM_qemu.md b/Amazon_AWS_Linux_2_on_KVM_qemu.md
@@ -19,7 +19,7 @@ KVM / qemu / virt-manager  instructions -
 
 #### Step 2 ( or step 1.5 ) 
  - Download "SHA256sums" file containing sha256 sums and download shasums signature file ( .gpg )
- - check sha256sum `grep `sha256sum amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2` SHA256SUMS `
+ - check sha256sum `grep \`sha256sum amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2\` SHA256SUMS `
  - import this AWS  key:  0x11CF1F95C87F5B1A
  - validate signature on the shasum signature file ( SHA256SUMS.gpg ) with gpg
 

diff --git a/Amazon_AWS_Linux_2_on_KVM_qemu.md b/Amazon_AWS_Linux_2_on_KVM_qemu.md
@@ -19,7 +19,7 @@ KVM / qemu / virt-manager  instructions -
 
 #### Step 2 ( or step 1.5 ) 
  - Download "SHA256sums" file containing sha256 sums and download shasums signature file ( .gpg )
- - check sha256sum `grep \`sha256sum amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2\` SHA256SUMS `
+ - check sha256sum `grep `sha256sum amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2` SHA256SUMS `
  - import this AWS  key:  0x11CF1F95C87F5B1A
  - validate signature on the shasum signature file ( SHA256SUMS.gpg ) with gpg
 

diff --git a/Amazon_AWS_Linux_2_on_KVM_qemu.md b/Amazon_AWS_Linux_2_on_KVM_qemu.md
@@ -18,10 +18,10 @@ KVM / qemu / virt-manager  instructions -
  https://cdn.amazonlinux.com/os-images/2.0.20201111.0/kvm/
 
 #### Step 2 ( or step 1.5 ) 
- Download "SHA256sums" file containing sha256 sums   and download shasums signature file ( .gpg ) 
- check sha256sum
- import this AWS  key:  0x11CF1F95C87F5B1A
- validate signature on the shasum signature file ( SHA256SUMS.gpg ) with gpg
+ - Download "SHA256sums" file containing sha256 sums and download shasums signature file ( .gpg )
+ - check sha256sum `grep \`sha256sum amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2\` SHA256SUMS `
+ - import this AWS  key:  0x11CF1F95C87F5B1A
+ - validate signature on the shasum signature file ( SHA256SUMS.gpg ) with gpg
 
 If the sha256sum checks out and the signature file is valid then proceed:
 

diff --git a/Amazon_AWS_Linux_2_on_KVM_qemu.md b/Amazon_AWS_Linux_2_on_KVM_qemu.md
@@ -28,28 +28,30 @@ If the sha256sum checks out and the signature file is valid then proceed:
 #### Step 3  ( NoCloud data source creation )
  Create two simple local text configuration files named 'meta-data' and 'user-data'
  meta-data is network settings and user-data sets up the ec2-user username account.
+
  See this link for default settings:
-
-    https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-linux-2-virtual-machine.html#amazon-linux-2-virtual-machine-prepare 
+  https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-linux-2-virtual-machine.html#amazon-linux-2-virtual-machine-prepare 
 
-    Change the network settings to fit your local network IP addresses or DHCP.
+ Change the network settings to fit your local network IP addresses or DHCP.
 
 
 _Note_ - the 2 local text files act as a "data source" named NoCloud - that is the IP addresses and usernames are NOT taken from AWS-EC2 or from DigitalOcean etc etc. 
 _See this:_
 https://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html
 
-_and the far more intimidating version of that info here:_
+_and the more intimidating version of that info here:_
+https://cdn.amazonlinux.com/os-images/2.0.20201111.0/README.cloud-init 
 
-https://cdn.amazonlinux.com/os-images/2.0.20201111.0/README.cloud-init and finally - the whole list of potential data sources here, with some blah-blah about telling the guest OS about the host virt. platform
 ##### Cloud Init docs
+and finally - the whole list of potential cloud init data sources here - with some blah-blah about telling the guest OS about the host virt. platform:
 https://cloudinit.readthedocs.io/en/latest/topics/datasources.html
 
 
 #### Step 4 
  Generate a boot ISO using  seed.iso along with data-source files named 'meta-data' and 'user-data'  that you created:
- That is to say - run the genisoimage command below: 
-    $ genisoimage -output seed.iso -volid cidata -joliet -rock user-data meta-data
+ That is to say - run the genisoimage command below:
+
+     $ genisoimage -output seed.iso -volid cidata -joliet -rock user-data meta-data
 
 #### Step 5 
  Create a new vm in virt-manager 

diff --git a/Amazon_AWS_Linux_2_on_KVM_qemu.md b/Amazon_AWS_Linux_2_on_KVM_qemu.md
@@ -12,23 +12,23 @@ https://cdn.amazonlinux.com/os-images/2.0.20201111.0/
 KVM / qemu / virt-manager  instructions - 
 
 #### Step 1 
-    Download 2 files - the seed.iso and then the actual OS disk image.
-    For KVM/qemu/virt-manager the OS file is currently named amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2
-    Here: 
-    https://cdn.amazonlinux.com/os-images/2.0.20201111.0/kvm/
+ Download 2 files - the seed.iso and then the actual OS disk image.
+ For KVM/qemu/virt-manager the OS file is currently named amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2
+ Here: 
+ https://cdn.amazonlinux.com/os-images/2.0.20201111.0/kvm/
 
 #### Step 2 ( or step 1.5 ) 
-    Download "SHA256sums" file containing sha256 sums   and download shasums signature file ( .gpg ) 
-    check sha256sum
-    import this AWS  key:  0x11CF1F95C87F5B1A
-    validate signature on the shasum signature file ( SHA256SUMS.gpg ) with gpg
+ Download "SHA256sums" file containing sha256 sums   and download shasums signature file ( .gpg ) 
+ check sha256sum
+ import this AWS  key:  0x11CF1F95C87F5B1A
+ validate signature on the shasum signature file ( SHA256SUMS.gpg ) with gpg
 
 If the sha256sum checks out and the signature file is valid then proceed:
 
 #### Step 3  ( NoCloud data source creation )
-    Create two simple local text configuration files named 'meta-data' and 'user-data'
-    meta-data is network settings and user-data sets up the ec2-user username account.
-    See this link for default settings:
+ Create two simple local text configuration files named 'meta-data' and 'user-data'
+ meta-data is network settings and user-data sets up the ec2-user username account.
+ See this link for default settings:
 
     https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-linux-2-virtual-machine.html#amazon-linux-2-virtual-machine-prepare 
 
@@ -47,16 +47,16 @@ https://cloudinit.readthedocs.io/en/latest/topics/datasources.html
 
 
 #### Step 4 
-    Generate a boot ISO using  seed.iso along with data-source files named 'meta-data' and 'user-data'  that you created:
-    That is to say - run the genisoimage command below: 
+ Generate a boot ISO using  seed.iso along with data-source files named 'meta-data' and 'user-data'  that you created:
+ That is to say - run the genisoimage command below: 
     $ genisoimage -output seed.iso -volid cidata -joliet -rock user-data meta-data
 
 #### Step 5 
-    Create a new vm in virt-manager 
-        Select Import existing disk image and use the qcow VM file  ( amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2 )
-        " For OS type and Version, choose Linux and Red Hat Enterprise Linux 7.0 "
-        Create a _new_ CDROM custom storage 
-            Browse local and choose the _generated_ seed.iso 
+ Create a new vm in virt-manager 
+   Select Import existing disk image and use the qcow VM file  ( amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2 )
+    "For OS type and Version, choose Linux and Red Hat Enterprise Linux 7.0 "
+    Create a _new_ CDROM custom storage 
+     Browse local and choose the _generated_ seed.iso as the cdrom 
     Begin Installation.
 
 "After the VM has booted, log in using one of the user accounts that is defined in the user-data configuration file. " 

diff --git a/Amazon_AWS_Linux_2_on_KVM_qemu.md b/Amazon_AWS_Linux_2_on_KVM_qemu.md
@@ -26,14 +26,16 @@ KVM / qemu / virt-manager  instructions -
 If the sha256sum checks out and the signature file is valid then proceed:
 
 #### Step 3  ( NoCloud data source creation )
-    Create two simple local text configuration files named 'meta-data' and 'user-data' .
+    Create two simple local text configuration files named 'meta-data' and 'user-data'
     meta-data is network settings and user-data sets up the ec2-user username account.
-    See this link for default settings; 
+    See this link for default settings:
+
     https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-linux-2-virtual-machine.html#amazon-linux-2-virtual-machine-prepare 
 
     Change the network settings to fit your local network IP addresses or DHCP.
 
-Note - the 2 local text files act as a "data source" named NoCloud - that is the IP addresses and usernames are NOT taken from AWS-EC2 or from DigitalOcean etc etc. 
+
+_Note_ - the 2 local text files act as a "data source" named NoCloud - that is the IP addresses and usernames are NOT taken from AWS-EC2 or from DigitalOcean etc etc. 
 _See this:_
 https://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html
 

diff --git a/Amazon_AWS_Linux_2_on_KVM_qemu.md b/Amazon_AWS_Linux_2_on_KVM_qemu.md
@@ -1,5 +1,5 @@
-# install and run AWS linux 2 on home computer as a virtual machine
-### These instructions are tailored for KVM and virt-manager specifically .
+## install and run AWS linux 2 on home computer as a virtual machine
+#### These instructions are tailored for KVM and virt-manager specifically .
 
 Detailed Instructions are here :
 https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-linux-2-virtual-machine.html
@@ -11,20 +11,21 @@ https://cdn.amazonlinux.com/os-images/2.0.20201111.0/
 
 KVM / qemu / virt-manager  instructions - 
 
-### Step 1 
-    Download 2 files - the seed.iso and then the actual OS disk image.     For KVM/qemu/virt-manager the OS file is currently named amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2
+#### Step 1 
+    Download 2 files - the seed.iso and then the actual OS disk image.
+    For KVM/qemu/virt-manager the OS file is currently named amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2
     Here: 
     https://cdn.amazonlinux.com/os-images/2.0.20201111.0/kvm/
 
-### Step 2 ( or step 1.5 ) 
+#### Step 2 ( or step 1.5 ) 
     Download "SHA256sums" file containing sha256 sums   and download shasums signature file ( .gpg ) 
     check sha256sum
     import this AWS  key:  0x11CF1F95C87F5B1A
     validate signature on the shasum signature file ( SHA256SUMS.gpg ) with gpg
 
 If the sha256sum checks out and the signature file is valid then proceed:
 
-### Step 3  ( NoCloud data source creation )
+#### Step 3  ( NoCloud data source creation )
     Create two simple local text configuration files named 'meta-data' and 'user-data' .
     meta-data is network settings and user-data sets up the ec2-user username account.
     See this link for default settings; 
@@ -43,12 +44,12 @@ https://cdn.amazonlinux.com/os-images/2.0.20201111.0/README.cloud-init and final
 https://cloudinit.readthedocs.io/en/latest/topics/datasources.html
 
 
-### Step 4 
+#### Step 4 
     Generate a boot ISO using  seed.iso along with data-source files named 'meta-data' and 'user-data'  that you created:
     That is to say - run the genisoimage command below: 
     $ genisoimage -output seed.iso -volid cidata -joliet -rock user-data meta-data
 
-### Step 5 
+#### Step 5 
     Create a new vm in virt-manager 
         Select Import existing disk image and use the qcow VM file  ( amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2 )
         " For OS type and Version, choose Linux and Red Hat Enterprise Linux 7.0 "

diff --git a/Amazon_AWS_Linux_2_on_KVM_qemu.md b/Amazon_AWS_Linux_2_on_KVM_qemu.md
@@ -0,0 +1,62 @@
+# install and run AWS linux 2 on home computer as a virtual machine
+### These instructions are tailored for KVM and virt-manager specifically .
+
+Detailed Instructions are here :
+https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-linux-2-virtual-machine.html
+( for VMWare and VirtualBox  and Hyoer-V in addiation to KVM )
+
+Instructions sample configs and cloud-init files for on on-premises images:
+https://cdn.amazonlinux.com/os-images/2.0.20201111.0/
+
+
+KVM / qemu / virt-manager  instructions - 
+
+### Step 1 
+    Download 2 files - the seed.iso and then the actual OS disk image.     For KVM/qemu/virt-manager the OS file is currently named amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2
+    Here: 
+    https://cdn.amazonlinux.com/os-images/2.0.20201111.0/kvm/
+
+### Step 2 ( or step 1.5 ) 
+    Download "SHA256sums" file containing sha256 sums   and download shasums signature file ( .gpg ) 
+    check sha256sum
+    import this AWS  key:  0x11CF1F95C87F5B1A
+    validate signature on the shasum signature file ( SHA256SUMS.gpg ) with gpg
+
+If the sha256sum checks out and the signature file is valid then proceed:
+
+### Step 3  ( NoCloud data source creation )
+    Create two simple local text configuration files named 'meta-data' and 'user-data' .
+    meta-data is network settings and user-data sets up the ec2-user username account.
+    See this link for default settings; 
+    https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-linux-2-virtual-machine.html#amazon-linux-2-virtual-machine-prepare 
+
+    Change the network settings to fit your local network IP addresses or DHCP.
+
+Note - the 2 local text files act as a "data source" named NoCloud - that is the IP addresses and usernames are NOT taken from AWS-EC2 or from DigitalOcean etc etc. 
+_See this:_
+https://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html
+
+_and the far more intimidating version of that info here:_
+
+https://cdn.amazonlinux.com/os-images/2.0.20201111.0/README.cloud-init and finally - the whole list of potential data sources here, with some blah-blah about telling the guest OS about the host virt. platform
+##### Cloud Init docs
+https://cloudinit.readthedocs.io/en/latest/topics/datasources.html
+
+
+### Step 4 
+    Generate a boot ISO using  seed.iso along with data-source files named 'meta-data' and 'user-data'  that you created:
+    That is to say - run the genisoimage command below: 
+    $ genisoimage -output seed.iso -volid cidata -joliet -rock user-data meta-data
+
+### Step 5 
+    Create a new vm in virt-manager 
+        Select Import existing disk image and use the qcow VM file  ( amzn2-kvm-2.0.20201111.0-x86_64.xfs.gpt.qcow2 )
+        " For OS type and Version, choose Linux and Red Hat Enterprise Linux 7.0 "
+        Create a _new_ CDROM custom storage 
+            Browse local and choose the _generated_ seed.iso 
+    Begin Installation.
+
+"After the VM has booted, log in using one of the user accounts that is defined in the user-data configuration file. " 
+Disconnect the seed.iso after you log in supposedly 
+
+