The Amazon Web Services (AWS) Management Console is a web application that you can use to administer the Amazon Elastic Compute Cloud (EC2) instances and other resources that you have created on AWS. Typically, you use ArcGIS Enterprise on Amazon Web Services deployment tools to create deployments and then you use the AWS Management Console to prepare resources and accomplish advanced administrative tasks such as adjusting security group rules or attaching more storage to your instances.
Tip:
For information on which browser version to use with AWS Management Console, see the AWS documentation.
Advanced users who require more specialized configurations can create deployments using the AWS Management Console. In many cases, you can create EC2 instances using an Esri ArcGIS Enterprise Amazon Machine Image (AMI), which includes ArcGIS Enterprise software. Or, if you require a different operating system, for example, you may create EC2 instances from a different AMI and install and configure ArcGIS Enterprise on these instances.
Creating a deployment using the AWS Management Console is a multistep process that requires architectural planning and an understanding of Amazon Web Services.
The following is a summary example of a basic workflow to deploy ArcGIS Enterprise using the AWS Management Console and an Esri AMI. The approach you take may vary based on your deployment needs.
- Prepare to deploy on AWS.
- Create an Amazon account and make sure it includes EC2 access.
- The first time you use a new Amazon Machine Image, accept AWS Marketplace terms.
- Create Amazon security groups for ArcGIS, configuring at least one security group that allows remote access.
- For ArcGIS Enterprise deployments on a single EC2 instance, configure an Amazon Elastic IP address and map a fully qualified domain name to the IP address. Create the Elastic IP address in the same Amazon region as your deployment.
- For deployments that include multiple machines (multiple EC2 instances), create Elastic Load Balancers (Classic) in the same Amazon region as your deployment. Create CNAME DNS mappings for each load balancer.
- Launch an AWS instance to create a base ArcGIS Enterprise deployment or a highly available portal and connect to the instance to license software.
- Use an Esri AMI to launch an EC2 instance.
- Connect to your new instance (or instances) using Microsoft Windows Remote Desktop, SSH and a terminal emulator from Windows, or an SSH connection from Linux and license Portal for ArcGIS and the hosting server (an ArcGIS GIS Server site).
- Create the ArcGIS Server roles you require and federate them with the portal.
- Launch an EC2 instance for each federated server site you require. Use the same Esri AMI you used to create the portal.
- Federate each site with the portal.
- If your users will publish services that reference registered data, set up a place to store your data on AWS.
- Choose where to store your data on the cloud.
- Optionally configure additional EBS volumes for local data storage.
- Optionally create enterprise geodatabases in Amazon Relational Database Service (RDS) for PostgreSQL or Amazon RDS for SQL Server to store service data.
- Register data sources with your stand-alone and federated ArcGIS Server sites.
- Move your data to AWS.
- Choose a data transfer method and move your data.
- Give the ArcGIS Server account permissions to access your data.
- Customize security on your AWS instances.
- Change the administrator password for your AWS instance (Windows only).
- Configure ArcGIS Server security.
- Optionally make other security adjustments to the AWS instance such as firewall adjustments, SSL configuration, and so on.
- Configure the ArcGIS Enterprise portal to meet your organization's needs.
- Configure portal security.
- Add or invite members to the portal, configure member roles, and assign app licenses.
- Configure categories for portal content.
- Prepare your production environment.
- Alter your AWS security group rules to disable or restrict remote access to the production AWS instance. This increases security on the production instance.
- Create a custom AMI containing the services and apps on your site.
- Iterate with larger instance types, if necessary, to arrive at the instance type with the appropriate amount of power for your deployment.
- If needed, use your custom AMI to launch or terminate instances in ArcGIS Server sites in response to demand. This can be done programmatically using the Amazon Auto Scaling API, or you can do it manually. Multiple machines can be connected by an Amazon Elastic Load Balancer.
This help system describes many of the steps summarized above. Another helpful resource is the Amazon Web Services documentation, which explains how to use the AWS Management Console and how to program with Amazon Web Services.