Manually Installing CTERA Portal
  
Manually Installing CTERA Portal
For instructions on how to deploy the CTERA Main Portal Server using an automated set-up, see Installing the CTERA Main Portal Server with CloudFormation.
Requirements
CTERA Portal must be installed on an EC2 instance that meets the following requirements:
m4.xlarge and 100GB EBS storage volume.
For the main database server and catalog nodes serving a large number of clients, a provisioned IOPS volume with minimum 1000 IOPS. CTERA recommends at least 2000 IOPS for a production environment.
The allocated EBS size should be 2 percent of the total amount of storage (raw) that you will be storing on Amazon S3.
Preview servers require at least 16GB of RAM, 4 CPU cores, and 60GB of magnetic drive.
The EBS volume attached to the CTERA instances running the CTERA database (applicable for the main database or catalog node) must yield a minimum of 700 TPS (transactions per second). To test the TPS on your installation, contact CTERA support at http://support.ctera.com.
The ports listed in Port Requirements are open.
Note: All resources allocated to a server must be dedicated to that server and not shared with other servers.
Installation Workflow
Use the following workflow to install CTERA Portal on each server.
1 Setting up the Amazon EC2 Instance.
2 Logging In to the CTERA Portal Server.
3 Configuring Network Settings.
4 Initializing the Storage Pool.
5 (Optional) Associate your CTERA Portal instance with an Elastic IP Address. See Obtaining an Elastic IP Address for the CTERA Portal Instance.
6 For the first server you install, follow all of the steps in Configuring the CTERA Portal Master Server.
7 For any additional servers beside the master server, configure the server as an additional server as described in Installing Additional CTERA Portal Servers.