Installing the Nasuni Filer on the EC2 Platform. Version 7.9 July 2017 Last modified: July 10, Nasuni Corporation All Rights Reserved

Transcription

1 Installing the Nasuni Filer on the EC2 Platform Version 7.9 July 2017 Last modified: July 10, Nasuni Corporation All Rights Reserved

2 Document Information Installing the Nasuni Filer on the EC2 Platform Version 7.9 July 2017 Copyright Copyright by Nasuni Corporation. All rights reserved. Information in this document is subject to change without notice and does not represent a commitment on the part of Nasuni. The software described in this document is furnished under a license agreement. The software may be used only in accordance with the terms of the license agreement. It is against the law to copy the software on any medium. No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose without the express written permission of Nasuni Corporation. Notice Although Nasuni Corporation has attempted to ensure the accuracy of the content of this manual, it is possible that this document might contain technical inaccuracies, and typographical or other errors. Nasuni assumes no liability for any error in this publication, and for damages, whether direct, indirect, incidental, consequential or otherwise, that might result from such error, including, but not limited to loss of data or profits. Nasuni provides this publication as is without warranty of any kind, either express or implied, including, but not limited to implied warranties of merchantability or fitness for a particular purpose. Trademarks NASUNI, UNIFS, and the ovals logo are Nasuni trademarks and service marks. All other names, brands and products are the property of their respective owners. Contacting Nasuni Corporation Nasuni Corporation One Marina Park Drive Boston, MA Telephone: Sales: info@nasuni.com Technical Support Telephone: NASUNI ( ) support@nasuni.com Technical Support is available 24/7/365 for full production clients.

3 Contents Audience iv What s in this Book iv Text Conventions v Product Documentation vi Electronic Publications vi Recent Changes to this Document viii Chapter 1: Installing on the Amazon EC2 Platform Overview Nasuni NAS Nasuni Filer Nasuni Management Console Creating a Virtual Private Cloud (VPC) Launching the AMI Configuring the Nasuni Filer on EC Configuring the Nasuni Management Console on EC Performance Chapter 2: Controlling the EC2 Instance Overview Shutting down the EC2 instance Starting the EC2 Instance Chapter 3: Uninstalling the EC2 Instance Overview Uninstalling the Nasuni Filer or Nasuni Management Console Installing the Nasuni Filer on the EC2 Platform iii

4 Preface Audience This guide is intended for the IT administrator or person responsible for installing the Nasuni Filer or the Nasuni Management Console on the Amazon EC2 platform. What s in this Book This guide contains the following chapters: Chapter 1, Installing on the Amazon EC2 Platform, on page 7 explains how to install the Nasuni Filer or the Nasuni Management Console on the Amazon EC2 platform. Chapter 2, Controlling the EC2 Instance, on page 16 explains how to control the Nasuni Filer or the Nasuni Management Console from the Amazon EC2 platform. Chapter 3, Uninstalling the EC2 Instance, on page 18 explains how to remove the Nasuni Filer or the Nasuni Management Console from your system if you are upgrading or replacing your hardware. Installing the Nasuni Filer on the EC2 Platform iv

5 What s in this Book Text Conventions The following text conventions are used in this document: Convention Description 1. Number Used to indicate a step in a task. Bullet Bold Italics Underline Monospace Used for items in a list without any particular order. Used to give emphasis to a word. Also used for named graphical elements. Used to represent options or parameters. Used for hyperlinks, such as links to Web sites. Used to indicate pathnames, filenames, folder names, typed information, and code. Installing the Nasuni Filer on the EC2 Platform v

6 Product Documentation Electronic Publications Extensive documentation is available for all aspects of installing, configuring, and operating the Nasuni Filer. The latest version of each of the following documents is available in PDF format at Hardware Getting Started Guide: For setting up the Nasuni Filer on the Nasuni Filer hardware appliance. To download this guide for the NF-60, visit: To download this guide for the NF-200, visit: To download this guide for the NF-400, visit: To download this guide for the NF-440, visit: To download this guide for the NF-600, visit: Installing the Nasuni Filer on Virtual Platforms: For installing the Nasuni Filer on a virtual machine within a corporate network. To download this guide, visit: Installing the Nasuni Filer on the Azure Platform: For installing the Nasuni Filer on the Microsoft Azure cloud virtual machine. To download this guide, visit: Installing the Nasuni Filer on the EC2 Platform: For installing the Nasuni Filer on the Amazon EC2 cloud virtual machine. To download this guide, visit: Installing the Nasuni Filer on the EC2 Platform vi

