Amazon Web Services provides virtual cloud platform and computing resources for developers and IT professionals. SoftNAS® provides a powerful shared-storage interface into this robust resource through unified connections of CIFS, NFS, iSCSI, giving the virtually unlimited capacity, remote replication, and high availability needed for the expected workload.
- Complete the /wiki/spaces/SD/pages/92996328 initial registration procedure, beginning from www.buurst.com and choose SoftNAS® for AWS.
- Continue through the registration wizard.
A SoftNAS® for Amazon Marketplace pricing page will ultimately appear. Choose to Launch with 1-Click or change preferred settings in the Manual Launch page and Launch from EC2 Console.
Amazon defines instance as "a copy of an Amazon Machine Image running as a virtual server in the AWS cloud." This guide will use the AWS terminology in this section for UI consistency.
What is covered in this document:
Manual Launch Procedure
To maximize customization, Manual Launch is the recommended choice for initial setup. Below are the basic steps to follow.
Launch Instance
- Once an AWS account has been created, log into the management console, and select EC2 from All services, or if applicable, Recently visited services, and navigate to the EC2 Dashboard.
- Create Instance from the Launch Instance item that appears on the Dashboard as well as the Instances page.
1. Choose a SoftNAS® Amazon Machine Image (AMI)
- From the menu on the left, click AWS Marketplace and search for SoftNAS.
- Select the version that most accurately fits the needs of deployment.
- Click Next.
2. Choose an Instance Type
Things to consider when deciding on the best instance type and size to deploy. Consider the following elements when configuring an Instance:
Element | Setup Recommendations |
|---|---|
Memory |
|
| |
| |
| |
CPU |
|
| |
Network |
|
|
For additional information, please refer to: AWS EC2 System Requirements.
- Select the instance size that best fits the expected environment.
- Then click Next: Configure Instance Details.
3. Configure Instance Details
Setting | Recommended | Notes |
|---|---|---|
Number of Instances | 1 | |
Network | EC2 | See VPC Notes below |
Availability Zone | No preference | Choose a preset zone |
IAM | None | |
Shutdown Behavior | Stop | |
Enable Termination Protection | Checked | Prevent Instances from being accidentally deleted |
Monitoring | As preferred | See CloudWatch Notes below |
VPC Notes:
For optimal efficiency, launch an instance into an Amazon VPC (Virtual Private Cloud) environment instead of the default Launch Into option to EC2. VPCs can be useful if all computing will be done in the EC2 environment, or to interconnect an existing network via a VPN gateway to the VPC environment; e.g., setting up an IPSec tunnel between an existing data center and the VPC. To operate SoftNAS® within the private subnet of a VPC, create an outbound NAT route that enables the SoftNAS® instance to access the Internet to perform software updates, activation, etc. In this case, only outbound TCP traffic to the softnas.com and mirror.softnas.com domains are required to be enabled; i.e., inbound access to ports 22 and 443 for administration can be restricted to VPC subnet access only. Please refer to the Knowledge Base Article titled Upgrading Software through a Firewall.
Use a VPC to use SoftNAS® in high availability mode (SNAP HATM). For more information, see the document High Availability.
CloudWatch Note:
Click Next: Add Storage.
4. Add Storage
This section allows you to attach additional EBS volumes and instance store volumes or edit the settings of the root volume. SoftNAS recommends skipping this step, as it is easier to configure and add disks within the SoftNAS UI, rather than creating disks and later provisioning disks created in the azure portal.
Instance store volumes may not be attached after launching an instance; however, EBS volumes may be attached after the instance is launched. Keep this in mind during initial network planning.
Using gp3 SSDs with SoftNAS
If you are planning to use the EBS General Purpose SSD gp3, it needs to be added using the EC2 console or during the initial creation of the SoftNAS Instance. For additional information about this specific SSD, please refer to AWS Getting Started - Storage. There is also an article titled "Adding an AWS gp3 disk device to a SoftNAS deployment: Best Practice" for additional information.
See also: Managing Volumes
5. Instance Tags
The EC2 environment takes advantage of keyword tag benefits by proactively setting a connection between an account and access to the current instance. Assigning a name tag to a new deployment helps to easily locate it on the EC2 Dashboard when there are many other instances deployed.
Note the following basic tag restrictions:
- The aws: prefix is reserved for AWS use, and tags with this prefix do not count against tags per resource limit.
- Maximum Tags: 10 tags per resource
- Maximum Key String: 127 Unicode characters (case-sensitive)
- Maximum Value String: 255 Unicode characters (case-sensitive)
6. Creating or Selecting a Security Group
Next, network settings and services can be determined in advance by setting up a Security Group. Depending on use case and the services you may wish to apply to your SoftNAS environment, the
- If creating a new security group for your instance, select the Create a new security group radio button.
- To create a custom configuration, simply click Add Rule, and select the desired protocol, the desired port, and for improved security, place a limit on the accepted source IP.
- To select an existing security group configuration, click the Select an existing security group radio button, and select the desired option from the dropdown that appears.
Creating a Key Pair
A Key Pair is a pair of security credentials associated with this Instance; the Public Key and the Private Key. The Create Key Pair section of the wizard will be displayed. In this step, create a public/private key pair used with SSH to access and administer the SoftNAS® instance in the cloud.
The Key Pair helps to securely connect to an instance when it is launched. You have two options to choose from. Either choose from existing key pairs that have been created in the current region or create a new key pair.
- If choosing from existing key pairs, simply select from the available options under "Select a key pair"
- Click on the "Acknowledgement" followed by
- Click on Launch Instances.
If creating a key pair, simply select said option from the top dropdown.
Upon clicking Create a new key pair, the following dialog appears:
- Name this key pair something that will help identify it later.
- Download the .pem file created, in order to gain access to your VM. As the warning below states, this will be the only opportunity to do so.
- Click on Launch Instances.
View Instance Details
Once you have deployed an instance, from the EC2 console you can select your specific deployment and under it you will see several tabs providing details including Description, Status Checks, Monitoring and Tags. To accomplish this:
- Click Instances in the left panel.
All the instances in the region will be displayed.
- Select the instance for which details are to be viewed.
The details of that instance will be displayed at the bottom of the screen in different tabs.
The Description tab shows all the basic and general information of the instance.
The Status Checks tab displays the information on system status checks and instance status checks. Status Check Alarms are created from here:
Status Checks & Alarms
The Monitoring tab displays all the CloudWatch alarm and metrics in graph format.
The Tags tab will show all the tags that are associated with the instance. Add, edit or remove tags in this area.
