Partek Flow Documentation

Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Click on EC2

Switch to the region intended intended to deploy Partek Flow. This tutorial uses US East (N. Virginia) as an example. 

...

Click the Select button next to Ubuntu Server 16.04 LTS (HVM), SSD Volume Type - ami-f4cc1de2

For the next step denoted Choose an Instance Type, the selection depends on your budget and the size of the Partek Flow deployment. We recommend m4.large for testing or cluster front-end operation, m4.xlarge for standard deployments, and m4.2xlarge for alignment-heavy workloads with a large user-base. See the section AWS instance type resources and costs for assistance with choosing the right instance. In most cases, the instance type and associated resources can be changed after deployment, so one is not locked in to into the choices made for this step.  For the step  

On the Configure Instance Details page, make the following selections:

Set the number of instances to 1. An autoscaling group is not necessary for single-node deployments

...

DNS hostname: change this to yes as internal dns DNS resolution may be necessary depending on the Partek Flow deployment

...

Make sure the DHCP option set is set to the one created above. If it is not, right-click on the row containing Flow-VPC and select Edit DHCP option sets.

...

Note: For multi-node Partek Flow deployments or instances where you would like Partek to manage AWS resources on your behalf, please see Partek AWS support and set up an IAM role for your Partek Flow EC2 instance. In most cases a specialized IAM role is unnecessary and we only need instance ssh keys.

Shutdown behaviorbehaviour: Stop

Enable termination protection: select Protect against accidental termination

...

EBS-optimized instance: Make sure Launch as EBS-optimized instance is enabled. Given the recommended choice of a an m4 instance type, EBS optimization should be enabled at no extra costscost

Tenancy: Shared - Run a shared hardware instance

...

The AWS console will suggest this server not be booted from a magnetic volume. Since there is not a lot of IO on the root partition and reboots are will be rare, choosing Continue with Magnetic will reduce costs. Choosing an SSD volume will not provide substantial benefit but it it OK if one wishes to use an SSD volume. See the EBS Volumes section for more information.

...