Registering Amazon Linux Clients

This section contains information about registering traditional and Salt clients running Amazon Linux operating systems.

Traditional clients are not available on Amazon Linux 2. Amazon Linux 2 clients are only supported as Salt clients.

When created at AWS, Amazon Linux instances always have the same machine-id id at /etc/machine-id. Make sure you regenerate the machine-id after the instance is created. For more information, see administration:troubleshooting/tshoot-registerclones.adoc.

1. Add Software Channels

Before you register Amazon Linux clients to your Uyuni Server, you need to add the required software channels, and synchronize them.

The architectures currently supported are: x86_64 and aarch64. For full list of supported products and architectures, see client-configuration:supported-features.adoc.

In the following section, descriptions often default to the x86_64 architecture. Replace it with other architectures if appropriate.

The channels you need for this procedure are:

Table 1. Amazon Linux Channels - CLI
OS Version Core Channel Client Channel

Amazon Linux 2

amazonlinux2-core

amazonlinux2-uyuni-client

Make sure you also add and sync amazonlinux2-extra-docker channel if you plan to use Docker at your Amazon Linux instances.

Procedure: Adding Software Channels at the Command Prompt
  1. At the command prompt on the Uyuni Server, as root, use the spacewalk-common-channels command to add the appropriate channels:

    spacewalk-common-channels \
    <base_channel_label>
    <child_channel_label_1> \
    <child_channel_label_2> \
    ... <child_channel_label_n>
  2. If automatic synchronization is turned off, synchronize the channels:

    spacewalk-repo-sync -p <base_channel_label>
  3. Ensure the synchronization is complete before continuing.

The client tools channel provided by spacewalk-common-channels is sourced from Uyuni and not from SUSE.

2. Check Synchronization Status

Procedure: Checking Synchronization Progress from the Web UI
  1. In the Uyuni Web UI, navigate to Software  Manage  Channels, then click the channel associated to the repository.

  2. Navigate to the Repositories tab, then click Sync and check Sync Status.

Procedure: Checking Synchronization Progress from the Command Prompt
  1. At the command prompt on the Uyuni Server, as root, use the tail command to check the synchronization log file:

    tail -f /var/log/rhn/reposync/<channel-label>.log
  2. Each child channel generates its own log during the synchronization progress. You need to check all the base and child channel log files to be sure that the synchronization is complete.

3. Create an Activation Key

You need to create an activation key that is associated with your Amazon Linux channels.

For more information on activation keys, see client-configuration:activation-keys.adoc.

4. Manage GPG Keys

Clients use GPG keys to check the authenticity of software packages before they are installed. Only trusted software can be installed on clients.

Trusting a GPG key is important for security on clients. It is the task of the administrator to decide which keys are needed and can be trusted. Because a software channel cannot be used when the GPG key is not trusted, the decision of assigning a channel to a client depends on the decision of trusting the key.

For more information about GPG keys, see client-configuration:gpg-keys.adoc.

5. Register Clients

Amazon Linux clients are registered in the same way as all other clients. For more information, see client-configuration:registration-overview.adoc.