diff --git a/xml/rmt_public_cloud.xml b/xml/rmt_public_cloud.xml
index 4f66875a80..61a6559b7a 100644
--- a/xml/rmt_public_cloud.xml
+++ b/xml/rmt_public_cloud.xml
@@ -15,7 +15,7 @@
-You can deploy a &sls; instance to support &rmt; in Amazon Web Services, Google Cloud, and Microsoft Azure.
+You can deploy a &sls; instance to support &rmt; in Amazon Web Services(AWS), Google Cloud Platform(GCP), and Microsoft Azure.
The Repository Mirroring Tool (RMT) is included in &sls; starting with version 15.
The following example shows a generic cloud architecture for the &rmt; deployment. Your deployment may look different based
@@ -89,6 +89,64 @@ To support &rmt; deployment, it is recommended to deploy a &rmt; instance from a
&prompt.sudo; SUSEConnect -e EMAIL_ADDRESS -r REGISTRATION_CODE
The registration code is available, once you log in to SCC.
-
+
+Considerations when using &rmt;
+ You must consider the following requirements when you use &rmt;
+
+
+ Disk space
+
+
+ The &rmt; server requires sufficient disk space to mirror the &sliberty; LTSS 7 repositories.
+ Downloaded packages are available in /var/lib/rmt/public/repo/. Disk space is dependent
+ on the number of repositories you mirror. We recommend a minimum of 1.5 times the total size of all enabled repositories.
+ It is a best practice to provision an additional disk volume to support this requirement.
+ You can either mount the volume to /var/lib/rmt/public/repo/ on instance creation or immediately after the launch.
+ For Azure, it is an additional disk volume. An Amazon EBS volume for AWS and a persistent disk volume for GCP.
+
+
+
+
+ IP or DNS resolution
+
+
+ A static IP address or a DNS name is required in order for clients to connect to the &rmt; server.
+In Azure,AWS and GCP, a
+ In Azure, AWS and GCP, a Cloud Service Provider(CSP) provided DNS is assigned when the instance is launched.
+ This IP or DNS may change if the instance is recreated. For Azure, consider using a static IP address to provide a consistent
+ connection point for your clients. In AWS, this would be an elastic IP or Route53. In GCP, this would be a cloud DNS
+ record that uses a static IP address.
+
+
+
+
+ Connectivity for the &rmt; server
+
+
+ The &rmt; server can connect to SCC on ports 80 and 443. There are many ways to provide connectivity.
+For example, in AWS, connectivity to SCC can be provided via an AWS Internet Gateway, an AWS NAT Gateway, or via a local data center (VPN/DX Connection) but this is dependent
+on whether the &rmt; instance is in a public or private subnet. GCP provides direct access to the internet via the VPC routes or
+Cloud NAT services. Azure offers similar services.
+
+
+
+
+ Connectivity for clients
+
+
+ Clients can connect to &rmt; on ports 80 and 443.
+ When launching the &sles; instance to support &rmt; check in AWS the network security group is configured to allow
+ inbound access to the &rmt; server from your clients (HTTP/HTTPS). For GCP, the firewall rules must be configured to allow
+ inbound access to the &rmt; server from your clients.
+When a &sles; instance is launched to support &rmt;, it is possible to use an existing AWS security group or a new one.
+The security group must be configured to allow inbound access to the &rmt; server from your clients.
+
+
+
+
+
+ More information
+
+