You can use ArcGIS Enterprise Amazon Machine Images (AMIs) to launch several different architectures on Amazon Web Services (AWS). Esri provides a tool, ArcGIS Enterprise Cloud Builder Command Line Interface for Amazon Web Services, you can use to prepare and create deployments from the ArcGIS Enterprise AMIs. Esri also provides sample AWS CloudFormation templates you can use to launch most supported architectures.
You can also use the AMIs and the AWS Management Console to deploy ArcGIS on AWS.
ArcGIS Enterprise Cloud Builder CLI for AWS
ArcGIS Enterprise Cloud Builder Command Line Interface for Amazon Web Services 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 your ArcGIS authorization files and your SSL certificates to the bucket. The ArcGIS Enterprise Cloud Builder CLI for AWS also uses information you provide in JSON files to create the following architectures:
- A base ArcGIS Enterprise deployment
- A base ArcGIS Enterprise deployment plus a federated ArcGIS GeoAnalytics Server, raster analysis server, and image hosting server
- Stand-alone ArcGIS Server sites (that can be federated with your ArcGIS Enterprise deployment if needed)
AWS CloudFormation templates
Esri provides sample AWS CloudFormation templates to deploy the architectures described in AWS CloudFormation and ArcGIS.
You can use these templates with Python or Windows PowerShell Tools to automate deployments of these same architectures.
AWS tools and ArcGIS deployments
You can build the same architectures manually on AWS using the AWS Management Console as you can when deploying on-premises; however, you need to be proficient in configuring the components of ArcGIS Enterprise and proficient in AWS. This section includes tips for manual deployments and links to related topics.
When you build your site manually using the AWS Management Console, you can use the Esri AMIs or you can use a custom AMI that you have derived from one of the Esri AMIs to create instances that include ArcGIS Server, Portal for ArcGIS, and ArcGIS Data Store. 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 Server site, you must launch an Elastic Load Balancer and add the machines to it.
- Enterprise geodatabases. If you want to store data in an enterprise geodatabase on AWS, you must create the database 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 Server site or create a geodatabase on AWS, assign the instance an Elastic IP address.
ArcGIS Server Cloud Builder on Amazon Web Services
ArcGIS 10.6.1 is the final release of ArcGIS Server Cloud Builder on Amazon Web Services. Use ArcGIS Enterprise Cloud Builder Command Line Interface for Amazon Web Services to deploy ArcGIS Server sites instead.
ArcGIS Server Cloud Builder on Amazon Web Services allows you to build a stand-alone ArcGIS Server site. The site can contain a single ArcGIS Server machine, or you can create a complex site with many ArcGIS Server machines. It also allows you to include an enterprise geodatabase and determine where the enterprise geodatabase is placed.
Considerations for ArcGIS deployments on AWS
Note the following information for specific architectures on AWS:
ArcGIS Enterprise that use tile cache data stores
If your ArcGIS Enterprise will include a tile cache data store and your hosting server machines use Windows operating systems, the following additional configuration is required to allow your portal members to publish hosted scene layers:
- You must make a remote desktop connection to each machine in the hosting server site and enable SSL 3.0 in the Internet options before publishing hosted scene layers. See technical article 000016013 for instructions on enabling SSL 3.0.
- You must establish trust between the tile cache data store and the hosting server. Follow the steps outlined in technical article 000012516 for instructions.