Follow the instructions in this procedure to upgrade the version of SignServer and note that the same steps apply for restoring a backup.

Currently used SignServer version

The version of SignServer is visible in the top-right corner of the SignServer Administration home screen.

Backup Existing Instance

  1. Using the SSH key that you selected when procuring the instance, SSH into the SignServer Cloud instance using the username ec2-user.

    # ssh -i ssh-key.pem ec2-user@elastic-ip.compute-1.amazonaws.com
    CODE

  2. Run the command sudo su to get elevated privileges:

    # sudo su
    CODE

  3. Change to the /opt/PrimeKey/support directory.

  4. Run the script system_backup.sh to create a backup of your system.
  5. Press Y to proceed and enter a password to protect the backup once prompted:

  6. Make a note of the name of the backup file created. Copy the backup file to a directory that is accessible by the ec2-user, for example /home/ec2-user/.
    In this case, the file "/opt/PrimeKey/support/backup_files/signserver_db-ip-172-16-0-128.ec2.internal-1509663778.tar.gz" is copied to /home/ec2-user/:

    # cp /opt/PrimeKey/support/backup_files/signserver_db-ip-172-16-0-128.ec2.internal-1509663778.tar.gz /home/ec2-user/
    CODE


Copy Backup to New Instance

Using either the command line interface (CLI) or a Secure Copy Protocol (SCP) utility, copy the file to your local system. You can copy the file directly from one instance to another if your VPC allows it. In this example, we will bring the file down locally and then SCP it to the new instance.

  1. Copy the file to your local system, using either CLI or a SCP utility:

  2. Using the CLI:

    # scp -i ~/Documents/C2\ Comp/PrimeKey/EC2\ Creds/c2-ssh/c2-ssh.pem ec2-user@ec2-34-229-187-81.compute-1.amazonaws.com:/home/ec2-user/signserver_db-ip-172-16-0-128.ec2.internal-1509663778.tar.gz ~/Downloads/signserver_db-ip-172-16-0-128.ec2.internal-1509663778.tar.gz
    CODE

  3. Using a SCP utility (in this case Cyberduck):

    1. Specify details to connect to your instance, for example hostname, username, and SSH key):
    2. Connect to the instance and download the file to the local system:
    3. Wait for the download to complete.
  4. Start a new instance from the Amazon AWS Marketplace. Ensure to select the correct version in the Version list menu (the most recent version is by default selected). For more information, refer to the SignServer Cloud Launch Guide.
  5. Wait for the new instance to start and retrieve the superadmin certificate for the new version. For more information, refer to the SignServer Cloud Launch Guide.
  6. Access the administration interface for the new instance.
    Note the version of the new instance in the top-right corner of the SignServer Administration home screen.

  7. SCP the backup file created in section Backup Existing Instance and copied to the new instance using the instructions in step 1 above.
    If using the CLI, the command will be a bit different since you are copying local to remote.

    # scp -i ~/Documents/C2\ Comp/PrimeKey/EC2\ Creds/c2-ssh/c2-ssh.pem ~/Downloads/signserver_db-ip-172-16-0-128.ec2.internal-1509663778.tar.gz ec2-user@ec2-52-23-217-245.compute-1.amazonaws.com:/home/ec2-user/
    CODE

  8. Once copied, SSH into the new host.

  9. Change to the /opt/PrimeKey/support directory.

Restore Backup on New Instance

  1. Run the script system_restore.sh by pointing it to the backup file location after the script. In this example, the backup file is located in /home/ec2-user/ and the file name is signserver_db-ip-172-16-0-128.ec2.internal-1509663778.tar.gz.

    # /opt/PrimeKey/support/system_restore.sh /home/ec2_user/signserver_db-ip-172-16-0-128.ec2.internal-1509663778.tar.gz
    CODE

  2. Confirm the script and then enter the password for your backup once prompted.

  3. Specify if you would like the existing backup of the system to be encrypted. If so, enter the password for the file to be encrypted with.
    A backup of the existing database will be located at /opt/PrimeKey/support/backup_files and SSL files will be backed up to /etc/httpd/ssl_backup.

  4. Access your new instance and verify that your workers and configuration appears in the new instance.

  5. Generate new TLS certificates for your new instance. Since you likely have a new public and internal IP on this node, new certificates are needed to match the new instance. Run the following script to generate new certs. Refer to the AWS TLS Certificate Generation Guide for more details if custom IP and DNS names are needed.

    # /opt/PrimeKey/support/new_tls_cert.sh -p
    CODE