Highly Available ArcGIS Image Server.

Provision a highly available ArcGIS Image Server site.

This template will provision an ArcGIS Image Server site. Optionally, you can have GeoDatabase created against AWS SQL Server RDS or Postgresql RDS. The GeoDatabase will be registered as Managered Enterprise GeoDatabase to the ArcGIS Server site. This template will set up an architecure as shown in the graphic.

HTML5 Icon

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. This bucket is called DeploymentBucket in the Parameters in the sample template.You will specify this name in the Parameters object when you launch the stack.
    • Upload your ArcGIS Image Server license file to the DeploymentBucket.

  • Request a certificate or import your SSL certificate to your AWS console Certificate Manager. Check AWS doc for more information.

  • Run the template to create CloudFormation stack.
    Click Launch Stack for this template. There are a number of properties in the Parameters object 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 primary machine in the site (machine 2 in the graphic) is the first EC2 instance created for the site, and it 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. The rest of the EC2 instances (machine 3, machine 4, and machine N...... in the graphic) will be created in an Auto Scaling group. These machines will join the ArcGIS Server site through accessing the ArcGIS Server config-store. Only certain instance types are allowed.
    • DBEngine:
      • none: No RDS GeoDatabase will be created.
      • sqlserver-se: GeoDatabase will be created with AWS SQL Server RDS, standard version.
      • postgres: Geodatabase will be created with AWS Postgresql RDS.
    • DBAllocatedStorage: Define the size of the RDS storage space. This value will be ignored if you picked "none" for DBEngine variable.
    • DBInstanceClass: The AWS RDS instance class. This value will be ignored if you picked "none" for DBEngine variable.
    • DeploymentBucket: The S3 bucket you created, which has Esri authorization files uploaded to it.
    • DriveSizeData: The size of the data drive. It's the D: drive on Windows and the /gisdata drive on Ubuntu Linux.
    • DriveSizeRoot: The size of the root drive. It's the C: drive on Windows and the root drive on Ubuntu Linux.
    • FSInstanceType: The instance type for the file server machine. This is machine 3 in the graphic. This machine hosts the server directories for the GIS Server site (and , possibly ArcGIS Server config-store if you picked "CloudStore" for "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.
    • RunAsUserPassword : This is the password for the account used to run the ArcGIS Server service. (Windows only)
    • SecondaryInstances: 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 minus 1. They are machine 2, machine 3, and machine N...... in the graphic.
    • ServerLicenseFile: The authorization file for ArcGIS Server that you obtained from Esri. It must be in the S3 deployment bucket.
    • SiteAdmin: ArcGIS Server primary site administrator account.
    • SiteAdminPassword: Password for SiteAdmin.
    • SSLCertificateARN: Amazon Resource Name (ARN) of the certificate in your AWS certificate manager. for example: "arn:aws:acm:us-east-1:123456789012:certificate/12345678-1234-1234-1234-123456789012". This certificate will be deployed to the ELB created in this stack.
    • StoreType:
      • FileSystem: Portal for ArcGIS content store and ArcGIS Server config-store will be on the file system in the same machine.
      • CloudStore: ArcGIS Server config-store will be in AWS DynamoDB and a 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 you entered above must belong to this VPC.

  • Map your domain name 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, e.g. servergis.domain.com to arcgis-serverhadynamodb-2116864963.us-east-1.elb.amazonaws.com through CNAME mapping. Your Image Server site will be https://your_domain_name/arcgis, for example, https://servergis.domain.com/arcgis. The certificate provided in the parameter "SSLCertificateARN" has been deployed to this ELB.

    • Notes:

    In this template if you picked "CloudStore" for the "StoreType" variable, 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.

You must manually federate your Image Server stack to your base ArcGIS Enterprise. Note that ArcGIS Image 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