Downgrades in AWS Elemental Server - AWS Elemental Server

This is version 2.15 of the AWS Elemental Server documentation. This is the latest version. For prior versions, see the Previous Versions section of AWS Elemental Conductor File and AWS Elemental Server Documentation.

Downgrades in AWS Elemental Server

Downgrade rules

The following rules apply when you're downgrading AWS Elemental Server software.

  • Your system must be in a working state prior to the downgrade. If it's in a degraded state (such as not creating jobs or not responding through the web interface), the downgrade does not work.

  • You can downgrade to a version that's a maximum of two major versions below your current version, such as from 2.15.x to 2.14.x. The number of patches between the two versions is irrelevant. We do recommend, however, that you always use the latest patch release of the major version that you're downgrading to, for example, 2.14.6. To downgrade over a larger span, you must perform several downgrades, such as from 2.15.3 to 2.14.4, then 2.12.3.


Plan to downgrade during a maintenance window. All activity on the nodes stops during downgrade.

This section describes how to upgrade a standalone AWS Elemental Server node.

The procedure for upgrading any version of a standalone node is the same; only the version numbers in the file name change. In this section, we show how to upgrade to version 2.15 of the software.


Refer to the AWS Elemental Server 2.15 Release Notes to identify changes in requirements and behavior with the upgrade.

Quick reference

Here are the key upgrade commands. Use the actual filename of the .run file that you're using, rather than that provided in the example.

[elemental@hostname ~]$ sudo ./ --skip-all -xeula --start --downgrade --restore-db-backup <file/path>

where n.n.nnnnnn is the version and build number of the software that you're downgrading to, such as

For more detailed instructions, see the following topics.