7 Product Documentation Electronic Publications Initial Configuration Guide: For configuring and deploying the Nasuni Filer after the initial installation on the hardware appliance or virtual machine. To download this guide, visit: Administration Guide: For managing unified storage using the Nasuni Filer. To download this guide, visit: Nasuni Management Console Guide: For managing multiple Nasuni Filers. To download this guide, visit: Nasuni Management Console Quick Start Guide: To quickly get started using the Nasuni Management Console to manage multiple Nasuni Filers. To download this guide, visit: Using Multiple Protocols: Discusses scenarios requiring particular access to data, and how different combinations of protocols can help provide the access that clients need. To download this guide, visit: Third-Party Licensing Guide: Listing of third-party software used in the Nasuni Filer. To download this guide, visit: Installing the Nasuni Filer on the EC2 Platform vii

8 Recent Changes to this Document Recent changes to this document include the following: Topic Section or Step Page Initial, Recommended, and Minimum Memory Initial, Recommended, and Minimum Memory page 17 Installing the Nasuni Filer on the EC2 Platform viii

9 Chapter 1: Installing on the Amazon EC2 Platform Overview This chapter explains the recommended procedure for the initial installation of the Nasuni Filer or the Nasuni Management Console on the Amazon EC2 platform. For additional information on the initial configuration of the Nasuni Filer, see the Nasuni Filer Initial Configuration Guide. For additional information on the initial configuration of the Nasuni Management Console, see the Nasuni Management Console Guide. Note: The vendor changes their interfaces occasionally with little notice to the users. The exact screens and text on these platforms might change at any time. Nasuni NAS Nasuni delivers an advanced storage solution using a cloud infrastructure. The core technology is a next-generation storage controller the Nasuni Filer that offers the security and performance of traditional storage, while adding unlimited scalability, automatic offsite protection, and global multi-site access to files. The Nasuni system is managed through a single, small-footprint point of control within the enterprise s data center. The Nasuni Filer is an on-premises storage device supporting NFS, CIFS, FTP/SFTP, iscsi, and HTTP/ REST protocols. The Nasuni Filer is fully integrated with Active Directory, LDAP, Distributed File System (DFS), and Windows Previous Versions. It includes a high-performance cache and takes periodic snapshots that enable file-level restores. Its reach and capacity far exceed those of a traditional controller, however, because it does not rely only on memory and local disk to manage its data: it has the entire capacity of the cloud at its disposal. All data is deduplicated, compressed, and encrypted before storage. Several choices are available for the back-end cloud storage component, including the following: Nasuni s integrated service, which includes a Nasuni-managed Microsoft Azure account. Your own public cloud service from Microsoft Azure Blob Storage or Amazon AWS S3. Installing the Nasuni Filer on the EC2 Platform 7

10 Installing on the Amazon EC2 Platform Nasuni Filer Private cloud products, including Cleversafe and EMC ViPR/ECS and Atmos. The choices for the back-end cloud storage component are part of each customer license. Each volume has only one back-end cloud storage component. Multi-site access enables organizations with several locations to work on a single set of shared data. Nasuni s architecture allows multiple storage controllers to have live access to the same volume of data. Organizations benefit by having a simple, safe, and secure way to share data across any number of sites. Nasuni s multi-site access enables capabilities that include: Secure data distribution to remote office/branch office (ROBO). Remote offices forwarding data to a central point. Two-way synchronized read-write. Multi-site access does away with cumbersome replication schemes and slow WAN optimizers. Nasuni Filer Nasuni s NAS is delivered through the Nasuni Filer, a storage controller that runs in your data center and provides primary storage with built-in backup, offsite protection, and multi-site access. With your Nasuni Filer, you manage your volumes and performance using the Web-based Nasuni Filer user interface. The Nasuni Filer is available as a virtual appliance, as a hardware appliance, and as a Microsoft Azure and Amazon EC2 virtual appliance. Nasuni Management Console The Nasuni Management Console enables you to monitor and manage many Nasuni Filers from one central appliance. Using the Nasuni Management Console, you can view the status of all of your managed Nasuni Filers, as well as configure their settings. Using the Nasuni Management Console, you can ensure consistent settings on all your Nasuni Filers. Note: If a Nasuni Filer loses internet connectivity with the Nasuni Management Console, the Nasuni Filer can still leave the Nasuni Management Console. Installing the Nasuni Filer on the EC2 Platform 8

