Note: Please go to to access the current RightScale documentation set. Also, feel free to Chat with us!
Home > Guides > RightLink 6 > RightLink Legacy Versions > RightLink 5.8 and Lower > Create RightScale-Enabled Images with RightLink 5.8 and lower > RightLink 5.8 Installer for SUSE Linux Enterprise Server (SLES)

RightLink 5.8 Installer for SUSE Linux Enterprise Server (SLES)


Boot a non-RightScale enabled SLES instance, perform some manual configuration, install the RightLink package and re-bundle the instance into a new, RightScale-enabled AMI. Optionally, test compatibility before bundling and create an MCI (MultiCloud Image) for your new image.


  1. Do not forget to tag the MCI! Any image with RightLink must be tagged appropriately to successfully operate with the RightScale management platform; see the last step in this article for more information.
  2. These instructions apply only to RightLink v5.5 and above. RightLink packages prior to v5.5 did not install cleanly and required extensive changes. Using the latest available RightLink package is always recommended.


NOTE: Although the steps provided below for bundling instances may still be valid in some scenarios, we encourage you to explore using the Instance Provisioner for bundling instances. See Create New Instance with the Instance Provisioner for additional information.


SLES Multi-cloud Images for RightScale are provided by SUSE and can be found in our Marketplace. You can also you can easily install RightLink on a SLES instance and bundle the instance into a new RightScale-enabled AMI.


Launch a SLES EC2 Instance

In the RightScale Dashboard, navigate to the appropriate cloud in the menu (e.g., Clouds > AWS Region > Instances > New) and launch a new instance with the SLES (or OpenSUSE) AMI you would like to RightLink-enable.

SSH into the Instance

Once the instance or server becomes operational, click on its 'SSH Console' button in the RightScale Dashboard. If the 'SSH Console' button doesn't work, then you may need to copy the instance's private launch key and manually SSH into the instance with a client such as Putty or OpenSSH.

Note: All terminal commands throughout this tutorial from this point forward should be done with a 'root' user.

Set the Cloud Type

Run the following command to set the cloud type to Amazon EC2:

mkdir -p /etc/rightscale.d && echo -n ec2 > /etc/rightscale.d/cloud

This file is used by the RightLink agent to recognize which cloud type the instance is running in.

Install Dependencies

Install the RightScale package dependencies manually:

echo 'Installing RightScale RightLink dependencies.'
rs_deps='git curl bash lsb-release bind-utils'
zypper -n install $rs_deps || yum -y install $rs_deps
Install RightLink

Browse RightScale's mirror ( for available RightLink packages.
Although we recommend using the latest available RightLink package, it may not be available for your particular distribution.
As specific packages are not built for SLES (or OpenSUSE), currently using the RHEL packages is recommended.

The most recently published packages can be found in the "latest" RightLink packages directory.  If you do not find a suitable package in one of the "latest" directories, you can also browse for a different version from one of the archived directories. You must choose the distribution package that's most appropriate for your purposes, based upon your instance's operating system and CPU architecture (32-bit or 64-bit).

Once your instance becomes operational, SSH into the instance and install the appropriate RPM package. You can copy and paste the link from your browser if required.

Specific Package

Note: The 5.8.8 version of RightLink for RHEL 5.8 is the only RPM compatible with SLES 11 currently, so slightly newer versions may be unavailable until a SLES specific RPM is available.

Install a specific version from the mirror (only recommended if a specific reason to not use the latest exists).The following installs RightLink 5.8.8 on a 64-bit instance:

rpm -iv

Bundle the Instance

To create a new AMI from the running instance, click the Bundle button in the Dashboard.
Once the bundle worker has completed the task, view the audit entry and take note of the AWS ID that was used to register the new AMI. If bundling an EBS backed AMI, no audit entry for the bundle operation may be present on the Instance > Audit Entries tab, however your browser should be redirected to the new AMI once bundling is complete. You can also locate your new AMI manually under the Clouds > AWS Region > EC2 Images menu if needed.

Create a MultiCloud Image

In order to use the new RightScale-enabled AMI with ServerTemplates, create a MultiCloud Image (MCI) that references the new image.  See Create a New MultiCloud Image. The MCI can then be added to any local (HEAD) ServerTemplates in your account. If you need to make that image available in a different AWS region, follow the Replicate an Image to different AWS regions

Add the AMI to the MCI

Next, add the AMI to the MCI.

Tag the MCI (mandatory)

Once the AMI has been added to your newly created MCI, manually add the following tag to the MCI:



Congratulations!  You now have a RightLink-enabled MCI.

Test the Bundled Image (optional)

If this tutorial was used to bundle a private cloud image. To perform a compatibility test on the new private RightLink-enabled image that you just created, see Testing your Private RightLink-enabled Image.

You must to post a comment.
Last modified
10:02, 19 Feb 2015



This page has no classifications.



© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.