Esri CloudFormation Templates 10.6.1

CloudFormation templates to deploy ArcGIS Enterprise on Amazon Web Services

The templates listed on this page use CloudFormation to create an ArcGIS Enterprise 10.6.1 deployment or ArcGIS Server 10.6.1 roles on Amazon Web Services (AWS).

Looking for a different Esri template version?

10.6 10.5.1 10.5 10.4.1 10.4 10.3.1

Table of Contents

To use the CloudFormation templates

Esri Cloud Builder Command Line Interface for Amazon Web Services

The CloudFormation templates below create either one base Enterprise deployment or one ArcGIS Server role deployment. An optimized ArcGIS Enterprise deployment often requires several ArcGIS Server and ArcGIS Data Store machines, the ArcGIS Enterprise Cloud Builder Command Line Interface for Amazon Web Services an intuitive tool for automating cloud deployments of ArcGIS Enterprise to create these deployments.

ArcGIS Enterprise CloudFormation templates

Create a VPC to deploy ArcGIS Enterprise

ArcGIS Enterprise needs to run in a VPC environment. Most Amazon Web Services accounts have a default AWS VPC created. Use this default VPC, create another VPC manually, or use the template described in this section to create a VPC.

ArcGIS Server requires the hostname to be valid. On the machine where ArcGIS Server is running, you need to make sure you can ping the hostname. To check that, run the following:

  • >hostname

    • This returns the hostname.

  • >ping "<the output of the hostname above>"

If the hostname is accessible, this command returns the valid ip address.

When you manually create a VPC, the following properties need to be ensure your hostname is accessible:

  • DNS resolution: Set to yes.
  • DNS hostname: Set to yes.
  • DHCP options set: You must have both domain-name and domain-name-servers set. For example:
    domain-name=ec2.internal; domain-name-servers=AmazonProvided

You can also use this template to create a VPC environment for your ArcGIS Enterprise deployment.

Template Name Description View Launch
Create an Amazon VPC Create an Amazon VPC with two subnets that ArcGIS Enterprise can be deployed in. ReadMe View Launch Stack

Deploy base ArcGIS Enterprise

A base ArcGIS Enterprise deployment includes Portal for ArcGIS, a GIS Server to be used as the portal's hosting server, and a relational and a tile cache data store created through ArcGIS Data Store and registered with the portal's hosting server.

These templates create a base ArcGIS Enterprise deployment You also have the option to include a spatiotemporal big data store with your base deployment when you use the following templates.

Template Name Description Platform View Launch
Single-machine deployment Create a base ArcGIS Enterprise deployment on a single machine. This is the minimal all-in-one configuration, where all the components are installed on a single instance. ReadMe Windows 2016 View Launch Stack
Ubuntu LTS 16.04 View Launch Stack
Highly available deployment Create a highly available deployment with two machines. Both machines contain all ArcGIS Enterprise components. The second machine acts as a standby ArcGIS Enterprise machine, which minimizes downtime in scenarios when one machine is unavailable. ReadMe Windows 2016 View Launch Stack
Ubuntu LTS 16.04 View Launch Stack

ELB for highly available base ArcGIS Enterprise deployment. The highly available base ArcGIS Enterprise CloudFormation template allows you to use an existing ELB. This option makes it easier to keep your existing domain_name mapping. The existing ELB has certain requirements, for example, the VPC, SSL cert, etc. It is recommended to create the ELB using this template.

 View Launch Stack
Disaster recovery deployment in a different region Build an identical ArcGIS Enterprise deployment in a different region and periodically synchronize content from the active deployment to a deployment in a different region. If the active deployment goes offline, you can switch your clients to use the second deployment. ReadMe Windows&Ubuntu

Deploy additional ArcGIS Server deployments

In addition to the base ArcGIS Enterprise deployment, you can add functionality and capacity with additional ArcGIS Server sites.

Template Name Description Platform View Launch
ArcGIS GIS Server This template creates a general purpose GIS Server site, GeoAnalytics Server site, or Image Server Sites that you can set as Raster analytics Server or Image Hosting Server for the portal in your base ArcGIS Enterprise deployment. You just need to use different Server license files to deploy different ArcGIS Server roles. ReadMe Windows 2016 View Launch Stack
Ubuntu 16.04 LTS View Launch Stack

