Versions Compared

Old Version 7

changes.mady.by.user Tom Sheffield

Saved on

compared with

New Version 8

changes.mady.by.user Sean Hastert

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Your
  •  To create your second
instance will mirror the first. You will again log in to the AWS management console, and again select the EC2 Dashboard. Again, select Launch Instance.From the AWS Marketplace, type softnas in the search bar, and select the same AMI you previously selected.
Select the same instance size chosen for the first instance, which in this case is r5.2xlarge.
  • In Configure Instance Details, select the same VPC used for the first instance. However, you will need to make certain to select a separate Availability Zone. For instance if you selected a subnet with US East 1-a at the tail end, you would select a separate subnet for this instance, for example US East 1-b or c.

    • Image Removed

    •  Mirror the remaining settings in Instance Details to your original instance, including adding a second Network Interface.
     Next, we have the Add Storage step. If you added storage to your first instance from the Add Storage configuration step, then it is a good idea to mirror this setup on the second. If not, remember that adding storage at this point is entirely optional, and you can skip ahead by selecting Next:Add Tags.
    Again, adding tags is an entirely optional step, but if you did provide a tag for the first instance, it can be a quick and easy step to repeat the process, providing the same tags. This would in essence place the two new instances into the same searchable group.
    •  Next, it is time to configure a Security Group. Again, mirror the previous configuration. The default security group configuration will provide the needed ports for a simple highly available configuration. Remember it is always a good idea for security's sake to lock down traffic to a single IP or IP range.

    Image Removed

    •  Finally, we are ready to Review and Launch. Again, review the settings to verify your selections.
    •  click Launch.
     The Launch button will again bring up a prompt to select or create a key pair. While you can create another key pair, it may be easier if you only have to keep track of one for any given pairing of SoftNAS instances. If there is no compelling reason for a second key pair, select Choose an Existing Key Pair, and find the key pair used for the first instance. Check the box to confirm you have access to the key pair, and click Launch Instance.
     As with the first instance, you will then need to create a NAT, AWS Direct Connect, or a VPN if you wish to connect via browser. 
    Image Removed
    • SoftNAS instance for High Availability, please follow the instructions presented on AWS Getting Started - Create your SoftNAS Instances.

    •  The difference here will be your Availability Zone.  In the Network settings section, you need to ensure that you pick a subnet that is located in a different Availability Zone than what your first instance is in.
    •  FOR EXAMPLE: If the first SoftNAS instance you created was assigned a subnet that was located in us-east-2a, your second SoftNAS instance would need an assigned subnet that was located in us-east-2b or us-east-2c.


    Note

    Do NOT create a column on the second instance.  The storage pool on the second instance serves as a landing strip for the volume in a failover situation.


    •  The Availability Zone for the currently selected subnet is identified in the Subnet selection box.


    Info

    More information regarding VPC and Subnet creation can be found here.


    Note

    Don't forget to add a secondary network interface to this instance as well.  Instructions can be found here.


    Image Added