Home > Storage > PowerScale (Isilon) > Product Documentation > Cloud > APEX File Storage for AWS: Deployment Guide > Create EC2 instances for the cluster
You have now completed most of the work required to deploy a cluster in AWS. This section demonstrates how you create cluster nodes based on the AWS resources in the previous sections.
After you purchase APEX File Storage for AWS, you should be able to find the OneFS AMI image in the AWS Web Console by using the following steps:
Figure 17 is an example of OneFS AMI.
Use the following steps to create the cluster nodes with the AWS CLI.
> cd C:\json-files-template
aws ec2 run-instances --image-id <onefs_ami_id> --instance-type <onefs_instance_type> --placement GroupName=<cluster_name>-onefs-placement-group --network-interfaces NetworkInterfaceId=<internal_network_interface_id>,DeviceIndex=0 NetworkInterfaceId=<external_network_interface_id>,DeviceIndex=1 --region <aws_region> --iam-instance-profile Name=onefs-runtime-instance-profile --user-data file://user-data-node-1.json --block-device-mappings file://block-device-mappings.json --tag-specifications "ResourceType=instance,Tags=[{Key=cluster-name,Value=<cluster_name>},{Key=Name,Value=<cluster_name>-node<node_number>}]"
The following example shows how to create cluster node1, node2, node3, and node4.
Create first node - node1:
> aws ec2 run-instances --image-id ami-0ca314a9cafe48d5b --instance-type m5dn.12xlarge --placement GroupName=vonefs-cfv-onefs-placement-group --network-interfaces NetworkInterfaceId=eni-044ba549fc8239cec,DeviceIndex=0 NetworkInterfaceId=eni-0e21d2c270a4b64de,DeviceIndex=1 --region us-east-1 --iam-instance-profile Name=onefs-runtime-instance-profile --user-data file://user-data-node-1.json --block-device-mappings file://block-device-mappings.json --tag-specifications "ResourceType=instance,Tags=[{Key=cluster-name,Value=vonefs-cfv},{Key=Name,Value=vonefs-cfv-node1}]"
Create second node - node2:
> aws ec2 run-instances --image-id ami-0ca314a9cafe48d5b --instance-type m5dn.12xlarge --placement GroupName=vonefs-cfv-onefs-placement-group --network-interfaces NetworkInterfaceId=eni-0d947a68641d2db6f,DeviceIndex=0 NetworkInterfaceId=eni-02929b093d9cfaccc,DeviceIndex=1 --region us-east-1 --iam-instance-profile Name=onefs-runtime-instance-profile --user-data file://user-data-node-2.json --block-device-mappings file://block-device-mappings.json --tag-specifications "ResourceType=instance,Tags=[{Key=cluster-name,Value=vonefs-cfv},{Key=Name,Value=vonefs-cfv-node2}]"
Create third node - node3:
> aws ec2 run-instances --image-id ami-0ca314a9cafe48d5b --instance-type m5dn.12xlarge --placement GroupName=vonefs-cfv-onefs-placement-group --network-interfaces NetworkInterfaceId=eni-0371c901933c7ec28,DeviceIndex=0 NetworkInterfaceId=eni-03aa64794d62b76af,DeviceIndex=1 --region us-east-1 --iam-instance-profile Name=onefs-runtime-instance-profile --user-data file://user-data-node-3.json --block-device-mappings file://block-device-mappings.json --tag-specifications "ResourceType=instance,Tags=[{Key=cluster-name,Value=vonefs-cfv},{Key=Name,Value=vonefs-cfv-node3}]"
Create fourth node - node4:
> aws ec2 run-instances --image-id ami-0ca314a9cafe48d5b --instance-type m5dn.12xlarge --placement GroupName=vonefs-cfv-onefs-placement-group --network-interfaces NetworkInterfaceId=eni-09c1b9a66c08e969d,DeviceIndex=0 NetworkInterfaceId=eni-0bf4fee125a58dffe,DeviceIndex=1 --region us-east-1 --iam-instance-profile Name=onefs-runtime-instance-profile --user-data file://user-data-node-4.json --block-device-mappings file://block-device-mappings.json --tag-specifications "ResourceType=instance,Tags=[{Key=cluster-name,Value=vonefs-cfv},{Key=Name,Value=vonefs-cfv-node4}]"
Use the following steps to create the cluster nodes with the AWS Management Console.
For the volume 2, which is the first data volume of the cluster node, specify a custom Device name: xvda, and then choose your planned volume size, volume type. Then choose Yes for the Delete on termination field. This option can help you to delete the volume automatically when you terminate your cluster node in the future. Otherwise, choose No if you want to keep the volume, even after you have terminated the cluster node. Figure 25 is an example.
Note: while adding volumes with the device names of xvdb, xvdc, and so on, you might see a warning: “The selected AMI does not support this device name.” This is expected behavior, and you can ignore it.
Note: After instances creation, please enable EC2 termination protection and stop protection to protect your instances from unexpected deletion and stopping. Refer to AWS documentation for the details: Enable Termination Protection and Enable Stop Protection.