11 Installing on the Amazon EC2 Platform Creating a Virtual Private Cloud (VPC) Creating a Virtual Private Cloud (VPC) Before launching the Amazon Machine Image (AMI) for the Nasuni Filer, you must create a Virtual Private Cloud (VPC). If you already have a VPC, you can use the existing VPC. Using a VPC gives you more control over networking features, such as assigning static addresses and enabling Active Directory or LDAP in the cloud. Important: You must create and maintain your own AWS account. Nasuni does not have access to your AWS account. To gain access to the Nasuni AMIs, contact Nasuni Technical Support with your AWS account number. To create an EC2 account, visit aws.amazon.com/ec2/. Important: This procedure assumes that you have already configured Active Directory, LDAP, and any domain controllers in the cloud. To create a VPC on the AWS web site: 1. Launch your Web browser. 2. Go to the Amazon Web Services VPC console at The VPC Dashboard appears. 3. Click Start VPC Wizard. The Create an Amazon Virtual Private Cloud screen appears. 4. Select the type of VPC that suits your networking needs best from the following types of VPC: VPC with a Single Public Subnet Only. VPC with Public and Private Subnets. VPC with Public and Private Subnets and Hardware VPN Access. VPC with a Private Subnet Only and Hardware VPN Access. 5. Click Continue. Depending on the type of VPC you selected in step 4, different screens appear for the VPC Wizard. Complete each screen with settings appropriate for your networking needs. Important: Whichever type of VPC you selected in step 4, ensure that you only provide a single network interface to the Nasuni Filer, and ensure that you assign an IP address to the Nasuni Filer. 6. After completing all screens of the VPC Wizard, click Create VPC. A message appears notifying you that the VPC is created. 7. On the VPC Dashboard, click DHCP Options Sets in the left-hand menu. A list of DHCP Options Sets appears. 8. If a suitable DHCP Options Set already exists, skip to step 9. Otherwise, click Create DHCP Options Set. The Create DHCP Options Set dialog box appears. Enter the appropriate settings for the new DHCP Options Set, then click Yes, Create. The new DHCP Options Set is created and appears in the list. 9. On the VPC Dashboard, click Your VPCs in the left-hand menu. A list of VPCs appears. 10. Right-click the VPC you are going to use, then select Change DHCP Options Set from the drop-down menu. The Change DHCP Options Set dialog box appears. Installing the Nasuni Filer on the EC2 Platform 9

12 Installing on the Amazon EC2 Platform Creating a Virtual Private Cloud (VPC) 11. From the DHCP Options Set drop-down list, select the DHCP Options Set to use with the VPC, then click Yes, Change. The selected DHCP Options Set is associated with the VPC. The VPC has now been created and the DHCP Options Set has been associated with it. Installing the Nasuni Filer on the EC2 Platform 10

