AWS CloudFormation is a service that helps you define architectures on Amazon Web Services. You can use CloudFormation templates provided by Esri and the following steps to create the deployments described in AWS CloudFormation and ArcGIS.
Starting with 10.5.1, if you have additional scripts you defined that you want to run as part of this CloudFormation deployment, perform step 2 and its substeps. For example, you could write your own script to add users or load data. If you do not have additional scripts to run, skip step 2.
- Before using an AMI for the first time, accept terms on AWS Marketplace.
- If you wrote a script that you want to run at the end of the deployment, follow these steps to include the script:
- Create an archive that contains your script.
- Place the archive in an Amazon Simple Storage Service (S3) bucket accessed by the same account you will use when running the CloudFormation templates provided by Esri.
When you get to step 7, update the PostInstallationScript parameter with this S3 bucket's information.
- Go to the S3 bucket where Esri stores sample CloudFormation templates.
- Choose the template you want, click ReadMe, and read the instructions for that template.
- Click View to download the template. Open the template and examine it before you launch the stack to be sure you have all the information you need to provide for the properties in the template's Parameters object.
- Once you meet all the prerequisites and have the information you need to provide for the template, click Launch Stack to run the template.
- Sign in to the AWS Management Console using your Amazon account.
The CloudFormation Stack page opens.
- Change the default Stack Name if you want and click Continue.
- Set the properties for your stack as needed and click Continue.
- Add tags to easily identify your instance, such as Key = Name and Value = MyCloudFormation, and click Continue.
- Examine all your parameter values. Click Continue when you are ready to create your stack.
The stack is launched. For most deployments, configuration is complete. You can access your site using the URL in the output tag.
If you add a tile cache data store to your deployment and your hosting server machines have Windows Server 2016 operating systems, 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 on Windows Server 2016.