In-place update

Updating via the in-place method means updating an existing instance to a newer version. You can achieve this either via the in-client option, or manually via SSH.

Updating is a distinct and separate process to migrating. Read Updating and migrating overview to learn the difference between these two processes and determine whether in-place update is the best option for you.

---

Prerequisites

• Before updating a Matillion ETL instance, always take a backup of the instance and make sure you are able to quickly restore from the backup in the event of any problems. Refer to the following for more information:

  • AWS backups.
  • GCP backups.
  • Azure backups.

• Ensure that the following URLs are allowed:

  artifacts.matillion.com/rpm/matillion-metl/stable
  artifacts.matillion.com/rpm/matillion-cdata/stable
  

• There are CentOS and PostgreSQL repositories that are enabled on the instance by default. The CentOS repositories are mirrors that can change, so can be difficult to allow. You can disable or point to an internal repository instead if required.

---

Performing an in-client update

1. In Matillion ETL, click Admin → Matillion ETL Updates. This will open the Matillion ETL Updates dialog.
2. Click the Check for Updates button to see if there are any updates waiting to be performed. Available updates will be listed in the console and the Update button will become available if these can be installed.
3. Click the Update button when you are ready to begin the update process.

---

Performing an update via SSH

The AMI comes pre-configured with a software repository where updates are published. Therefore a standard sudo yum update matillion command is all that's required to update the Matillion ETL 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:

   • Amazon Web Services
   • Microsoft Azure
   • Google Cloud Platform

   Note

   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 default 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 tomcat 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.

Warning

You can't choose which release this method will update to, so you may be updating the instance to a short-term support (STS) release. If you prefer to remain on long-term support (LTS) releases, you should instead use the method described in Updating to a specific release, which lets you pick the specific release you want to update to.

Read Matillion ETL support lifecycle for details of the differences between STS and LTS releases.