ELB for ArcGIS GIS Server deployment. The ArcGIS GIS Server CloudFormation template allows you to use an existing ELB. This option makes it easier to keep your existing domain_name mapping. The existing ELB has certain requirements, for example, the VPC, SSL cert, etc. It is recommended to create the ELB using this template.

 View Launch Stack
ArcGIS GeoEvent Server This template creates a single-machine ArcGIS GeoEvent Server site that can be scaled up to a multi-machine deployment that you can federate with the portal in a base ArcGIS Enterprise deployment. To archive stream service data, you must have a spatiotemporal big data store, which must run on separate instances from the other components. ReadMe Windows 2016 View Launch Stack
Ubuntu LTS 16.04 View Launch Stack

ELB for ArcGIS GeoEvent Server deployment. The ArcGIS GIS Server CloudFormation template allows you to use an existing ELB. This option makes it easier to keep your existing domain_name mapping. The existing ELB has certain requirements, for example, the VPC, SSL cert, etc. It is recommended to create the ELB using this template.

 View Launch Stack
Stand-alone ArcGIS Server sites Create an autoscaling group of stand-alone ArcGIS Server sites behind an Elastic Load Balancer. You can create a GIS Server site, Image Server site, or GeoEvent Server site. ReadMe Windows&Ubuntu View Launch Stack
Top of Page

Stop and start all the instances in your CloudFormation stack

The CloudFormation stacks for highly available base enterprise deployments, ArcGIS GIS Server deployments, and ArcGIS GeoEvent Server deployments will create Lambda functions to help stop and start all the EC2 instances in your deployment stack. It's recommended to use these Lamdba functions to stop and start all the EC2 instances and to scale auto-scaling groups up or down rather than perform those tasks manually.

These Lambda functions have the name starting with "<CloudFormation Stack Name>-StartStackFunction" or "<CloudFormation Stack Name>-StopStackFunction". You can invoke the function using the sample event data provided in the AWS Management Console following these steps:

  • On the functions page, select the function you want to run, choose Test from the Actions list.
  • In the Configure test event page, choose Create new test event and in Event template, leave the default Hello World option. Enter an Event name and click on Create
  • On the yourfunction page, click on Test
Top of Page

Automate CloudFormation stack creation using Python and PowerShell

You can create a ClouldFormation stack using AWS Command Line Interface, AWS Tools for Windows PowerShell, and AWS SDKs for different languages. See Tools for Amazon Web Services for more information. Sample Python and PowerShell scripts are provided to create ArcGIS Enterprise and ArcGIS Server CloudFormation stacks.

To run the Python script:

  • Make sure you have Python installed. Python is installed with ArcGIS Desktop and ArcGIS Server under the C:\Python27\ folder or <ArcGIS Server Installation Directory>/arcgis/server/tools folder on Linux.
  • Download and install AWS SDK for Python (boto).
  • Download sample python scripts and run them with the parameters required by your CloudFormation templates.
    For example, the single-machine ArcGIS Enterprise file, cf_parameters_win_allinone_webgisstack.json, defines the parameters required to deploy all base ArcGIS Enterprise components on one Windows instance on AWS. Modify the parameters accordingly. Run the file by typing:

    >> python cloudformation_stack_creation.py <Your AWS Access key> <Your AWS Secret Access Key> cf_parameters_win_allinone_webgisstack.json

To run the PowerShell script:

  • Download and install AWS Tools for Windows PowerShell.
  • Download sample PowerShell scripts and modify accordingly.
  • Two sample Powershell scripts are included in the downloaded zip file:
    • arcgis-WebGIS-ha-windows.ps1 : Use this to create a highly available ArcGIS Enterprise deployment on Windows.
    • arcgis-server-ubuntutu.ps1: Use this to create an ArcGIS Server site that uses DynamoDB and S3 for the site's configuration store.
Top of Page

Upgrade to 10.6.1