13 Installing on the Amazon EC2 Platform Launching the AMI Launching the AMI Installing the Nasuni Filer or Nasuni Management Console requires the corresponding Amazon Machine Image (AMI), which is available on the Amazon Web Services (AWS) web site. Important: You must create and maintain your own AWS account. Nasuni does not have access to your AWS account. To gain access to the Nasuni AMIs, contact Nasuni Technical Support with your AWS account number. To create an EC2 account, visit aws.amazon.com/ec2/. Important: To access Active Directory-enabled volumes, the Nasuni Filer must be connected to an Active Directory server in the same Active Directory forest. This requires part of your Active Directory infrastructure to also be running on the EC2 platform. Similarly, to access LDAP-enabled volumes, the Nasuni Filer must be able to access LDAP and Kerberos in the same LDAP domain. To launch the AMI from the AWS web site: 1. Launch your Web browser. 2. Go to the Amazon Web Services EC2 console at The EC2 Dashboard page appears. Log in using your AWS credentials. 3. In the left-hand column, click AMIs. The AMIs page appears. 4. If the correct AMI is not visible in the list of AMIs, then, in the Filter: area at the top of the screen, click Owned By Me or Public Images, then select Private Images. The correct AMI should appear in the list of AMIs. If the correct AMI still does not appear, type Nasuni in the Search AMIs text box at the top of the screen and press Enter. The correct AMI should appear in the list of AMIs. Note: The Nasuni AMIs are not publicly available. Contact Nasuni Technical Support with your AWS account number to gain access to the Nasuni AMIs. 5. Select the check box to the left of the correct Nasuni AMI entry, then click Launch. The Step 2: Choose an Instance Type screen appears. In the Type column, select an instance type with a suitable number of virtual CPU cores, memory, and instance storage for your purposes. If the Nasuni Filer being installed is 7.8 or later, select the highest appropriate M-class or C-class instance type, xlarge or higher. If the Nasuni Filer being installed is before 7.8, limit your selection to an M3 or C3 instance type. After selecting the instance type, click Configure Instance Details. 6. The Step 3: Configure Instance Details screen appears. a. In the Number of Instances text box, enter the number of instances to launch. Using multiple instances can help you deal with issues such as performance, different uses or needs, different geographies or locations, and cache management. b. From the Network drop-down list, Nasuni recommends selecting the VPC option. From the Subnet drop-down list, select the subnet to correspond to the VPC created in Creating a Virtual Private Cloud (VPC) on page 9. Installing the Nasuni Filer on the EC2 Platform 11

14 Installing on the Amazon EC2 Platform Launching the AMI c. From the Auto-assign Public IP drop-down list, select Enable, Select other options based on your security needs. d. Click Add Storage. 7. The Step 4: Add Storage screen appears. Note: On this screen, the largest EBS is the cache disk; the smallest EBS is the COW (copy on write) disk. The default cache disk size is 40 GB. The maximum cache disk size is 1 TB (16 TB for SSDs). The default COW disk size is 10 GB. You receive a warning if the COW disk becomes less than 25 percent of the cache disk. Warning: Due to EC2 limitations, disk (EBS volume) sizes cannot be changed after you launch the AMI. Ensure that the cache disk size is sufficient before launching. a. To remove any of the existing EBS volumes (disks), click the X to the right of that EBS volume. Warning: You cannot remove disk 1 (Root, /dev/sda). Also, if you are installing a Nasuni Filer, and you remove disk 2 (EBS, /dev/sdc) or disk 3 (EBS, /dev/sdb), you must create replacement EBS volumes in step b below. b. If you are installing a Nasuni Filer, to create additional or replacement EBS volumes (disks), follow these steps: i. From the Type drop-down list, select EBS. ii. From the Device drop-down list, select the device for the new EBS volume (disk). If you have removed an existing EBS volume (disk), that device is available in the list. iii. In the Size text box, enter the volume size for the new EBS volume (disk). iv. Leave Snapshot, Volume Type, IOPS, and Delete on Termination on their default values. v. Click Add New Volume. The new EBS volume (disk) appears in the list of EBS volumes (disks). vi. To add more EBS volumes (disks), start with step i above. c. Click Tag Instance. 8. The Step 5: Tag Instance screen appears. Add any desired key/value pairs for management, or keep the defaults. Click Configure Security Group. Installing the Nasuni Filer on the EC2 Platform 12

