Updating - In-Place Updates
  • Dark
    Light

Updating - In-Place Updates

  • Dark
    Light

Overview

Updating via the "In-Place" upgrade method means upgrading an existing instance without bringing up a new instance and migrating your resources over. This can be done either via the in-client option or manually via SSH.

Caution

Always back up your instance before performing any updates!


Preparing to update

  • Before updating a Matillion ETL instance, please ensure that the hostname packages.matillion.com is whitelisted.
  • Make sure you have taken a backup prior to making any changes.
  • Make sure you are able to quickly restore from the backup in the event of any problems.


Updating in-client

The in-client upgrade method does not inherently use backups nor is it testable before committing to the upgrade. However, it is very simple to execute and may fit better into your workflow than the Machine Images & Migration method.

1. Click Admin in the top-right of the user interface (UI), and then click Matillion ETL Updates. The Matillion ETL Updates dialog box will open.

2. Check for software updates using the Check for Updates button. Available updates will be listed in the console and the Update button will become available if these can be installed.

Matillion ETL Updates dialog box

3. Click the Update button when you are ready to begin the update process.


Updating manually via SSH

The AMI comes pre-configured with a software repository where updates are published. Therefore a standard 'sudo yum update matillion' is all that is required to update the Matillion software on the AMI.

1. Connect to your Matillion ETL instance via SSH. The method to do this will differ depending on your hosting platform.

Important information for AWS users

Prior to an upgrade from Amazon Linux 1 to CentOS, connecting via SSH to your Matillion ETL instance used a default username ec2-user. However, following the upgrade, the default username is now centos.

This should not be confused with the Matillion ETL application username, which remains ec2-user.

2. Once connected issue the following command: sudo yum update matillion-universal

3. Follow the on-screen instructions.

4. Restart Apache Tomcat using the following: sudo service tomcat8 restart

5. Log out of your session with: exit

Note

If you run the AMI inside a VPC and do not allow outbound internet access, then updates will not be possible using the standard update procedure. Contact support for details on how to do so manually.