step 0: make a backup of the existing system.Use the webgisdr utility. This tool helps make a backup of all the components of your deployment – Portal for ArcGIS, any federated ArcGIS Server sites, and ArcGIS Data Store – into one single backup file.

Upgrade standalone base ArcGIS Enterprise machine from 10.6 to 10.6.1

  • On Windows:
    1. Login to the EC2 instance.
    2. Upload the 10.6.1 ArcGIS Server installation file (ArcGIS_Server_Windows_1061_163968.exe), Portal for ArcGIS (Portal_for_ArcGIS_Windows_1061_163979.exe), ArcGIS DataStore (ArcGIS_DataStore_Windows_1061_163980.exe), ArcGIS Web Adaptor for IIS (Web_Adaptor_for_Microsoft_IIS_1061_163981.exe) installation exes to a folder, e.g. C:\temp folder.
    3. Upload the 10.6 version of software authorization files for ArcGIS Server and Portal for ArcGIS to a folder, e.g. C:\temp folder.
    4. Download the Esri ArcGIS 10.6.1 cookbook to the EC2 instance; unzip it; copy over cookbooks folder inside it to replace the C:\chef\cookbooks folder.
    5. Open the C:\Chef\node.json file in a text editor, add the version to 10.6.1; copy over the 10.6.1 setups into a folder and define it as ""archives" under "repository"; "change to the 10.6.1 version of authorization file, like the sample base_enterprise_allinone_windows.json file.
    6. Open a command line windows as administrator, run
      chef-solo -j c:\chef\node.json
  • On Ubuntu:
    1. SSH to the EC2 instance as the ubuntu user.
    2. Upload the 10.6.1 ArcGIS Server (ArcGIS_Server_Linux_1061_164044.tar.gz), Portal for ArcGIS (Portal_for_ArcGIS_Linux_1061_164055.tar.gz), ArcGIS DataStore (ArcGIS_DataStore_Linux_1061_164056.tar.gz), ArcGIS Web Adaptor for Java (Web_Adaptor_Java_Linux_1061_164057.tar.gz) installation file to a folder, e.g. /tmp/upgrade folder.
    3. Upload the 10.6 version of software authorization files for ArcGIS Server and Portal for ArcGIS to a folder, e.g. /tmp/upgrade folder.
    4. Download the Esri ArcGIS 10.6.1 cookbook to the EC2 instance; unzip it; copy over cookbooks folder inside it to replace the /var/chef/cookbooks folder.
    5. Open the /tmp/node.json file in a text editor, add the version to 10.6.1; copy over the 10.6.1 setups into a folder and define it as ""archives" under "repository"; change to the 10.6.1 version of authorization file, like the sample base_enterprise_allinone_ubuntu.jsonfile.
      Note: If you don't have the /tmp/node.json file, you can get it by running
      sudo cfn-init -v -c secondpass -s <StackName> -r AllInOneEC2Instance --region <AWS::Region>
    6. Run
      sudo chef-solo -j /tmp/node.json

