...

Number of instances = 1. You do not need to create an autoscaling group for single-node deplaymentsdeployments.

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

1) DHCP options set : (ec2.internal is for us-east-1)

Click "Yes, Create". You may be asked to select a DHCP option set. If so, then make sure the DHCP option set you select or create has the following options:

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

http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_DHCP_Options.html

...

DNS resolution: leave the defaults set to yes

...

DNS hostname

...

: change this to yes and you may need internal dns resolution 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", then 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, select "Edit DHCP option sets" by right clicking on the Flow-VPC and select the correct VPC.

Now, close the VPC management tab and go back to the EC2 management console. Click the refresh arrow next to "Create new VPC" and select the Flow-VPC VPC.

Next, 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-Testing-Subnet

...