Zadara Storage Cube
Amazon Web Services
See full video tutorials: http://my.zadarastorage.com
This document describes how to create your first Zadara Cube purchased at the AWS marketplace and connect your AWS account to Zadara Storage using DirectConnect.
This document is designed for an audience with a basic familiarity of AWS.
It should take most administrators about 10 minutes to complete the steps in this document.
- An AWS account.
Welcome to the Zadara Storage Cube registration page. Zadara Storage Cubes are available exclusively from the AWS Marketplace and are “fixed-capacity” versions of the Zadara Storage Virtual Private Storage Array (VPSA) that is available from the Zadara Storage website (www.ZadaraStorage.com). You will see some terminology relating to VPSA which can be interchanged with the Storage Cube.
- Purchase any Zadara Standard Cube from AWS Marketplace here
- Connect to the Cube and activate it
- Accept offered Direct Connect's Virtual Interfaces
- Setup a VPC routing
- Connect to your Storage Cube
1. Purchase and Connect to Zadara Storage Cube from AWS Marketplace
1.1 Connect to AWS Marketplace
1.2 Find Zadara Storage Cube fitting for your needs.
1.3 Click continue and select 1-click or Manual
1.4 Select VPC or create new VPC
2. Connect to the Cube and activate it
2.1 Check the IP address of your instance and instance ID in your EC2 management panel
2.2 Connect to the web interface of your instance via http(s)://<instance ip>
2.3 Ignore security warning and continue
2.4 Login using instance ID
2.5 Fill in the form as needed
2.6 Create the Cube
2.7 The Status of the cube is displayed and will show when the Cube will be ready
3. Accept offered Direct Connect's Virtual Interfaces
Zadara has created one or two new virtual interfaces in your account but for security reasons that connection will be inactive until you accept it. You should have a Virtual Private Gateway in your VPC. Your Zadara Cube instance should be in this VPC.
For more information on creating a Virtual Private Gateway: Create a Virtual Private Gateway in AWS
If you don’t see any pending interfaces make sure you are in the right region. The current region is always displayed in the upper right corner of the AWS console.
Select a Virtual Private Gateway (VGW) attached to your VPC. You can attach a VGW to the VPC on a later stage as well.
That’s your account connected to Zadara’s! Almost done.
4. Setup a VPC routing
If you don’t already have a VPC created you will need to create one now. A full discussion of the complexities of a VPC are out of scope for this document, see https://aws.amazon.com/documentation/vpc/ for details. We recommend using the VPC Wizard.
Once your VPC is setup you need to attach the VGW you created earlier to it -
Now you need to add this gateway to your VPC’s route table -
Enable Route Propagation for this VGW:
Check for route propagation to complete. Once it does your route table should look something like this -
That’s it! You’ve completed all of the one time setup tasks required to attach an instance to your new Storage Cube.
5. Connect to your Storage Cube
Congratulations! Now you should be able to connect to your VPSA / Cube using the following protocols.
*URL/IP address of the VPSA is only available from within the VPC
Connecting to VPSA / CUBE Management GUI
You can connect directly using a web browser from your ec2 instance or from a local machine using ssh tunneling
How To setup SSH tunneling to work on VPSA GUI from your laptop
5.1 Your Cube status will show your GUI URL
5.2 The GUI
See VPSA User Guide for detailed information
Attaching the Storage Cube to your Instance
How To Install iSCSI Initiator in Linux
How To Connect a Windows Server to a VPSA using CHAP
How to Mount an SMB Share in Ubuntu
How to mount an SMB share Share in Windows OS
How To create and attach a NFS share to a Linux Server
How to access NFS shares from Windows OS
Other Helpful Articles
How To enable MPIO and set multiple iSCSI sessions on Windows Server 2008 R2
How To setup Multiple iSCSI sessions and MultiPath on your Linux Cloud Server
Changing SMB Share Level Permissions in an Active Directory Environment