Upgrade highly available base ArcGIS Enterprise deployment from 10.6 to 10.6.1

  • Make sure the primary machine for Portal for ArcGIS and ArcGIS DataStore (TileCache and Relantiaonal DataBase) are all on the same machine. It's referred as Primary machine in this session. The other machine is referred as Standby machine.
  • On Windows:
    1. Login to the standby machine first.
      1. Upload the 10.6.1 ArcGIS Server installation file (ArcGIS_Server_Windows_1061_163968.exe), Portal for ArcGIS (Portal_for_ArcGIS_Windows_1061_163979.exe), ArcGIS DataStore (ArcGIS_DataStore_Windows_1061_163980.exe), ArcGIS Web Adaptor for IIS (Web_Adaptor_for_Microsoft_IIS_1061_163981.exe) installation exes to a folder, e.g. C:\temp folder.
      2. Upload the 10.6 version of software authorization files for ArcGIS Server and Portal for ArcGIS to a folder, e.g. C:\temp folder.
      3. Download the Esri ArcGIS 10.6.1 cookbook to the EC2 instance; unzip it; copy over cookbooks folder inside it to replace the C:\chef\cookbooks folder.
      4. Open the C:\Chef\node.json file in a text editor, add the version to 10.6.1; copy over the 10.6.1 setups into a folder and define it as ""archives" under "repository"; change to the 10.6.1 version of authorization file, like the sample base_enterprise_ha_windows_standby.json file.
      5. Open a command line windows as administrator, run
        chef-solo -j c:\chef\node.json
    2. Login to the primary machine next.
      1. Upload the 10.6.1 ArcGIS Server installation file (ArcGIS_Server_Windows_1061_163968.exe), Portal for ArcGIS (Portal_for_ArcGIS_Windows_1061_163979.exe), ArcGIS DataStore (ArcGIS_DataStore_Windows_1061_163980.exe), ArcGIS Web Adaptor for IIS (Web_Adaptor_for_Microsoft_IIS_1061_163981.exe) installation exes to a folder, e.g. C:\temp folder.
      2. Upload the 10.6 version of software authorization files for ArcGIS Server and Portal for ArcGIS to a folder, e.g. C:\temp folder.
      3. Download the Esri ArcGIS 10.6.1 cookbook to the EC2 instance; unzip it; copy over cookbooks folder inside it to replace the C:\chef\cookbooks folder.
      4. Open the C:\Chef\node.json file in a text editor, add the version to 10.6.1; copy over the 10.6.1 setups into a folder and define it as ""archives" under "repository"; change to the 10.6.1 version of authorization file, like the sample base_enterprise_ha_windows_primary.json file.
      5. Open a command line windows as administrator, run
        chef-solo -j c:\chef\node.json
  • On Ubuntu:
    1. ssh to the standby machine as ubuntu userfirst.
      1. Upload the 10.6.1 ArcGIS Server (ArcGIS_Server_Linux_1061_164044.tar.gz), Portal for ArcGIS (Portal_for_ArcGIS_Linux_1061_164055.tar.gz), ArcGIS DataStore (ArcGIS_DataStore_Linux_1061_164056.tar.gz), ArcGIS Web Adaptor for Java (Web_Adaptor_Java_Linux_1061_164057.tar.gz) installation file to a folder, e.g. /tmp/upgrade folder.
      2. Upload the 10.6 version of software authorization files for ArcGIS Server and Portal for ArcGIS to a folder, e.g. /tmp/upgrade folder.
      3. Download the Esri ArcGIS 10.6.1 cookbook to the EC2 instance; unzip it; copy over cookbooks folder inside it to replace the /var/chef/cookbooks folder.
      4. Open the /tmp/node.json file in a text editor, add the version to 10.6.1; copy over the 10.6.1 setups into a folder and define it as ""archives" under "repository"; change to the 10.6.1 version of authorization file, like the sample base_enterprise_ha_ubuntu_standby.json file.
        Note: If you don't have the /tmp/node.json file, you can get it by running
        sudo cfn-init -v -c secondpass -s <StackName> -r SecondaryServerEC2Instance --region <AWS::Region>
      5. Run
        sudo chef-solo -j /tmp/node.json
    2. Login to the primary machine next.
      1. Upload the 10.6.1 ArcGIS Server (ArcGIS_Server_Linux_1061_164044.tar.gz), Portal for ArcGIS (Portal_for_ArcGIS_Linux_1061_164055.tar.gz), ArcGIS DataStore (ArcGIS_DataStore_Linux_1061_164056.tar.gz), ArcGIS Web Adaptor for Java (Web_Adaptor_Java_Linux_1061_164057.tar.gz) installation file to a folder, e.g. /tmp/upgrade folder.
      2. Upload the 10.6 version of software authorization files for ArcGIS Server and Portal for ArcGIS to a folder, e.g. /tmp/upgrade folder.
      3. Download the Esri ArcGIS 10.6.1 cookbook to the EC2 instance; unzip it; copy over cookbooks folder inside it to replace the /var/chef/cookbooks folder.
      4. Open the /tmp/node.json file in a text editor, add the version to 10.6.1; copy over the 10.6.1 setups into a folder and define it as ""archives" under "repository"; change to the 10.6.1 version of authorization file, like the sample base_enterprise_ha_ubuntu_standby.json file.
        Note: If you don't have the /tmp/node.json file, you can get it by running
        sudo cfn-init -v -c secondpass -s <StackName> -r PrimaryServerEC2Instance --region <AWS::Region>
      5. Run
        sudo chef-solo -j /tmp/node.json

