About this guide - AWS Elemental Live

About this guide

This guide is intended for engineers who upgrade the software running on the nodes of AWS Elemental Live. In addition, the worker nodes in the cluster can be set up in a redundant or non-redundant configuration. In a redundant configuration, when a worker node fails, its events automatically fail over to another node.

The full suite of upgrade information for AWS Elemental Live is described in the table:

Possible problem Possible reason

Stand-alone deployments

AWS Elemental Live nodes are not in a cluster controlled by AWS Elemental Conductor Live 3.

This guide.

Single Conductor cluster, no worker redundancy

AWS Elemental Live nodes without backup worker nodes in a cluster controlled by one AWS Elemental Conductor Live 3 node.

AWS Elemental Conductor Live 3 Upgrade Guide

Single Conductor cluster with worker redundancy

AWS Elemental Live nodes with one or more backup worker nodes in a cluster controlled by one AWS Elemental Conductor Live 3 node.

AWS Elemental Conductor Live 3 Upgrade Guide

High-availability cluster, no worker redundancy

AWS Elemental Live nodes without backup worker nodes in a cluster controlled by two AWS Elemental Conductor Live 3 nodes.

AWS Elemental Conductor Live 3 Upgrade Guide

High-availability cluster, with worker redundancy

AWS Elemental Live nodes with backup worker nodes, in a cluster controlled by two AWS Elemental Conductor Live 3 nodes (a primary and a backup).

AWS Elemental Conductor Live 3 Upgrade Guide

Prerequisite knowledge

We assume that you know how to:

  • Connect to the AWS Elemental Live web interface using your web browser.

  • Log in to a remote terminal (Linux) session in order to work via the command line interface.

Note

To receive assistance with your AWS Elemental appliances and software products, see the AWS Elemental Support Center.

Sending commands

  • Unless otherwise stated, enter all Linux shell commands from the home directory (/home/elemental).

  • To ensure that the commands are executed regardless of your user permissions, use "sudo" to run the command as a superuser.