adds images

xml/rmt_public_cloud.xml

@@ -36,7 +36,41 @@ PAYG (Pay As You Go) and BYOS (Bring Your Own Subscription). These images are up
 new instances from the latest version of the image to ensure the most recent security updates are in place.
 To support &rmt; deployment, it is recommended to deploy a &rmt; instance from a BYOS image.
 </para>
-
+<sect2 xml:id="sec-rmt-byos-image-where">
+  <title>Finding images in the cloud marketplace </title>
+  <para>Where to find the relevant image in each of the cloud provider is shown below: </para>
+  <figure>
+    <title>Google Cloud</title>
+    <mediaobject>
+      <imageobject role="fo">
+        <imagedata fileref="gcp-launch-sles-instance-cloud-rmt-marketplace.png" width="70%"/>
+      </imageobject>
+       </mediaobject>
+  </figure>
+  <figure>
+    <title>Amazon Web Services</title>
+    <mediaobject>
+      <imageobject role="fo">
+        <imagedata fileref="aws-launch-sles-instance-cloud-rmt-marketplace.png" width="70%"/>
+      </imageobject>
+       </mediaobject>
+  </figure>
+  <figure>
+    <title>Microsoft Azure</title>
+    <mediaobject>
+      <imageobject role="fo">
+        <imagedata fileref="azure-launch-sles-instance-cloud-rmt-marketplace.png" width="70%"/>
+      </imageobject>
+       </mediaobject>
+  </figure>
+  <para> It is recommended to start with an instance type with 2 to 3 VCPUS and a minimum of 8GB RAM to support the
+    &rmt; deployment. For example, in AWS this would be a EC2 T3 large instance.
+    </para>
+</sect2>
+<sect2 xml:id="sec-rmt-byos-image-registration">
+  <title></title>
+  <para></para>
+</sect2>
   </sect1>
 
 </chapter>