Getting started with AWS and Zadara -

 

zadara-horz.png

Getting Started With

Zadara

and

Amazon Web Services

craig@zadarastorage.com

This document describes how to create your first Zadara Virtual Private Storage Array and connect your AWS account to Zadara using DirectConnect.

Audience

This document is designed for an audience with a basic familiarity of AWS.

Time

It should take most administrators about an hour to complete the steps in this document.

Prerequisites

The Process

  1. Create a VSPA
  2. Connect your AWS account to Zadara’s AWS account
  3. Accept the new connection
  4. Setup a VPC and routing

First, Create a VPSA -

Login to Zadara Storage

0_z_home_page.png 1_login_zadara_storage.png 2_create_vpsa.png

Give your VPSA a name (you can’t change this later!) and a description.
Choose AWS as your cloud provider (it’s the default).
Choose the AWS region you want to use.
Choose the controller size you want to use, if you are just demoing Zadara pick Baby or Basic.
Pick at least three drives of the same size and type.
Make sure you check the “Enterprise Suite” option, that enables encryption and remote replication.
Click “Submit”!

3_create_vpsa.png

Great! While your VPSA is being built (usually takes < 5 minutes) let’s connect your AWS account to ours. If this is the first VPSA you’ve started a Zadara sales person might want to talk to you before the array is created. If you want to speed that process up just send an email to sales@zadarastorage.com and let us know what you’re working on.

Second, connect your AWS account to Zadara’s AWS account -

You only ever have to do this step once per AWS region. You will need your AWS account number for this step. To get it login to your AWS account, click your name in the right hand corner, then click “My Account”
0_get_acct_num.png

Your account number will be center top of the page -

1_got_acct_number.png

Now you need instruct Zadara to setup a connection. Send an email -

TO: support@zadarastorage.com
SUBJECT: New virtual connection for AWS account ‘insert your account number’ in ‘selected region’

During business hours setting up a connection generally only takes an hour, you will get an email from support when the connection is setup on our end.

Third, accept the new connection -

Zadara has created a new virtual interface in your account but for security reasons that connection will be inactive until you accept it. To accept the connection you first need to create a Virtual Private Gateway (VGW).

Login to your AWS account, browse to the VPC product. Make sure you are in the same region you created the VPSA in!

go_to_vpc.png
Then create your VGW -

create_vgw.png created_vgw.png

Now browse to the DirectConnect product -

direct_connect.png

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. As you can see in this screenshot I’ve setup my connection in Tokyo.

accept_interface.png

accept_vi.png

That’s your account connected to Zadara’s! Almost done.

Fourth, setup a VPC and 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.

It’s important that the RFC 1918 subnet range you select for your VPC doesn’t overlap with Zadara’s range. Zadara’s ranges for each region are detailed here -

US East–1: 10.10.1.0/24

US East–2: 172.31.240.0

US West: 172.31.224.0/22

Japan: 172.30.224.0/22

Dublin: 172.29.224.0/22

Australia: 172.29.224.0/22

Once your VPC is setup you need to attach the VGW you created earlier to it -

attach_vgw.png attach_vgw_final.png

Now you need to add this gateway to your VPC’s route table -

propagate_0.png propagate_1.png

It can take up to 15 minutes for route propagation to complete. Once it does your route table should look something like this -

propagated.png

That’s it! You’ve completed all of the one time setup tasks required to attach an instance to your new VPSA.

Next Steps -

Setting up your new VPSA

Creating an iSCSI block device

Creating a NFS volume

Creating a CIFS volume

Attaching an iSCSI LUN to a Windows instance

Attaching a niSCSI LUN to a *nix instance

Mounting an NFS volume to a *nix instance

Mounting a CIFS volume to a Windows instance

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.