Skip to main content

Set your AWS region

Creating the subnet

First, we need to know what VPC to create the subnet on, so let’s describe the VPCs in the region where we want to create the Omni machines.
Output:
Note the VpcId (vpc-04ea926270c55d724). Now, create a subnet on that VPC with a CIDR block that is within the CIDR block of the VPC. In the above example, as the VPC has a CIDR block of 172.31.0.0/16, we can use 172.31.128.0/20.
Output:
Note the SubnetID (subnet-04f4d6708a2c2fb0d).

Create the Security Group

Output
Note the GroupId (sg-0b2073b72a3ca4b03). Allow all internal traffic within the same security group, so that Kubernetes applications can talk to each other on different machines:

Creating the bootable AMI

To do so, log in to your Omni account, and, from the Omni overview page, select “Download Installation Media”. Select “AWS AMI (amd64)” or “AWS AMI (arm64)”, as appropriate for your desired EC2 instances. (Most are amd64.) Click “Download”, and the AMI will be downloaded to you local machine. Extract the downloaded aws-amd64.tar.gz Then copy the disk.raw file to S3. We need to create a bucket, copy the image file to it, import it as a snapshot, then register an AMI image from it.

Create S3 bucket

Copy image file to the bucket

Import the image as a snapshot

Output:
Check the status of the import with:
Output:
Once the Status is completed note the SnapshotId (snap-056a7e086ecf7b452).

Register the Image

Output:
Note the ImageId (ami-07961b424e87e827f).

Create EC2 instances from the AMI

Now, using the AMI we created, along with the security group created above, provision EC2 instances: