ArcGIS GIS Server

Provision a highly available ArcGIS GIS Server site

This template provisions a GIS Server, Image Server, or ArcGIS GeoAnalytics Server site. Optionally, you can have a geodatabase in an Amazon Relational Database Service for SQL Server or PostgreSQL. The geodatabase will be registered as the registered database to the ArcGIS Server site. This template will set up an architecture as shown in the graphic.

Highly available ArcGIS GIS Server site

To deploy this template, follow the steps below:

  • Create an S3 bucket in your account to store Esri authorization files.
    • Create a S3 bucket in your AWS account. You will specify this name in the template parameters when you launch the stack. This bucket is called DeploymentBucket in the template Parameters.
    • Upload your ArcGIS Server license file to the DeploymentBucket. The ArcGIS Server license role will determine the type of site you create: a GIS Server site, Image Server site, or ArcGIS GeoAnayltics Server site.
    • Upload your SSL certificate into AWS Certificate Manager. Write down the Amazon Resource Name (ARN) of the certificate.

  • Create CloudFormation stack using the template.
    Click Launch Stack for this template. There are several parameters that you can set when launching the stack using the template, such as the following:
    • ASInstanceType: The instance type for the EC2 instances that participate in the ArcGIS Server site. In this site, the EC2 instances will be created in an Auto Scaling group. These machines will join the ArcGIS Server site through accessing the ArcGIS Server configuration store.
    • ASInstances: The number of EC2 instances in the ArcGIS Server site that will be created in the Auto Scaling group. This number is the number of machines you want in your ArcGIS Server site.
    • DBEngine:
      • none: No geodatabase in an RDS instance is created.
      • sqlserver-se: A geodatabase will be created in an Amazon RDS for SQL Server instance, standard version. The database will be registered as the ArcGIS Server site’s managed database.
      • postgres: A geodatabase will be created in an Amazon RDS for PostgreSQL instance. The database will be registered as the ArcGIS Server site’s managed database.
    • DBAllocatedStorage: Define the size of the RDS storage space. This value is ignored if DBEngine parameter value is set to "none".
    • DBInstanceClass: The AWS RDS instance class. This value is ignored if DBEngine parameter value is set to "none".
    • DeploymentBucket: The S3 bucket you created, which has Esri authorization files uploaded to it.
    • DriveSizeRoot: The size of the root drive. It's the C: drive on Windows and the root drive on Ubuntu Linux.
    • ELBName: The name of an existing ELB, or specify 'NEW_ELB' to create and use a new one.
    • FSInstanceType: The instance type for the file server machine. This is machine 1 in the graphic. This machine hosts the server directories for the GIS Server site (and the ArcGIS Server configuration store if you picked CloudStore for the StoreType parameter). This machine will be configured with the AWS Auto Recovery feature. If the instance crashes, AWS can restore it in the same Availability Zone to the stage before it crashed. Only certain instance types are allowed.
    • KeyName: The EC2 Key Pair to allow Remote Desktop access to the instances.
    • PostInstallationScript: A ZIP archive file with custom post installation script. This zip file must be uploaded to DeploymentBucket. If there's a deploy.bat or deploy.sh at the root level inside this zip file, deploy.bat will be executed as administrator on Windows as the last step to configure the machine. On Ubuntu, deploy.sh will be executed as superuser.
    • RunAsUserPassword: This is the password for the account used to run the ArcGIS Server service. (Windows only)
    • ServerLicenseFile: The authorization file for ArcGIS Server that you obtained from Esri. It must be in the S3 deployment bucket.
    • SiteAdmin: The user name for the ArcGIS Server primary site administrator account.
    • SiteAdminPassword: Password for SiteAdmin.
    • SSLCertificateARN: Amazon Resource Name (ARN) of the certificate in AWS Certificate Manager. for example: "arn:aws:acm:us-east-1:123456789012:certificate/12345678-1234-1234-1234-123456789012". This certificate will be used to configure HTTPS listener in the ELB created by this stack.
    • StoreType:
      • FileSystem: The ArcGIS Server configuration store will be on the file system machine.
      • CloudStore: The ArcGIS Server configuration store will be in AWS DynamoDB and an S3 bucket created by this stack.
    • Subnet1: The id of the subnet you want this deployment to be deployed to.
    • Subnet2: The id of another subnet you want this deployment to be deployed to.
    • VPCId: The id of the VPC where you want to deploy to. The Subnets must belong to this VPC.

  • Map your domain name in DNS to the ELB created with this stack.
    After the stack is created successfully, the output of this stack has the URL to ArcGIS Server Manager and the REST page containing the ELB URL. You need to map your domain to the ELB. For example, map servergis.domain.com to arcgis-serverhadynamodb-2116864963.us-east-1.elb.amazonaws.com through CNAME mapping. Your GIS Server or GeoAnalytics Server site will be https://your_domain_name/server, for example, https://servergis.domain.com/server.

    • Notes:

    In this template if you picked "CloudStore" for the "StoreType" parameter, the DynomoDB's provision capacity is set to:
    • Read Capacity units to 250 tables
    • Write Capacity units to 25 tables
    The estimated cost is about $36/month. Esri testing indicates this is good for publishing approximately 500 services. You can edit this setting in the AWS Management console to decrease the units to lower the cost, or increase the units for more services. Some ArcGIS Server functionalities, such as publishing, could fail if you don't have enough capacity.

Steps to complete the deployment

If you created a stand-alone GIS Server site, sign in to ArcGIS Server Manager and configure users and security for the site.

If you created a GeoAnalytics Server site, or the ArcGIS Server site you deployed is intended to be used as a federated server with your ArcGIS Enterprise deployment, you must manually federate. Note that ArcGIS GeoAnalytics Server sites can only be used as federated servers, not as stand-alone ArcGIS Server sites.

  • Open "All traffic" in the security groups between GIS Server stack and base Enterprise stack. Add "All traffic" in each security group to the other security group.
  • As a portal administrator, sign in to the Portal for ArcGIS organization you created with your base ArcGIS Enterprise deployment. Follow steps in the Portal for ArcGIS administrator guide that are appropriate for the type of ArcGIS Server site you created. You can use the ArcGIS Server site URL for both Server URL and Server Admin URL during federation, e.g. https://gisserver.domain.com/server. The following links go to instructions for Windows operating systems; use the drop-down list at the top of each topic to change to Linux instructions