How to launch

EXAScaler Cloud application can be launched on AWS by navigating to the link below and selecting Continue to Subscribe.

Step by step guide

The steps below will show how to create a EXAScaler Cloud Cluster on AWS platform.

You will need a AWS account. Sign in.

Login to your account and go to the AWS Marketplace.

In the search box that appears, type "EXAScaler Cloud" and hit return. For some reason the completions that start to show up do not work as expected:

Click "Continue to Subscribe" button:

TODO

EXAScaler Cloud environment can be deployed as a standard AWS Cloud Formation template. And the installation wizard is used to deploy it. Installation wizard contains few configuration steps:

Stack name step contains unique name of EXAScaler Cloud environment:

Filesystem details:

• Filesystem name that will be mounted from clients as a distributed network resource.
• Configuration profile - we can choose predefined configuration profile or create a custom EXAScaler Cloud configuration. We provides three predefined profiles:
  - Small profile that will configure AWS Cloud resources to deliver 10TB capacity.
  - Medium profile that will configure AWS Cloud resources to deliver 50TB capacity.
  - Large profile  that will configure AWS Cloud resources to deliver 100TB capacity.
  DDN EXAScaler Cloud pricing is based on the number of CPU cores configured to meet the defined performance requirements.

Network and security step to configure AWS Virtual Network which enables resources to securely communicate with each other. And the subnets inside the virtual network where Bastion host and EXAScaler Cloud environment will be deployed to:

• SSH public key - name of an existing EC2 SSH key to enable SSH access to EXAScaler Cloud environment. Please select an item in the drop-down list.
• Virtual network name - existing VPC network where EXAScaler Cloud environment will be deployed to. Please select an item in the drop-down list.
• Public subnet name - name of an exisiting public subnet within the previously selected VPC network. Public subnet will be used to deploy bastion host instance.
• Private subnet address range - address range in CIDR notation for new private subnet within the previously selected VPC network. For example, 10.0.1.0/24. Private subnet will be used to deploy EXAScaler Cloud environment.
• Placement group - name of placement group to use. Optional, leave blank if not required.
  
• Cloud Watch - enable forwarding of EXAScaler Cloud logs to AWS Cloud Watch.
• Access to the filesystem - lockdown access to EXAScaler Cloud filesystem. Default can be accessed from anywhere.
• Access to the management web console - lockdown access to EXAScaler Cloud management web console. Default can be accessed from anywhere.
• Access to the management SSH console - lockdown SSH access to the bastion host. Default can be accessed from anywhere.

TODO