Checklist: Upgrading Your AWS Cluster
Throughout the rolling upgrade process, services not actively being upgraded would continue to be available. Services that utilize the ArcSight Database, such as event ingestion and search, would be interrupted during the Database upgrade phase, but any in-flight data would be cached and processed as soon as the Database upgrade completes.
If you deployed and configured your system for high availability, during the rolling Kubernetes worker node upgrade process, services delivered by pods on the affected worker node would be restarted on another worker node. Similarly, the upgrade of Kubernetes pods is performed in a rolling manner, so there would be a brief pod-level service pause as pods are restarted to perform the upgrade. Some services, such as Transformation Hub, can be configured for high availability with pod replicas so that there are no service pauses during the rolling upgrade.
Use this checklist to complete the upgrade tasks in the listed order.
|
|
Task |
See |
|---|---|---|
|
Ensure that you are upgrading from and to the correct version of ArcSight Platform |
ArcSight Platform Upgrade Paths |
|
|
Identify the product versions, files to download, and known issues related to the upgrade |
"Downloading the ArcSight Platform Installation Files" in the Release Notes for ArcSight Platform |
|
|
Download the installation packages |
Downloading the Upgrade Packages for an AWS Deployment |
|
|
(Conditional) If your deployment includes Intelligence or Recon, prepare the ArcSight Database for the backup process |
|
|
|
Back up the ArcSight Platform configuration data; the Postgres database, which contains the configuration of your deployed capabilities; and, if you have Intelligence or Recon deployed, the ArcSight Database |
|
|
|
(Conditional) If your deployment includes Intelligence or Recon, upgrade the Database |
|
|
|
Upgrade the OMT infrastructure |
|
|
|
Create new target groups with the new port values for the front-end and portal ingress controller services |
|
|
|
Upgrade the deployed capabilities |
|
|
|
(Conditional) If your deployment includes Intelligence, back up Elasticsearch data |
(Conditional - For Intelligence Deployments only) Elasticsearch data backup for Intelligence |
|
|
Upgrade Kubernetes version of the control plane and worker nodes |
|
|
|
(Conditional) If your deployment includes Intelligence and the Elasticsearch recovery actions in Step 8 of the EKS upgrade procedure succeeded, perform the workarounds |
(Conditional – Intelligence) Running Analytics on Demand after Recovering Elasticsearch |
|
|
(Conditional) If your deployment includes Intelligence and the Elasticsearch recovery actions in Step 8 of the EKS upgrade procedure failed, perform the workarounds |
(Conditional – Intelligence) Resolving Issues before Running Analytics on Demand |
|
|
Complete post-upgrade tasks |
Completing Post Upgrade Tasks |
|
|
(Conditional) If your environment includes ESM, you should upgrade to the latest version |
|
|
|
(Conditional) If you have purchased licenses for additional capabilities, deploy them to your environment |