15 Installing on the Amazon EC2 Platform Launching the AMI 9. The Step 6: Configure Security Group screen appears. On this screen, you configure port security, including creating a new security group for the Nasuni appliances. Warning: Running the Nasuni Filer or NMC on the Amazon EC2 platform is similar to running these systems outside of your business. Unused ports should not be exposed to the public Internet, including the SSH port, port 222. Minimally, the following ports should be exposed to the hosts that access them: Outbound: EC2 does not enable restricting outbound traffic. Nasuni recommends allowing outgoing traffic on all ports to all hosts for the Nasuni Filer and NMC. Inbound: Here are recommendations for the following ports: Port 222 SSH: Close this port. If Nasuni Customer Support requests you to open this port, open this port temporarily to all clients/ranges. Port 443 TCP: Used for Web Access as well as Mobile Access (ios and Android devices). If these features are in use, Nasuni recommends opening this port to all clients/ ranges. Note that these features must be enabled on the Nasuni Filer. Port 8443 TCP: Used to administer the Nasuni Filer and Nasuni Management Console. Open to clients that need to use the Nasuni administration interface. Ports 139 and 445 TCP: Open to clients that need to use SMB/CIFS. Ports 111, 662, 875, 892, 2049, and TCP or UDP: Open to clients that need to use NFS. Port 3260 TCP: Open to clients that need to use iscsi. Port 161 UDP: Open to clients that need to use SNMP. a. Select Create a new Security Group. b. In the Security Group Name text box, enter a name for this security group, such as Nasuni. c. In the Description text box, enter a description for this security group, such as Nasuni appliance security. d. In the rule area, follow these steps: i. Click Add Rule. The new rule appears. In the Port range text box, type 443. In the Source text box, type /0. ii. Click Add Rule. The new rule appears. In the Port range text box, type In the Source text box, type /0. Tip: Add any other rules you need, as discussed above. Nasuni recommends restricting access to only the ports and incoming hosts that you use. e. Click Review and Launch. 10. The Step 7: Review Instance Launch screen appears. Review the information on this screen. To make any changes to the configuration, click Previous to return to previous screens and correct the information. Click Launch. Installing the Nasuni Filer on the EC2 Platform 13

16 Installing on the Amazon EC2 Platform Configuring the Nasuni Filer on EC2 11. The Select an existing key pair or create a new key pair screen appears. For security reasons, key pairs cannot be added. Select Proceed without a Key Pair from the drop-down list. Click Launch Instances. 12. The Launch Status page appears and displays the Your instances are now launching. message. 13. Click View Instances. The Instances screen appears. If the Instances screen does not appear, click Instances in the left-hand column. 14. The new instances appear in the list of instances. Select the check box to the left of the instance. The state should be Running. Details of the selected instance appear at the bottom of the screen. You can click the Status Checks, Monitoring, and Tags tabs to examine their information. 15. Note the Public DNS address on the Description tab. 16. In your web browser, enter the following in the address bar and press Enter: DNS address> It may take a few minutes before the new Nasuni Filer or Nasuni Management Console is available. 17. The Nasuni Filer or Nasuni Management Console is now installed and ready to access using the Public DNS address. Configuring the Nasuni Filer on EC2 You now use the Nasuni Filer Initial Configuration Guide to complete the configuration of the Nasuni Filer. During this configuration, do not change any of the network settings. Leave the network interface/ configuration as DHCP and the traffic group as General. Only a single interface and traffic group are supported on EC2 images. After the Nasuni Filer is running, if you need Nasuni Technical Support to help you with your EC2 instance, enable the Remote Support Service on the Services menu. Configuring the Nasuni Management Console on EC2 You now use the Nasuni Management Console Guide to complete the configuration of the Nasuni Management Console. During this configuration, do not change any of the network settings. Leave the network interface/ configuration as DHCP and the traffic group as General. Only a single interface and traffic group are supported on EC2 images. Installing the Nasuni Filer on the EC2 Platform 14

17 Installing on the Amazon EC2 Platform Performance After the Nasuni Management Console is running, if you need Nasuni Technical Support to help you with your EC2 instance, enable the Remote Support Service on the Console Settings menu. Performance For the Nasuni Filer, industry-standard NAS and SAN interfaces are not designed to be hosted on remote sites and attached over the public Internet. Nasuni recommends using only Mobile Access (ios and Android devices), Web Access, and Nasuni Desktop Client over long distances. Nasuni also recommends only using the NAS and SAN protocols from clients that are hosted in the same infrastructure near the Nasuni Filer. For the Nasuni Management Console, since all access is browser-based, there are no specific performance concerns. Installing the Nasuni Filer on the EC2 Platform 15

18 Chapter 2: Controlling the EC2 Instance Overview Virtual platforms offer the ability to control various aspects of your Nasuni Filer or Nasuni Management Console. This chapter presents procedures for these control functions. Because these controls depend on third-party virtual platforms, you should follow the procedures for your specific virtual platform. Note: The vendor changes their interfaces occasionally with little notice to the users. The exact screens and text on these platforms might change at any time. Shutting down the EC2 instance On the virtual platform, you can shut down the EC2 instance of the Nasuni Filer or Nasuni Management Console. Note: You can also shut down the Nasuni Filer or Nasuni Management Console using the Shutdown or Power button available on every page. To shut down the EC2 instance, follow these steps: 1. Launch the Amazon Web Services EC2 console at The EC2 Dashboard page appears. Log in using your credentials. 2. Click Instances in the left-hand column. The Instances screen appears. 3. Right-click the instance, then select Stop from the drop-down list. The state changes to Stopping, then to Stopped. The virtual machine shuts down. Installing the Nasuni Filer on the EC2 Platform 16

