Skip To Content

Deployment options on Amazon Web Services

You can launch several different ArcGIS Enterprise architectures on Amazon Web Services (AWS). Esri provides the following deployment tools to help you prepare and create ArcGIS Enterprise deployments on AWS:

Alternatively, you can use an Esri ArcGIS Enterprise Amazon Machine Image (AMI) and AWS Management Console to deploy ArcGIS on AWS.

ArcGIS Enterprise Cloud Builder for Amazon Web Services

ArcGIS Enterprise Cloud Builder for Amazon Web Services includes a graphical user interface application and ArcGIS Enterprise Cloud Builder Command Line Interface for Amazon Web Services.

The command utility takes information you provide in JSON files and the Esri CloudFormation templates to automate preparatory steps such as creating a network stack and Amazon Simple Storage Service (S3) bucket and uploading ArcGIS authorization files and SSL certificates to the bucket. ArcGIS Enterprise Cloud Builder CLI for AWS also uses information you provide in JSON files to create different ArcGIS architectures.

The ArcGIS Enterprise Cloud Builder for Amazon Web Services app guides you through options to provision resources and create ArcGIS deployments. It takes the information you provide and populates the same JSON files as ArcGIS Enterprise Cloud Builder CLI for AWS. Both the app and the command utility create the following deployment types:

  • A base ArcGIS Enterprise deployment
  • A base ArcGIS Enterprise deployment plus federated ArcGIS Server roles such as ArcGIS GIS Server, ArcGIS GeoEvent Server, ArcGIS GeoAnalytics Server, ArcGIS Image Server, a raster analysis server, image hosting servers, ArcGIS Notebook Server, and ArcGIS Mission Server.
  • Stand-alone ArcGIS Server sites (that can be federated with your ArcGIS Enterprise deployment if needed), which can include registered databases

AWS CloudFormation templates

Esri provides sample AWS CloudFormation templates to deploy the architectures described in AWS CloudFormation and ArcGIS.

You can use these templates in the AWS Management Console or use Python or Windows PowerShell tools to automate deployments of these same architectures.

AWS tools and ArcGIS Enterprise deployments

You can build the same architectures on AWS as you can when deploying on-premises using the AWS Management Console. To use this option, however, you need to be proficient in configuring the components of ArcGIS Enterprise and proficient in AWS.

When you build your site using the AWS Management Console, you can use an Esri AMI, or you can use a custom AMI. In either case, you are responsible for creating supporting components such as the following:

  • An Amazon Elastic Load Balancer—If your deployment includes a multiple-machine ArcGIS Enterprise portal or ArcGIS Server site, you must launch an Elastic Load Balancer and add the machines to it.
  • Enterprise geodatabases (optional)—If you want to store data in an enterprise geodatabase on AWS, you must create the database or database service on AWS, create the geodatabase in it, and register it with your ArcGIS Server site.
  • Amazon Elastic IP addresses—If you create a single-machine ArcGIS Enterprise portal or connect to a database on AWS, assign the instance an Elastic IP address.

Data sources on AWS

For best performance, the data used by web services that run on ArcGIS Server sites on AWS should also be stored on AWS and in the same region. See Strategies for data transfer to Amazon Web Services.

Considerations for ArcGIS Server sites used with ArcGIS API for JavaScript applications on Microsoft Windows

If you'll be hosting ArcGIS API for JavaScript applications on a Windows instance to use with an ArcGIS Server site you created directly from an Esri ArcGIS Enterprise AMI, you must configure ArcGIS Web Adaptor with the ArcGIS Server site. The Esri AMIs include ArcGIS Web Adaptor, so you only need to sign in to your instance and configure the web adaptor. See Strategies for web app deployment on AWS for more information and instructions.