Skip to content

Commit

Permalink
final edits
Browse files Browse the repository at this point in the history
  • Loading branch information
Amrita42 committed Oct 9, 2024
1 parent cb55427 commit 837ece3
Showing 1 changed file with 21 additions and 3 deletions.
24 changes: 21 additions & 3 deletions xml/rmt_public_cloud.xml
Original file line number Diff line number Diff line change
Expand Up @@ -111,7 +111,6 @@ To support &rmt; deployment, it is recommended to deploy a &rmt; instance from a
<listitem>
<para>
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
Expand All @@ -135,7 +134,7 @@ Cloud NAT services. Azure offers similar services.
<listitem>
<para>
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
When launching the &sles; instance to support &rmt; check if 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.
Expand All @@ -146,7 +145,26 @@ The security group must be configured to allow inbound access to the &rmt; serve
</sect1>
<sect1>
<title>More information</title>
<para></para>
<variablelist>
<varlistentry>
<term><link xlink:href="https://documentation.suse.com/sles/15-SP6/html/SLES-all/cha-rmt-mirroring.html#sec-rmt-mirroring-credentials"/>
</term>
<listitem>
<para>
Organization credentials to create a local mirror of the &sle; repositories.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><link xlink:href="https://documentation.suse.com/sles/15-SP6/html/SLES-all/cha-register-sle.html#sec-register-sle-installation"/>
</term>
<listitem>
<para>
Register and activate &sles; with the SUSE Customer Center.
</para>
</listitem>
</varlistentry>
</variablelist>
</sect1>

</chapter>

0 comments on commit 837ece3

Please sign in to comment.