The templates listed on this page use CloudFormation to create an ArcGIS Enterprise 10.7.1 deployment or ArcGIS Server 10.7.1 roles on Amazon Web Services (AWS).
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 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:
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:
You can also use this template to create a VPC environment for your ArcGIS Enterprise deployment.
|Create an Amazon VPC||Create an Amazon VPC with two subnets that ArcGIS Enterprise can be deployed in. ReadMe||View||Launch Stack|
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.
|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 2019||View||Launch Stack|
|Ubuntu LTS 18.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 2019||View||Launch Stack|
|Ubuntu LTS 18.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.
|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|
In addition to the base ArcGIS Enterprise deployment, you can add functionality and capacity with additional ArcGIS Server sites.
|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 2019||View||Launch Stack|
|Ubuntu 18.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.
|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 2019||View||Launch Stack|
|Ubuntu LTS 18.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.
|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|
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:
You can create a ClouldFormation stack using AWS Command Line Interface and AWS SDKs for different languages. See Tools for Amazon Web Services for more information. A sample Python script is provided to create base ArcGIS Enterprise and ArcGIS Server CloudFormation stacks.
<ArcGIS Server Installation Directory>/arcgis/server/toolsfolder on Linux.
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
Step 0: Before you upgrade, make a backup of the existing system. Before upgrading an ArcGIS Enterprise deployment, use the webgisdr tool installed with Portal for ArcGIS to create a backup of the ArcGIS Enterprise components. This backup allows you to restore your deployment using the same URLs if you encounter issues that require you to revert to your old deployment. Note: If you have a spatiotemporal big data store in your deployment, use the ArcGIS Data Store backupdatastore utility to create a backup of it, as it is not included in the backup created by the webgisdr tool.
The following steps are for upgrading 10.6.1 or 10.7 to 10.7.1. The 10.6.1 or 10.7 deployments might be created from Esri sample cloudformation templates or ArcGIS Enterprise Cloud Builder Command Line Interface.
Chef Automation can help upgrade in-place and upgrade from 10.6 or older version to 10.7.1. The deployments might be created from Esri sample cloudformation templates or ArcGIS Enterprise Cloud Builder Command Line Interface.
It is recommended to move all the instances out of the auto-scaling group, and upgrade the ArcGIS components as you would upgrade an on-premise deployment.
DeploymentLogs in CloudWatch. The deployment logs are exported to CloudWatch. In the CloudFormation stack, you can click on Resources and there is the link for the “DeploymentLogs in the list. Clicking on the link will take you to the deployment logs on all started instances, including the chef-run.log.
You can also 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.