Open topic with navigation

# Upgrading Deployed Capabilities in AWS

If it has been more that 12 hours since the cluster was installed, you will need to refresh the ECR credentials. See Refreshing the ECR Credentials in Kubernetes.

As part of the upgrade process, you must upgrade your deployed capabilities using the OMT Management Portal. Perform these steps in order:

1. Understanding the Upgrade Prerequisites

2. Upload the Upgrade File

3. Upgrading Deployed Capabilities

## Understanding the Upgrade Prerequisites

Before upgrading the Suite, ensure these requirements are met:

- Ability to access the management portal on port 5443

- The AWS client is configured on the bastion

- The Kubernetes command line tool (`kubectl`) is installed on the bastion and connected to your cluster

- Ensure all pods are running with this command:

      kubectl get pods -A

- Verify you have performed all the required tasks and obtained all installation packages as discussed in Upgrade Prerequisites .

- (Conditional) If you are using custom data identifiers for Intelligence, ensure that you back up the `logstash-config-pipeline` config map that is accessible through the Kubernetes dashboard.

## Upload the Upgrade File

1. Upload the metadata file for the upgrade version to your bastion host, the name of which follows this format: `arcsight-suite-metadata-uv.x.tar.gz`

   For example: `arcsight-suite-metadata-23.2-cloud.tar`

2. Upload offline images of the upgrade version to your bastion host, which follow this format: `{product}-uv.x.tgz`

   For example: `transformationhub-3.5.4.4-cloud.tar`

## Upgrading Deployed Capabilities

1. Change to the following directory:

    cd arcsight-platform-cloud-installer-<VERSION>.zip/aws-scripts/scripts

2. Run the following commands to upload the images to the Elastic Container Registry (ECR). Use the `-F <image file>` option on the command line multiple times for each image to upload. Adjust the value of the `-c` parameter (2 in the instruction below) to up to half your CPU cores in order to increase the speed of the upload.

       ./upload_images_to_ECR  -o $(kubectl get cm -n core base-configmap --output=jsonpath={.data.REGISTRY_ORGNAME}) -c 8 -F arcsight-platform-cloud-installer-<VERSION>.zip/images/fusion-x.x.x.x.tar -F {unzipped-installer-dir}/images/recon-x.x.x.x.tar

3. Accepting the Certificate from the user interface:

   1. Browse to the management portal at https://<virtual_FQDN>:5443.

   2. Click DEPLOYMENT, and select Deployments.

   3. Click the Three Dots (Browse) on the far right and choose Reconfigure.

   4. Accept the certificate.

4. Add new metadata.
   Make sure to copy the `arcsight-suite-metadata-x.x.x.x.tar` to the system where your web browser is running before performing the process below.
5. Browse to the management portal at `https://<virtual_FQDN>:5443`.
   1. Click DEPLOYMENT>Metadata and click + Add.
   2. Select `arcsight-suite-metadata-x.x.x.x.tar` from your system, and click Okay. The new metadata is added to the system.
6. Start the upgrade process.
While the upgrade process is running, if you cannot complete it for any reason, make sure to cancel it before you navigate away from it.

1. Go to DEPLOYMENT > Deployments. Notice the number 1 in the red circle in the Update column.
Minor version changes do not display like regular updates (for example: 22.1.0.15 -> 22.1.0.16.)
2. Click the red circle and select your recently added metadata to initiate the upgrade.

7. From the Update to page, click NEXT until you reach the Import suite images page.
   When prompted to download or transfer images, you can simply click Next to skip the steps. You performed these steps earlier.
8. Ensure that the validation results of container images show a complete number of files.
   When you arrive at the Import suite images page, the images should already be imported, as you performed these steps earlier.

9. Click NEXT until you reach the Upgrade Complete page.

Next Step: Upgrading EKS