Install and Configure File IQ on AWS EC2

Virtual Machine Requirements

• On AWS EC2, only use EBS-Only virtual machines

• On AWS EC2, for best performance use Provisioned IOPS SSD (io2) for high-intensity I/O

Deploy File IQ in the Amazon EC2 Platform

This chapter explains how to install the File IQ Solution on the Amazon EC2 platform.

Tip: This document is about deploying virtual machines. It does not cover configuring a storage account for use with Nasuni volumes.

Warning: DO NOT attempt to restore from a virtual machine snapshot or backup. Attempting to restore from a virtual machine snapshot or backup puts the IQ Appliance in an unknown state in relation to the Nasuni Orchestration Center (NOC) and requires a recovery process. This might result in data loss.

Tip: Nasuni recommends leveraging your cloud provider's role-based access and identity access management features as part of your security strategy. Based on your policies, such features can limit or prohibit administrative access to the cloud account.

Important: File IQ Appliances must be configured with operational DNS servers and a time server (internal or external) within your environment. The File IQ Appliance is configured with a default time server time.nasuni.com. If you need to use a different time server, the procedure to change the default time server is documented in the Nasuni Edge Appliance Time Configuration section of the Nasuni Edge Administration guide.

Note: Vendors change their interfaces occasionally with little notice to the users. The exact screens and text on these platforms might change at any time.

Tip: Check out the File IQ Installation and Configuration videos for a general reference on the File IQ installation process. Your specific hypervisor installation will include unique steps not included in this video reference series.

Day 1 File IQ Installation Checklist

To complete a day 1 File IQ installation, follow this checklist:

1. Prerequisites

The following items should be readily available to help you navigate the File IQ installation and setup process. It is recommended that you complete these requirements before starting or have a way to fulfill them during the installation process.

2. Installing File IQ Using the Amazon EC2 AMI

This step describes how to install the File IQ Appliance using the File IQ Amazon Machine Image (AMI) from portal.nasuni.com.

Important: You must create and maintain your own AWS account because Nasuni does not have access. To gain access to the Nasuni AMIs, contact Nasuni Technical Support with your AWS account number. To create an EC2 account, visit http://aws.amazon.com/ec2/.

Tip: In the Nasuni model, customers provide their own cloud accounts for storing their data. As part of their overall security strategy, customers should leverage their cloud provider's role-based access and identity access management features. These features can limit or prohibit administrative access to the cloud account based on company policies. 

Important: File IQ Appliances must be configured with operational DNS servers and a time server (internal or external) within your environment. The File IQ Appliance is configured with a default time server time.nasuni.com. If you need to use a different time server, the procedure to change the default time server is documented in the Nasuni Edge Appliance Time Configuration section of the Nasuni Edge Administration guide.

Important: To access Active Directory-enabled volumes, the File IQ Appliance must be connected to an Active Directory server in the same Active Directory Forest. This requires part of your Active Directory infrastructure to run on the EC2 platform. 

To launch the AMI from the AWS Dashboard page, follow these steps: 

