Before launching an AMI into an Amazon VPC, you must ensure that the VPC has access to an Internet Gateway. If your VPC does not have access to an Internet Gateway, you can use the Amazon management console to create an Internet Gateway and associate it with your VPC. Please note: if you are using EC2-Classic networking, you do not need to provide an Internet Gateway.For detailed information about creating and using an Internet Gateway, see the Amazon documentation at:To launch an Amazon EC2 instance that contains a running copy of the Ark console and the Ark console's backing database, connect to your Amazon AWS Marketplace Account and locate the AMI that contains the Ark console. Navigate through the introductory page for the AMI, selecting AWS service options that are appropriate to your application, and agreeing to the Terms and Conditions. When you agree to the Terms and Conditions, Amazon will process the subscription.After you subscribe, Amazon will forward an email to the address associated with your user account that includes launch instructions for the AMI. For additional information about launching software from the AWS Marketplace, please refer to the online resources for Amazon Marketplace:Use the Amazon launch wizard to launch your instance, noting the requirements that follow on Step 3 and Step 6 of the wizard.When configuring your instance, you should include the following selections on the Step 3: Configure Instance Details dialog of the Amazon launch wizard (see Figure 3.1):
• Use the Auto-assign Public IP drop-down to specify Enable to automatically assign an IP address to the new instance.
• Use the Advanced Details section to provide the text of the script that will start the Ark console setup or recovery dialog.#!/bin/sh
rm -f /usr/share/tomcat/startup-password.txt
echo "console_password" > /usr/share/tomcat/startup-password.txt
chown tomcat:tomcat /usr/share/tomcat/startup-password.txt
chmod 600 /usr/share/tomcat/startup-password.txtWhen the user first connects to the AWS Ark console, they will be required to provide the console_password provided in the script.Continue through the launch wizard; please note that when configuring your security group, the group must allow communication between the nodes of the cluster.
The CIDR addresses specified in the rules for SSH, HTTP, HTTPS, and 5432 can be customized to restrict access to a limited set of users. The CIDR addresses specified for port 6666 and ports 7800 through 7999 must specify a value of 0.0.0.0/0.The Custom TCP rule that opens ports 7800 through 7999 provides enough ports for 200 cluster connections; the upper limit of the port range can be extended if more than 200 clusters are required.