IN THIS ARTICLE
Outlines how to configure a single node instance of QF2 in AWS
- Amazon Web Services (AWS) account
- AWS account number and target region
- Permission to launch EC2 instances
- Account limits large enough for 5TB of EBS storage across GP2 and ST1
- Amazon Machine Image (AMI) of Qumulo Core for AWS version 2.7.6 or greater
NOTE: Modifying the type or size of the EBS volumes in the QF2 AMI will render the software not functional. Please use the AMI volume layout provided in the original image.
Running QF2 in AWS as a single node cluster provides you with 5TB of raw storage so that you can leverage the full power of the Qumulo filesystem. As you begin using QF2 in AWS, please consider the following:
- A stand alone single-node system cannot be expanded. Adding nodes is disabled in the UI and API.
- Running QF2 in stand-alone configuration is recommended for evaluation and for workflows where high availability, data durability and performance scalability is not required. It is not recommended to use standalone mode for production data without a replication or backup strategy.
- Customers should configure a 4+ node cluster to enable scaling and data protection.
Launch the AMI
- Sign in to the AWS account and select EC2
- Select the region using the same details provided to Qumulo in the AMI request form
- From the EC2 dashboard, click on AMIs in the AWS sidebar
- Select Private Images from the AMI source drop down
- Check the box to choose the AMI provided by Qumulo on the Resource Group page
- Click Launch to provision the image
- Select an m4.2xlarge or m4.16xlarge instance type from the list
- Click Next: Configure Instance Details
- Navigate to Configure Security Group leaving the default settings in place for Configure Instance, Add Storage, and Add Tags
Configure the Security Group
- Ensure the security group, existing or new, associated with the AMI includes the following open ports:
- SSH: Port 22
- HTTPS: Port 443
- NFS: Port 2049
- Custom TCP for NFS port mapper: Port 111
- Custom TCP for GUI: Port 8000
- Custom TCP for QF2 replication: Port 3712
- Click the Review and Launch button
- Review the settings on the Instance Launch page and make changes in prior steps as needed
- Click Launch
Launch the Instance
- Select an existing key pair or create and download a new pair of keys to SSH into the instance
- Click Launch Instances
- On the Launch Status page, click the View Instances button
- In the QF2 instance listing, the Status Checks column will display Initializing
NOTE: Initialization times can vary and may take up to 10 minutes to complete.
- Once the Status Checks column displays 2/2 checks, the instance is running and ready for cluster configuration
Prevent Accidental Termination
Before configuration, follow the steps below to prevent accidental termination of the nodes in your cloud cluster.
- Right-click on each EC2 instance (node), select Instance Settings and click Change Termination Protection
- Click Yes, Enable in the Enable Termination Protection dialog box
Configure your QF2 Cluster
- In a browser window, enter https:// followed by the Public IPv4 address included in the Description tab of the instance listing
Note: Qumulo is configured with a self-signed certificate by default which may cause your browser to display a warning. This is normal behavior. A custom certificate can be installed at a later time to avoid the warning if needed.
- At the warning, select ADVANCED and click Proceed to continue
- Agree to the the End User Agreement and click Submit
- Enter a custom Cluster Name or use the default name of qumulo
- Create a new password for your admin account
- Retype the password to confirm
- Click Create Cluster to form your cluster
- Select Yes, Create Cluster when prompted
- Complete cluster configuration by confirming the settings for monitoring, networking, and time zone preferences in the right-hand panel of the dashboard
You should now be able to successfully configure a single-node instance of QF2 in AWS
Like what you see? Share this article with your network!