1. If your AWS account ID can access the Nasuni AMIs, continue to step 2.
   If not, follow this procedure to enable your AWS account ID to access the Nasuni AMIs. Alternatively, request Nasuni Technical Support to enable your AWS account ID to access the Nasuni AMIs. 

   1. Log in to your Nasuni account Web site ( https://portal.nasuni.com/) and click Install Software.

      The Installs page appears.
      

   2. Click Amazon EC2 or scroll down to the Nasuni AMIs on EC2 area. 

   3. In the text box, enter the 12-digit AWS account IDs permitted to access the Nasuni AMIs. Separate AWS account IDs by commas. 

   4. Click Submit. These AWS account IDs are granted access to the Nasuni AMIs. 

      Note: Access can take up to 5 minutes to be granted. If access has not been given after 5 minutes, contact Nasuni Technical Support. 

2. Go to the Amazon Web Services EC2 console at https://console.aws.amazon.com/ec2/. The EC2 Dashboard page appears.

3. In the left-hand column, click AMIs. The AMIs page appears. 

4. The File IQ AMI appears in the list of AMIs.

   Tip: If the File IQ AMI is not visible on the list of AMIs, navigate to the filter area at the top of the page and click Owned by Me or Public Images, then click Private Images from the dropdown list. The File IQ AMI should appear in the list of AMIs.  If not, type “Nasuni” in the Search text box and press Enter. The File IQ AMI should appear in the list of AMIs. 

5. From the list of AMIs, choose the most up-to-date AMI version for File IQ. 

6. Select the check box to the left of the correct Nasuni AMI entry and click Launch instance from AMI (upper right corner). 
   The Launch an instance screen appears.

7. In the Name text box, enter a name for this instance. 

   Note: You can add tags (key and value pairs) by clicking Add additional tags.

8. In the Application and OS Images (Amazon Machine Image) area, verify that the correct AMI has been chosen. If necessary, you can change your AMI selection here. 

9. In the Instance type area, select an instance type with a suitable number of virtual CPU processors and memory.

   Important: The File IQ Sizing Tool provides a suggestion for the Virtual Machine size to use when setting up the File IQ Virtual Machine in EC2.

10. In the Key pair (login) area, leave the Key pair name empty.

11. In the Network settings area, click Edit to update. 

    1. From the VPC dropdown list, select the VPC to use. 

    2. From the Subnet dropdown list, select the subnet corresponding to the VPC you selected.

    3. From the Auto-assign public IP dropdown list, select Disable. You can assign a public IP to the File IQ Appliance; however, the File IQ can operate effectively with a private IP address.

    4. Use the Firewall (security groups) area to configure security, as follows. 

       Warning: Running the File IQ on the Amazon EC2 platform is like running these systems outside of your business. Unused ports, including the SSH port and port 222, should not be exposed to the public Internet.

       Minimally, the following ports should be exposed to the hosts that access them:

       Outbound: Amazon EC2 does not enable restricting outbound traffic. Nasuni recommends allowing outgoing traffic to all hosts on all ports for the File IQ.

       Inbound: Here are recommendations for the following ports:

       • Port 222 SSH: This port is implicitly closed. If Nasuni Customer Support requests that you open it, open it temporarily to all clients and ranges.

       • Port 443 TCP: Used to administer the Nasuni Appliance (see step e.iv).

       • Port 8443 TCP: Used to administer the File IQ Appliance. Open to clients who need to use the Nasuni administration interface (see step e.iii).

       • Port 3000 HTTPS: Used to access the File IQ Dashboards (see step e.v).

    5. Select Create security group or use an existing security group designed for Nasuni products.

       1. In the Security group name text box, enter a name for this security group. For example, “Nasuni”. 

       2. In the Description text box, enter a description for this security group, such as “Nasuni appliance security.” 

       3. Update the security group rule.

          1. In the Type combo box, select Custom TCP.

          2. In the Port range text box, type “8443”. 

          3. In the Source type, select Custom.

          4. In the Source text box, type “0.0.0.0/0”. 

       4. Click Add security group rule. The new rule appears.

          1. In the Type combo box, select HTTPS.

             Note: For HTTPS, port 443 is entered automatically.

          2. In the Source type, select Custom.

          3. In the Source text box, type “0.0.0.0/0”

       1. Click Add security group rule. The new rule appears.

          1. In the Type combo box, select Custom TCP.

          2. In the Port range text box, type “3000”. 

          3. In the Source type, select Custom.

          4. In the Source text box, type “0.0.0.0/0”. 

       Tip: Add additional rules as required. Nasuni recommends restricting access to only the ports and incoming hosts you use. 

12. The Configure storage area allows you to manage the disk for the virtual machine. By default, four disks are automatically provisioned. Skip this section if you are using a version below 10.1, as the resizing of EBS Volumes for the File IQ Appliance is performed in Appendix E: Resize the File IQ Appliance EBS Volumes after completing the first boot wizard.

    Important: Do not modify any setting in the Configure storage section, because it might interfere with the File IQ Appliance installation process.

13. Use the Advanced details area for additional configuration. 

    1. From the Shutdown behavior dropdown list, select Stop. 

       Caution: Ensure that the Shutdown behavior is not set to Terminate. Instance termination renders the File IQ Appliance inoperable and can lead to data loss. 

    2. Placement groups can help minimize the network latency between the File IQ Appliance and EC2 workloads. By default, when launching a new EC2 instance, the EC2 service attempts to spread all your instances across underlying hardware to minimize correlated failures.
       Placement groups influence the placement of interdependent instances at no additional charge. AWS offers three placement group strategies. The Cluster placement group strategy works best to minimize latency. You can add the instance to an existing placement group or create a new one using the Cluster placement group strategy.
       You can also change the placement group, as described here.

14. Use the Summary area to verify and change configuration. 
    In the Number of Instances text box, use the default value “1”.  

15. Click Launch instance. A dialog appears, allowing you to select an existing key pair or create a new one.

16. Select Proceed without key pair and click Launch instance. The instance is launched.

17. At the bottom of the screen, click View all instances. The Instances screen appears. 

18. If the Instances screen does not appear, click Instances in the left-hand column. The new instances appear in the list of instances.

19. Select the check box to the left of the instance. The Instance State displays Running. 

    Note: Details of the selected instance appear at the bottom of the screen. Click the Status and alarms, Monitoring, and Tags tabs to examine their information. 

20. Name the EBS volumes:

    1. After the instance is running, navigate to the EC2 dashboard.

    2. Access the Instances section and click the File IQ Appliance instance for which you need to name the volumes.

    3. On the instance details page, click the Storage tab, where the list of volumes is attached to this instance.

    4. For each volume, click on the Volume ID column to access the volume details page, and click on the Name column to add a descriptive name. The descriptive name of each volume (such as “File IQdb”) should be prefixed with the File IQ Instance name as a best practice. For example:

       1. In the release prior to 10.1

          1. The EBS Volume with a size = 32 GB should be named “<File IQ_instance_name>_os” for the OS disk.

          2. The EBS Volume with a size = 10 GB should be named “<File IQ_instance_name>_cow” for the COW disk.

          3. The EBS Volume with a size = 30 GB should be named “<File IQ_instance_name>_fiqdb” for the File IQ database disk.

          4. The EBS Volume with a size = 40 GB should be named “<File IQ_instance_name>_cache” for the cache disk.

       2. In the release from 10.1+

          1. The EBS Volume with a size = 32 GB should be named “<File IQ_instance_name>_os” for the OS disk.

          2. The EBS Volume with a size = 10 GB should be named “<File IQ_instance_name>_cow” for the COW disk.

          3. The EBS Volume with a size = 30 GB should be named “<File IQ_instance_name>_cache” for the cache disk.

          4. The EBS Volume with a size = 40 GB should be named “<File IQ_instance_name>_fiqdb” for the File IQ database disk.

          After a volume is renamed, click your browser's back button to return to the list of volumes for your File IQ Instance, then proceed to the next volume rename step.

          Important: The File IQ Appliance relative sizes are important during installation because the NEA (on which the File IQ Appliance is built) allocates disks to various roles based on size.  Nasuni recommends using suffixes for the data disks, so that the names of the disk indicate their expected roles based on their initial sizes. The File IQ DB Disk is the largest, the Cache Disk is the next largest, and the COW Disk is the smallest.

The deployment of the File IQ Appliance instance is complete.

3. Running the File IQ Appliance First Boot Wizard

To access the newly installed File IQ Appliance on Amazon EC2, follow these steps:

1. Navigate to the EC2 Dashboard by clicking the Services menu at the top of the AWS Management Console and selecting EC2.

2. From the navigation pane on the left, click Instances. The list of your EC2 instances displays.

3. Locate and click the EC2 instance you previously created for the File IQ Appliance. The details pane for this instance appears, showing an overview under the Details tab.

4. Obtain the IP Address under the Details tab:

   1. If a public IP address has been assigned to your instance, you can locate it under the Public IPv4 address field.

   2. If no public IP address is assigned, locate the Private IPv4 addresses field instead. To connect using a private IP, you must be within the same network, for example, a VPN or another EC2 instance within the same VPC.

      Note: If both the Public IPv4 address and Private IPv4 addresses are present, you can use either one.

   3. If the IP address field is empty or the instance is not running, click Instance State, followed by Start Instance.

      Note: It might take a few minutes for the instance to launch and for the IP address to be displayed. Refresh the page to see the updated information.

5. Navigate to the First Boot Wizard for the File IQ Appliance by opening a new browser window.

   1. To access the File IQ Appliance, enter the address in this form: https://<IP address>, where <IP address> is the IP address from step 4.

   2. The Enter the Network Parameters for this Filer page appears.
       

6. Enter the Hostname defined in the File IQ Hostname. This was defined in the 1. Prerequisites section.

7. Complete the remainder of the System Settings defined in the File IQ Network Details as part of the 1. Prerequisites section above.

8. Click Continue. The Review the Network Settings pane appears.

9. If all fields are correct, click Continue. The next pane confirms if the File IQ Appliance is Configuring Network Settings. If the File IQ Appliance does not automatically reconnect, try refreshing the page and checking if the File IQ Appliance’s IP address has changed. If so, update the browser address bar.

10. The Nasuni Filer Software Update pane appears. Click Continue.

11. Enter the File IQ Serial Number and Authorization Code obtained under the File IQ Serial Number and Authorization Code as part of the 1. Prerequisites section above.

12. Click Continue. The Add a New Nasuni Filer to your account pane appears.

    Note: If you get an Invalid serial number or access code provided during this step, it is because you have used a NEA Serial Number instead of an File IQ Serial Number. Nasuni recommends double-checking your Serial Number and trying again. See the 1. Prerequisites section for the correct location to the File IQ Serial Number and Authorization Code values.

13. Enter Install New Filer into the Confirmation textbox.

14. Click Continue. The Accept the Terms of Service and License Agreement pane appears.

15. Accept the Terms of Service and click Continue. The Enter or accept Filer Name pane appears.

16. Click Continue. The Nasuni Management Console Detected pane appears.

17. Enable the Join NMC Management checkbox and click Continue. The Enter a username and password for Administration of this Filer pane appears.

18. Enter your NMC local account Username and Password, and then Confirm Password. These were obtained in the File IQ Username and Password section of the 1. Prerequisites section above.

19. Click Continue, the First Boot Wizard is complete, and the File IQ Appliance Management window appears.

3.a. Joining the File IQ Appliance to Active Directory

4a. Set the Escrow Passphrase for the File IQ Appliance (10.0+)

4b. Add the File IQDB disk to the File IQ Appliance

Important: These steps are only applicable to File IQ Appliances prior to the 10.1 release.

Before enabling the File IQ Appliance, add another disk for the File IQ Database, by following this procedure:

1. Log in to the Nasuni Management Console associated with the File IQ Appliance.

2. Click Filers.

3. Click Shutdown & Reboot. The Shutdown and Reboot pane appears.

4. For the File IQ Appliance, click the associated Shutdown/Reboot action. The Initiate Shutdown/Reboot of File IQ Appliance pane appears.

5. Enter ‘Change Filer Power State’ into the Confirmation Phrase textbox.

6. Select Shut down immediately. Click Shutdown. The Shutdown and Reboot pane appears. Wait until the Status column for the File IQ Appliance changes to a checkmark before proceeding; at that point, the File IQ Appliance is shut down.

7. Go to the Amazon Web Services EC2 console at: https://console.aws.amazon.com/ec2/. The EC2 Dashboard page appears.

8. Click Instances under the Instances section in the left-hand menu and click on your File IQ Appliance.

9. Take note of the Instance ID and Availability Zone to use in a later step.

10. Click Volumes under the Elastic Block Store section in the left-hand menu

11. Click Create volume. The Create Volume pane appears.

    1. Volume Type: Nasuni recommends using Provisioned IOPS SSD (io2) for the File IQ DB volume.

    2. Size: Use the File IQ Sizing Tool to estimate the size of the Nasuni File IQ DB volume.

    3. IOPS: Use the File IQ Sizing Tool to estimate the IOPS of the Nasuni File IQ DB volume.

    4. Throughput: Not applicable if you select Provisioned IOPS SSD (io2) for Volume Type. Otherwise, use the File IQ Sizing Tool to estimate the throughput of the Nasuni File IQ DB volume.

    5. Availability Zone: Must match the Availability Zone of your File IQ Appliance.

12. Select the newly created volume from the list of Volumes.

13. Click Actions and then Attach volume.

    1. Instance: Enter the Instance ID, which was copied in step 9, and select your File IQ Appliance.

    2. Device Name: Select /dev/sdd as the device name.

14. Click Attach.

15. Click Instances under the Instances section in the left-hand menu and click on your File IQ Appliance.

16. With the instance selected, click the Instance state dropdown menu at the top of the page.

17. Click Start instance from the dropdown options. It might take a few minutes for the instance to start. You might need to refresh the page to see the updated information

The File IQ Appliance Virtual Machine starts.

5. Connect the Nasuni Volumes to the File IQ Appliance

6. Disabling Quality of Service (QoS) for the File IQ Appliance

7. Enable File IQ in Nasuni Portal and Configure Edge Appliances

a. Enabling the File IQ on the New File IQ Appliance

b. Enabling File IQ Service and Assigning the File IQ Appliance for the NEA

c. Forcing the Configuration to be Applied to the File IQ Appliance and Nasuni Edge Appliance

8. Accessing the File IQ Dashboards

9. Nasuni File IQ Status and File IQ Appliance Health

This section describes the Nasuni File IQ Status tool that is shipped with the File IQ Appliance.

a. File IQ Status Tooling

b. File IQ Appliance Health

c. File IQ Status Messaging

Appendix A: Firewall Configuration

The File IQ Appliance and Nasuni Edge Appliance both require access to the Microsoft Azure Event Hub API. For configuration instructions, see Firewall and Port Requirements.

Appendix B: Deletion Security

The Amazon cloud storage platform offers several safeguards to prevent or mitigate unwanted deletion. You might choose to employ some or all these safeguards.

For specific recommendations and guidelines on managing and safeguarding EC2 instances and associated disks (EBS volumes), AWS provides targeted documentation that can help protect these resources from accidental or unauthorized deletion.

For more information directly related to managing EC2 instances and EBS volumes, see the following resources:

1. Amazon EC2 Documentation. This section includes detailed information on managing instances, including permissions and lifecycle considerations: Amazon EC2 Documentation

2. Amazon EBS Documentation. Covers all aspects of managing Elastic Block Store volumes, including backups, encryption, and preventing accidental deletion: Amazon EBS Documentation

3. AWS Using IAM to Manage Access to Amazon EC2 Resources. Provides guidelines on how to create and manage IAM policies for EC2 resources, crucial for preventing unauthorized access or deletion: Manage Access to EC2 Resources

4. Preventing Unintended Resource Deletion with AWS Rule Locks. While not limited to just EC2 and EBS, this guide explains how to use rule locks to prevent accidental deletion: Rule Locks.

Storage Redundancy

Carefully consider the best redundancy options for your data and your organization. Considerations might include legally mandated data locations and geographic proximity to other resources.

To achieve this, Amazon provides Regions and Availability Zones, AWS Local Zones, Data Replication Options, and Automation and Scaling Capabilities. For more information, see Resilience in Amazon EC2.

Locking Resources

Locking resources in AWS is critical to ensuring that essential components are not accidentally modified or deleted. AWS offers various mechanisms to control and restrict these operations, enhancing security and governance across your AWS environment.

Resource Locking Features in AWS

1. AWS Resource Locks: Lock your resources to prevent accidental deletion or modification. Achieve this using IAM policies that restrict delete permissions and other critical operations.

2. IAM Policies:

   1. Prevent Deletion: Configure IAM policies to deny the deletion of specific resources. Specify actions that cannot be executed, effectively implementing a CanNotDelete lock.

   2. Read-Only Access: Set read-only access policies to resources to prevent modifications.

3. Permissions Required: Specific permissions to alter IAM policies or service configurations are required to create or manage locks. Typically, only users with administrative privileges (AdministratorAccess) or those explicitly granted permissions can manage these locks.

4. Inheritance: Locks in AWS are not inherited through resource hierarchy (like resource groups) by default. Each resource needs a specific lock or IAM policy to ensure protection.

For more information, see Controlling access to AWS resources using policies.

Protecting Attached Resources in AWS

AWS incorporates several safeguards to prevent the unintended deletion of resources that are currently in use or attached to other services, ensuring data integrity and operational continuity.

Features for Protecting Attached Resources in AWS

1. Amazon EC2 and EBS volumes:

   1. Prevention of Deletion: AWS does not allow the deletion of an Amazon Elastic Block Store (EBS) volume when attached to a running instance. This safeguard ensures that active data is not accidentally removed.

   2. Deletion Protection: Configure Amazon EC2 instances with deletion protection to prevent accidental termination through the AWS Management Console, CLI, or API.

2. Leased Resources: AWS provides similar protections via resource-locking features and permissions management.

3. Permissions and Policies: In AWS, IAM policies are critical in preventing resource deletion. Define policies restricting users' ability to delete important resources like EC2 instances, EBS volumes, and more.

For more information, see Amazon EC2 and Amazon EBS.

Appendix C: Controlling the EC2 File IQ VM

Virtual platforms offer the ability to control various aspects of your File IQ Appliance. This section 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.

Starting the Amazon EC2 VM

You can start a stopped Amazon EC2 VM of the File IQ Appliance on the virtual platform.

To start a stopped Amazon EC2 VM, follow these steps:

1. Open your web browser and navigate to: https://console.aws.amazon.com/ec2/.

2. Once logged in, navigate to the EC2 Dashboard.

3. On the EC2 Dashboard, click Instances in the left-hand navigation pane. A list of your EC2 instances displays.

4. In the list of instances, locate the File IQ Appliance instance you want to start. You can identify it by its Instance ID, Name tag, or other details set during its creation or previous configuration.

5. Select the instance by clicking the checkbox next to its name.

6. With the instance selected, click the Instance State dropdown menu at the top of the page.

7. Click Start instance from the dropdown options.

Note: This might require a few minutes to launch, or a page refresh to see the updated information.

Status of the Amazon EC2 VM

To view the status of the Amazon EC2 VM of the File IQ Appliance, follow these steps:

1. After starting the instance, monitor its status in the Instance state column of the Instances list.

2. The instance might take a few minutes to change from Stopped to Pending to Running.

3. Once the instance status is Running, it indicates that the system has completed the boot process. However, additional time might be required for the operating system to load and for startup tasks to complete. To determine operational readiness, monitor the Status check column for any system and instance checks to pass, confirming that all services and applications are fully functional and ready for use.

Shutting Down the Amazon EC2 VM

To shut down the Amazon EC2 VM, follow these steps:

1. Log in to the Nasuni Management Console associated with the File IQ Appliance.

2. Click Filers.

3. Click Shutdown & Reboot. The Shutdown and Reboot pane appears.

4. For the File IQ Appliance, click the associated Shutdown/Reboot action.

5. The Initiate Shutdown/Reboot of File IQ Appliance pane appears.

6. Enter “Change Filer Power State” into the Confirmation Phrase textbox.

7. Select the Option to Shut down immediately. Click Shutdown. The Shutdown and Reboot pane appears.

8. Wait until the Status column for the File IQ Appliance changes to a checkmark before processing and the File IQ Appliance shuts down.

Appendix D: Uninstalling the Amazon EC2 VM

This section describes uninstalling the File IQ Appliance from the Amazon EC2 platform.

Note: Vendors change their interfaces occasionally with little notice to the users. The exact screens and text on these platforms might change at any time.

Uninstalling the File IQ Appliance

To uninstall the File IQ Appliance on the Amazon EC2 VM platform, follow these steps:

1. After logging in to https://console.aws.amazon.com/ec2/, navigate to the EC2 Dashboard.

2. Click Instances in the left-hand navigation pane to view your EC2 instances.

3. Locate the File IQ Appliance VM you want to uninstall and click the checkbox next to its name.

4. From the Instance State dropdown menu, select Stop instance to ensure the VM is stopped.

5. Confirm the action by clicking Stop in the confirmation dialog.

6. With the instance still selected, click Actions.

7. Navigate to Instance State and then select Terminate instance.

8. A confirmation dialog box appears with a list of associated EBS volumes. Note the EBS Volume identifiers. This list of volume identifiers might be used to identify the list of volumes to be deleted.

9. Confirm your intention to delete the instance by clicking Terminate. This action permanently deletes the VM.

Terminating the virtual machine might not delete the EBS volumes associated with it.

To delete the associated EBS volumes, follow these steps:

1. After terminating the instance, navigate to Volumes in the left-hand navigation pane.

2. Look for any volume names prefixed with the File IQ Instance name ,or use the list of volume identifiers provided in the Terminate instance confirmation dialog.

3. Select the volumes in the Volumes table view.

4. If any of the volumes are still associated with the terminated instance, click Actions.

   1. Select Detach volume, and a confirmation dialog appears.

   2. Click Detach. The associated volumes are no longer associated with the terminated instance and are ready to be deleted.

   3. Confirm that the volumes are selected in the Volumes table view.

5. Click Actions and select Delete volume. A confirmation dialog with a list of volume identifiers appears.

6. Type “delete” in the Confirmation field.

7. Confirm the deletion by clicking Delete.

8. Revisit the Instances and Volumes sections to ensure that the instances and volumes have been successfully deleted.

Appendix E: Resizing the File IQ EBS Volumes

This section describes how to resize the File IQ Appliance EBS volumes from the Amazon EC2 platform.

Note: Vendors change their interfaces occasionally with little notice to the users. The exact screens and text on these platforms might change at any time.

Important: Only EBS volumes can be increased.

Prerequisites:

• The File IQ Instance installation is complete.

• The File IQ EBS volumes are correctly named using the prefixing of the volume names (such as “File IQdb”) with the File IQ Instance name. For more information, see step 20 of 2. Installing File IQ using the Amazon EC2 AMI.

To resize the File IQ EBS volumes, follow these steps:

1. Log in to the Nasuni Management Console associated with the File IQ Appliance.

2. Click Filers.

3. Click Shutdown & Reboot. The Shutdown and Reboot pane appears.

4. For the File IQ Appliance, click the associated Shutdown/Reboot action. The Initiate Shutdown/Reboot of File IQ Appliance pane appears.

5. Enter ‘Change Filer Power State’ into the Confirmation Phrase textbox.

6. Select Shut down immediately, and click Shutdown. The Shutdown and Reboot pane appears.

7. Wait until the File IQ Appliance's Status column changes to a checkmark before proceeding; at that point, the appliance is shut down.

8. Go to the Amazon Web Services EC2 console at: https://console.aws.amazon.com/ec2/. The EC2 Dashboard page appears.

9. Click Volumes in the left-hand navigation pane to view your list of EBS volumes.

10. The list of volumes displays. By filtering the list of volumes using the File IQ Instance name, locate the File IQ EBS volumes you need to resize.

11. For each of the volumes displayed in the list that you want to resize, execute the following steps:

    1. Select the Volume checkbox that you want to change.

    2. From the Actions dropdown menu, select Modify volume. The editor for the volume appears.

    3. Via the Volume editor, you can update:

       1. The Volume type. Nasuni recommends:

          1. Using Provisioned IOPS SSD for both the File IQ cache volume and File IQ DB volumes.

          2. Using General Purpose SSD for both the Operating System and COW volumes.

       2. The volume's Size. Use the File IQ Sizing Tool to estimate the size of the Nasuni Cache and File IQ DB volumes.

       3. The volume's IOPS value. Use the File IQ Sizing Tool to set this value.

       4. The Throughput value (MiB/s).

          Note: This option is available when the volume type is set to gp3.

    4. Click Modify. A confirmation dialog box appears. Ignore the message indicating that the file system must be extended to the new volume size. The File IQ appliance automatically detects when the EBS volume is extended and adjusts the file system accordingly.

    5. Click Modify. The volume update is triggered, and the list of all the volumes is displayed.

12. On the left panel, click Instances. The list of Instances is displayed, and the same File IQ instance previously modified should remain selected. If not, reselect the File IQ Instance to display the Instance's detailed view.

13. With the instance selected, click the Instance state dropdown menu at the top of the page.

14. Click Start instance from the dropdown options. It might take a few minutes for the instance to start. You might need to refresh the page to see the updated information.

The File IQ Appliance Virtual Machine starts.

Appendix E: HTTPS Proxy Configuration

For more information on the HTTPS proxy configuration, see Chapter 11 of the NEA.

Appendix F: Next Steps