Skip to main content

Prerequisites to upgrade ArcGIS Enterprise on AWS

No matter what method you use to upgrade ArcGIS Enterprise on AWS, complete the following tasks before you upgrade the deployment:

  • Determine if you can upgrade directly to the latest version of ArcGIS Enterprise, or if you must upgrade to an interim version first. See ArcGIS upgrades on AWS for information.

  • Obtain the required ArcGIS licenses for the current software version. Download the license files from your account in My Esri.

  • Ensure that all required ports are open or available.

    Consult the port lists for each component and the port diagram (PDF).

  • Ensure that no one is connected to your ArcGIS Enterprise or ArcGIS Server sites.

    Caution:

    Do not stop the Portal for ArcGIS, ArcGIS Server, or ArcGIS Data Store services. If you stop those services, the webgisdr utility cannot create a backup of the deployment.

  • Create a backup of the deployment before you upgrade it or apply a patch to it.

    You can use the webgisdr utility provided with Portal for ArcGIS to create a backup of most components in an ArcGIS Enterprise deployment. This backup allows you to restore the deployment using the same URLs if you encounter issues that require you to revert to your old deployment.

    Note:

    Depending on what version you are upgrading from, some data store types may not be included in this backup. If you are upgrading a deployment that contains data store types not included when you run the webgisdr utility, use the ArcGIS Data Store backupdatastore utility to create backups of those data store types before you upgrade.

    If you deployed ArcGIS Enterprise components on a single Elastic Compute Cloud (EC2) instance, you can create an Amazon Machine Image (AMI) from the existing EC2 instance before upgrading. You can use this image to redeploy if any issues arise during upgrading. If you have to redeploy, you must deploy using the same portal URL.

    For instructions to upgrade a stand-alone ArcGIS Server site, see Back up and restore an ArcGIS Server site configuration.

  • If the deployment includes a single-machine ArcGIS Notebook Server site, you may need to move the workspace directory.

Operating system upgrades

Before you upgrade to 12.2, ensure the operating system versions on the Amazon EC2 machines used by your deployment are supported with ArcGIS Enterprise 12.2 on AWS. If they are not, you must upgrade the operating system before you upgrade the ArcGIS Enterprise components.

Manual upgrades of components in Auto Scaling groups

If you will be upgrading ArcGIS Enterprise components using the same method as an on-premises deployment, you must remove all EC2 instances running ArcGIS Enterprise component software from their AWS Auto Scaling groups.

The following components are deployed in an Auto Scaling group when you use ArcGIS Enterprise Cloud Builder for AWS or a CloudFormation template provided by Esri to create a highly available deployment:

  • ArcGIS Server

  • ArcGIS Notebook Server

  • ArcGIS Data Store spatiotemporal big data store

Important:

Once upgraded, you cannot put the instances back in the Auto Scaling group; you must manually add instances to or delete instances from the site or cluster when needed after upgrading, and you cannot use the Lambda functions created by the templates to stop and start these instances.

If you don't remove the instances or if you put the instances back in the Auto Scaling group after you upgrade, instances added to the site or cluster by the Auto Scaling group will be running the old version of the software. You cannot have multiple versions of ArcGIS Data Store, so this can corrupt your deployment.

Before you manually upgrade these components, complete the following steps to remove the EC2 instances from their respective Auto Scaling groups:

  1. Sign in to AWS Management Console and find the Auto Scaling group associated with the site or the data store cluster.

  2. Change the minimum capacity and maximum capacity properties of the Auto Scaling group to 0.

  3. Remove all the EC2 instances from the Auto Scaling group.

  4. Change the desired capacity property of the Auto Scaling group to 0.

  5. After you remove all EC2 instances, delete the Auto Scaling group to prevent anyone from adding the instances back after the site or cluster is upgraded.

  6. Repeat these steps for each component in an Auto Scaling group.