19 Controlling the EC2 Instance Starting the EC2 Instance Starting the EC2 Instance On the virtual platform, you can start a stopped EC2 instance of the Nasuni Filer or Nasuni Management Console. To start a stopped EC2 instance, follow these steps: 1. Launch the Amazon Web Services EC2 console at The EC2 Dashboard page appears. Log in using your credentials. 2. Click Instances in the left-hand column. The Instances screen appears. 3. Right-click the instance, then select Start from the drop-down list. The state changes to Pending, then to Running. The virtual machine starts. Installing the Nasuni Filer on the EC2 Platform 17

20 Chapter 3: Uninstalling the EC2 Instance Overview This chapter explains how to uninstall the Nasuni Filer or Nasuni Management Console from the EC2 platform. You might need to uninstall the Nasuni Filer or Nasuni Management Console if you are upgrading the system hardware. Note: The vendor changes their interfaces occasionally with little notice to the users. The exact screens and text on these platforms might change at any time. Uninstalling the Nasuni Filer or Nasuni Management Console Caution: When you uninstall the Nasuni Filer, all data in the cache is deleted. To uninstall the Nasuni Filer or Nasuni Management Console on the EC2 platform: 1. Launch the Amazon Web Services EC2 console at The EC2 Dashboard page appears. Log in using your credentials. 2. Click Instances in the left-hand column. The Instances screen appears. 3. Right-click the instance, then select Terminate from the drop-down list, Caution: Terminating a Nasuni Filer deletes the EC2 instance and all data in it. Any data not preserved via a snapshot is permanently lost The state changes to Shutting Down, then to Terminated. The virtual machine is uninstalled. Installing the Nasuni Filer on the EC2 Platform 18

21 Index A Active Directory 7 Administration Guide vii Amazon AWS S3 7 Amazon EC2 8 Amazon EC2 platform 7 Amazon Machine Image 9, 11 Amazon Web Services 11, 16, 17, 18 AMI 9, 11 Atmos 8 authentication LDAP 7 AWS 11 Amazon AWS S3 7 Azure 7 Microsoft 8 back-end cloud storage 7 B C cache disk 12 maximum 12 C-class 11 CIFS 13 Cleversafe 8 compression 7 COW (copy on write) disk 12 CPU cores 11 customer license 8 deduplication 7 DHCP Options Set creating 9, 10 selecting 9, 10 D E EBS 12 EC2 Amazon 8 EC2 console 9, 11, 16, 17, 18 Nasuni ii Nasuni Support ii EMC 8 EMC Atmos 8 EMC ViPR 8 H Hardware Getting Started Guide vi HTTP/REST protocol 7 Initial Configuration Guide vii installation 7 Installing the Nasuni Filer on the Azure Platform vi Installing the Nasuni Filer on the EC2 Platform vi Installing the Nasuni Filer on Virtual Platforms vi Instance Type 11 iscsi 13 I Installing the Nasuni Filer on the EC2 Platform 19

22 Index LDAP 7 maximum cache disk 12 M-class 11 memory 11 Microsoft Azure 7, 8 Mobile Access 15 L M N NAS 15 Nasuni Filer 11 shutting down 16 starting 17 Nasuni Management Console 11 Nasuni Management Console Guide vii Nasuni Management Console Quick Start Guide vii NFS 13 Number of Instances 11 U uninstall 18 Using Multiple Protocols vii ViPR 8 Virtual Private Cloud creating 9, 10 VPC creating 9, 10 V W Web Access 13, 15 Windows Previous Versions 7 xlarge 11 X port security 13 Public DNS address 14 S3 Amazon AWS S3 7 SAN 15 SFTP 7 shutting down Nasuni Filer 16 SMB 13 SNMP 13 SSH 13 starting Nasuni Filer 17 P S T text conventions v Third-Party Licensing Guide vii Installing the Nasuni Filer on the EC2 Platform 20