...

For the next step called Choose an Instance Type the selection depends on your budget and the size of the 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 the choices made for this step.  

For "the step Configure Instance Details", make the following selections:Number

Set number of instances

...

to 1.

...

An autoscaling group is not necessary for single-node deployments

...

Purchasing option: Leave

...

Request Spot instances

...

unchecked. This is relevant for cost-minimization of Flow cluster deployments.

Network: If you do not have a VPC already created for Flow, click

...

Create new VPC

...

. This will open a new browser tab for VPC management. 

Use the following settings for the VPC:

Name tag: Flow-VPC

IPv4 CIDR block: 10.0.0.0/16

Select

...

No IPv6 CIDR Block

...

Tenancy: Default

Click

...

Yes, Create

...

. You may be asked to select a DHCP option set. If so, then make sure the DHCP option set

...

has the following

...

properties:

Options: domain-name = ec2.internal;domain-name-servers = AmazonProvidedDNS;

DNS resolution: leave the defaults set to yes

DNS hostname: change this to yes

...

as internal dns resolution may be necessary depending on the Flow deployment

...

Once created, the new Flow-VPC will appear in the list of available VPCs. The VPC needs additional configuration for external access. To continue, right click on Flow-VPC and select

...

Edit DNS Resolution

...

,

...

select

...

Yes

...

, and then Save. Next, right click the Flow-VPC and select

...

Edit DNS Hostnames

...

, select Yes, then Save. 

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.

...

Close the VPC management tab and go back to the EC2 management console.

Click the refresh arrow next to

...

Create new VPC

...

and select

...

Flow-VPC

...

.

...

Click Create new subnet

...

and a new browser tab will open with a list of existing subnets. Click

...

Create Subnet

...

and set the following options:

Name tag: Flow-Subnet

VPC: Flow-VPC

VPC CIDRs: This should be automatically populated with the information from Flow-VPC

Availability Zone: It is OK to let Amazon choose for you if you do not have a preference

IPv4 CIDR block: 10.0.1.0/24

Stay on the VPC dashboard tab and on the left navigation menu, click

...

Internet gateways

...

, then click

...

Create Internet Gateway

...

and use the following options:

Name tag

...

: Flow-IGW

...

Click Yes, create

...

The new gateway will be displayed as "detached". Right click on the Flow-IGW gateway and select "Attach to VPC", then select Flow-VPC and click "Yes, Attach"

...