Upgrade Spatial Temporal DataStore from 10.6 to 10.6.1

If you have Spatial Temporal DataStore deployed with your base ArcGIS Enterprise Deployment, upgrade the spatial temporal datastore after you upgrade the base ArcGIS Enterprise deployment.

  • On Windows:
    1. Change ‘Min’ property of the stack’s AutoScaling group to 0
    2. Move all the BDS EC2 instances from the 10.6 stack’s AutoScaling group.
    3. Change ‘Desired’ of the stack’s AutoScaling group to 0.
    4. Run install on all the spatial temporal datastore instances except one instance.
      1. Login to one EC2 instance.
      2. Upload the 10.6.1 ArcGIS DataStore installation file (ArcGIS_DataStore_Windows_1061_163980.exe) to a folder, e.g. C:\temp folder.
      3. Download the Esri ArcGIS 10.6.1 cookbook to the EC2 instance; unzip it; copy over cookbooks folder inside it to replace the C:\chef\cookbooks folder.
      4. Open the C:\Chef\node.json file in a text editor, add the version to 10.6.1; copy over the 10.6.1 setups into a folder and define it as ""archives" under "repository"; change to the 10.6.1 version of authorization file, like the sample spatialtemporal_windows_install.json file.
      5. Open a command line windows as administrator, run
        chef-solo -j c:\chef\node.json
      6. Repeat the above steps on all spatialtemporal datastore machines except one machine.
    5. On the last machine, run the same steps but using a different json file, like the sample spatialtemporal_windows_configure.json file.
      chef-solo -j c:\chef\node.json
    6. Click on the parameters tab for your current 10.6 base ArcGIS Enterprise CloudFormation stack and make a copy of all the input parameters you originally used.
    7. Create a new CloudFormation stack by Launch Stack using 10.6.1 arcgis-bds-windows.template.
      Template Name Description Platform View Launch
      Upgrade Spatial Temporal DataStore AutoScaling Group Upgrade the Spatial Temporal DataStore AutoScaling Group created by ArcGIS base Enterprise deployment CloudFormation stack at 10.6 to 10.6.1. Windows 2016 View Launch Stack
      Use the same input parameters as in the 10.6 base ArcGIS Enterprise CloudFormation stack, except:
      1. ServerInstancePrivateIp: private IP address of the base enterprise EC2 instance.
      2. BDSInstances: 0
      3. ELBName: the ELB name used by the 10.6 base ArcGIS Enterprise CloudFormation stack.
      4. SecurityGroupId: pick the security group id of the used by the 10.6 ArcGIS GIS Server CloudFormation stack.
      5. SiteAdmin and SiteAdminPassword: the current username and password for the 10.6 base ArcGIS Enterprise.
    8. Change ‘Max’ of the AutoScaling group of the new BDS CloudFormation stack to the number of existing BDS EC2 instances.
    9. Add the old upgraded BDS EC2 instances to the AutoScaling group of the new BDS CloudFormation stack.
    10. Change ‘Desired’ of the AutoScaling group of the new BDS CloudFormation stack to the number of existing BDS EC2 instances.
  • On Ubuntu:
    1. Change ‘Min’ property of the stack’s AutoScaling group to 0
    2. Move all the BDS EC2 instances from the 10.6 stack’s AutoScaling group.
    3. Change ‘Desired’ of the stack’s AutoScaling group to 0.
    4. Run install on all the spatial temporal datastore instances except one instance.
      1. ssh to one EC2 instance as ubuntu user
      2. Upload the 10.6.1 ArcGIS DataStore installation file (ArcGIS_DataStore_Linux_1061_164056.tar.gz to a folder, e.g. /tmp/upgrade folder.
      3. Download the Esri ArcGIS 10.6.1 cookbook to the EC2 instance; unzip it; copy over cookbooks folder inside it to replace the /var/chef/cookbooks folder.
      4. Open the /tmp/node.json file in a text editor, add the version to 10.6.1; copy over the 10.6.1 setups into a folder and define it as ""archives" under "repository"; change to the 10.6.1 version of authorization file, like the sample spatialtemporal_ubuntu_install.json file.
        Note: If you don't have the /tmp/node.json file, you can get it by running
        sudo cfn-init -v -c secondpass -s <StackName> -r LaunchConfig --region <AWS::Region>
      5. Run
        sudo chef-solo -j /tmp/node.json
      6. Repeat the above steps on all spatialtemporal datastore machines except one machine
    5. On the last machine, run the same steps but using a different json file, like the sample spatialtemporal_ubuntu_configure.json file.
    6. Click on the parameters tab for your current 10.6 base ArcGIS Enterprise CloudFormation stack and make a copy of all the input paramters you originally used.
    7. Create a new CloudFormation stack by Launch Stack using 10.6.1 arcgis-bds-ubuntu.template.
      Template Name Description Platform View Launch
      Upgrade Spatial Temporal DataStore AutoScaling Group Upgrade the Spatial Temporal DataStore AutoScaling Group created by ArcGIS base Enterprise deployment CloudFormation stack at 10.6 to 10.6.1. Ubuntu LTS 16.04 View Launch Stack
      Use the same input parameters as in the 10.6 base ArcGIS Enterprise CloudFormation stack, except:
      1. ServerInstancePrivateIp: private IP address of the base enterprise EC2 instance.
      2. BDSInstances: 0
      3. ELBName: the ELB name used by the 10.6 base ArcGIS Enterprise CloudFormation stack.
      4. SecurityGroupId: pick the security group id of the used by the 10.6 ArcGIS GIS Server CloudFormation stack.
      5. SiteAdmin and SiteAdminPassword: the current username and password for the 10.6 base ArcGIS Enterprise.
    8. Change ‘Max’ of the AutoScaling group of the new BDS CloudFormation stack to the number of existing BDS EC2 instances.
    9. Add the old upgraded BDS EC2 instances to the AutoScaling group of the new BDS CloudFormation stack.
    10. Change ‘Desired’ of the AutoScaling group of the new BDS CloudFormation stack to the number of existing BDS EC2 instances.

Upgrade ArcGIS GIS Server deployment from 10.6 to 10.6.1

  • On Windows:
    1. Change Min and Desired properties of the stack's AutoScaling group to 0.
    2. After all the instances in the AutoScaling group are terminated, remove the terminated machines from the ArcGIS Server site in ArcGIS Server Manager.
    3. Run install on the primary ArcGIS GIS Server instance.
      1. Login to the EC2 instance.
      2. Upload the 10.6.1 ArcGIS Server installation file (ArcGIS_Server_Windows_1061_163968.exe), to a folder, e.g. C:\temp folder.
      3. Upload the 10.6 version of software authorization files for ArcGIS Server and to a folder, e.g. C:\temp folder.
      4. Download the Esri ArcGIS 10.6.1 cookbook to the EC2 instance; unzip it; copy over cookbooks folder inside it to replace the C:\chef\cookbooks folder.
      5. Open the C:\Chef\node.json file in a text editor, add the version to 10.6.1; copy over the 10.6.1 setups into a folder and define it as ""archives" under "repository"; change to the 10.6.1 version of authorization file, like the sample server_windows.json file.
      6. Open a command line windows as administrator, run
        chef-solo -j c:\chef\node.json
    4. Click on the parameters tab for your current 10.6 ArcGIS GIS Server CloudFormation stack and make a copy of all the input paramters you originally used.
    5. Create a new CloudFormation stack by Launch Stack using 10.6.1 arcgis-server-cluster-windows.template.
      Template Name Description Platform View Launch
      Upgrade ArcGIS GIS Server AutoScaling Group Upgrade the AutoScaling Group created by ArcGIS GIS Server deployment CloudFormation stack at 10.6 to 10.6.1. Windows 2016 View Launch Stack
      Use the same input parameters as in the 10.6 ArcGIS GIS Server CloudFormation stack, except:
      1. ServerLicenseFile: the new ArcGIS software authorization file, if it's different from the original one.
      2. FSInstancePrivateIp: private IP address of the file server EC2 instance.
      3. ELBName: the ELB name used by the 10.6 ArcGIS GIS Server CloudFormation stack.
      4. SecurityGroupId: pick the security group id of the used by the 10.6 ArcGIS GIS Server CloudFormation stack.
      5. DBEndpoint: the endpoint of RDS DB instance used by the 10.6 ArcGIS GIS Server CloudFormation stack, if any.
      6. SiteAdmin and SiteAdminPassword: the current username and password for the 10.6 ArcGIS GIS Server site.
  • On Ubuntu:
    1. Change Min and Desired properties of the stack's AutoScaling group to 0.
    2. After all the instances in the AutoScaling group are terminated, remove the terminated machines from the ArcGIS Server site in ArcGIS Server Manager.
    3. Run install on the primary ArcGIS GIS Server instance.
      1. Ssh to the EC2 instance as ubuntu user.
      2. Upload the 10.6.1 ArcGIS Server installation file (ArcGIS_Server_Linux_1061_164044.tar.gz), to a folder, e.g. /tmp/upgrade folder.
      3. Upload the 10.6 version of software authorization files for ArcGIS Server and to a folder, e.g. /tmp/upgrade folder.
      4. Download the Esri ArcGIS 10.6.1 cookbook to the EC2 instance; unzip it; copy over cookbooks folder inside it to replace the /var/chef/cookbooks folder.
      5. Open the /tmp/node.json file in a text editor, add the version to 10.6.1; copy over the 10.6.1 setups into a folder and define it as ""archives" under "repository"; change to the 10.6.1 version of authorization file, like the sample server_ubuntu.json file.
        Note: If you don't have the /tmp/node.json file, you can get it by running
        sudo cfn-init -v -c secondpass -s <StackName> -r PrimaryServerEC2Instance --region <AWS::Region>
      6. Run
        sudo chef-solo -j /tmp/node.json
    4. Click on the parameters tab for your current 10.6 ArcGIS GIS Server CloudFormation stack and make a copy of all the input paramters you originally used.
    5. Create a new CloudFormation stack by Launch Stack using 10.6.1 arcgis-server-cluster-ubuntu.template.
      Template Name Description Platform View Launch
      Upgrade ArcGIS GIS Server AutoScaling Group Upgrade the AutoScaling Group created by ArcGIS GIS Server deployment CloudFormation stack at 10.6 to 10.6.1. Ubuntu LTS 16.04 View Launch Stack
      Use the same input parameters as in the 10.6 ArcGIS GIS Server CloudFormation stack, except:
      1. ServerLicenseFile: the new ArcGIS software authorization file, if it's different from the original one.
      2. FSInstancePrivateIp: private IP address of the file server EC2 instance.
      3. ELBName: the ELB name used by the 10.6 ArcGIS GIS Server CloudFormation stack.
      4. SecurityGroupId: pick the security group id of the used by the 10.6 ArcGIS GIS Server CloudFormation stack.
      5. DBEndpoint: the endpoint of RDS DB instance used by the 10.6 ArcGIS GIS Server CloudFormation stack, if any.
      6. SiteAdmin and SiteAdminPassword: the current username and password for the 10.6 ArcGIS GIS Server site.

Upgrade from 10.5.1 and before to 10.6.1

To upgrade from 10.5.1 and before to 10.6.1, it is recommended to move all the instances in auto-scaling group out and then run manual upgrade steps just like on-premises following upgrade document.

  • Move ArcGIS GIS Server instances that are in an auto-scaling group out.
  • If you have spatial temporal datastore deployment, move the instances out of the auto-scaling group as well.
  • Follow the upgrade documentation, for Windows or Ubuntu, to upgrade ArcGIS Enterprise deployment.
Top of Page

Troubleshooting guide

See Troubleshoot AWS CloudFormation stack creation in the ArcGIS Enterprise on Amazon Web Services help for information on how to identify and correct issues you may encounter when launching a CloudFormation stack using the Esri sample templates.