Exploring the options for Vertica Deployment

Vertica on Amazon Web Services
https://www.vertica.com/docs/latest/HTML/Content/Authoring/UsingVerticaOnAWS/UsingVerticaOnAWS.htm

Using Eon Mode
https://www.vertica.com/docs/latest/HTML/Content/Authoring/Eon/EonModeLandingPage.htm

Let us know if you have any questions!

Hi Jim,

Thank you for your response.
Consider the scenario where I do not have the access to AWS console, but given 4 EC2 instances. How could I install and Launch the Vertica instances (EON) from this? Is there a way to do this?

You have to install vertica manually : https://www.vertica.com/docs/10.0.x/HTML/Content/Authoring/UsingVerticaOnAWS/ManuallyDeployAWSVertica.htm
including the cluster creation ( https://www.vertica.com/docs/10.0.x/HTML/Content/Authoring/UsingVerticaOnAWS/FormingaCluster.htm )
and finally create the database using admintools :
https://www.vertica.com/docs/10.0.x/HTML/Content/Authoring/AdministratorsGuide/AdminTools/CreatingADatabase.htm - refers to the "Create an Eon Mode Database" chapter

Hi,
Thank you for the response. I had read that document. I am stuck at the step where launching an EC2 instance.
https://vertica.com/docs/10.0.x/HTML/Content/Authoring/UsingVerticaOnAWS/ConfiguringAndLaunchingAnInstance.htm
Configure EC2 Instances in AWS
Select the Vertica AMI from the AWS marketplace.
I do not have access to AWS Marketplace and AWS Console, so is there an alternative for this or only option is to get the access to console+AMI?

You do not need to rely on our AMIs on the AWS marketplace to deploy Vertica Eon. Though that's the most ideal way if you're on AWS since those AMI's have all the OS configurations, security groups (etc...) already set up for you.
 
But generally,

• Select EC2 instances (at least 3 for High Availability). Our supported instance list is here.
• Make sure the instances are in a VPC and in a subnet (create them if not available).
• Create an S3 Gateway Endpoint and optionally an Internet Gateway for your VPC.
• Create a Placement Group and use Cluster as the Placement Group Strategy
• Choose the storage/EBS volumes as you require for the Depot, Catalog and Temp. NVMe drives are the most optimal for the Depot (which are available on the i3's, amongst others). However, keep in mind that shutting down your instances would lose all data on these type of volumes (which should be okay for the Depot)
• Configure Security Groups as per here.
• Create a key pair to access your instances using SSH
• Launch your instances.
• Make sure your EC2 instances have read/write access to your S3 buckets by assigning IAM roles. This is required for the Eon Communal Storage.
• Create an empty S3 bucket which is what we'll use for the Eon Communal Storage.
   

Then:

• Format the EBS volumes as ext4 & mount your drives. One for Depot, Catalog and Temp each. Do this on all nodes. Follow guide here for reference.
• Set CPU C-State to 0 and P-State Turbo ON. Do this on all nodes. Follow instructions here.
• Now let's install Vertica RPM. Download and install the package on the instances. Do this on all nodes:

rpm -Uvh /path/to/vertica-10.0.1-0.x86_64.RHEL6.rpm

• Create a Cluster. Do this on any one node:

sudo /opt/vertica/sbin/install_vertica -s <hostlist> -i <key.pem>

• Fix any OS configuration errors that the installer outputs and then rerun the above command.
• Create an Eon Database. The communal storage location is the S3 bucket you created above. Do this on any one node:

admintools -t create_db -d <dbname> -s <hostlist> --shard-count=<#> --depot-path=<depot_path> --data_path=<data_path> --catalog_path=<catalog_path> --communal-storage-location=<s3_bucket> 

• Example:

admintools -t create_db -d dbname -s 172.31.14.97,172.31.0.124,172.31.6.154 --shard-count=12 --depot-path=/vertica/depot --data_path=/vertica/data --catalog_path=/vertica/catalog --communal-storage-location=s3://dbname-vertica/eon

• Your Eon database should be created now and ready to go!
• Don't forget to set the Temp directory:

vsql -c "CREATE LOCATION '/vertica/temp' USAGE 'TEMP' LABEL 'tempfiles';"

Hopefully, you can appreciate why there's AMIs & CFTs that does most of the above for you. For reference, you can also take a look at our CFTs here.
 
Documentation for Reference:
https://www.vertica.com/docs/10.0.x/HTML/Content/Authoring/UsingVerticaOnAWS/ConfigureYourNetwork.htm
https://www.vertica.com/docs/10.0.x/HTML/Content/Authoring/UsingVerticaOnAWS/InstallingAndRunningVerticaOnAWSTheDetailedProcedure.htm
https://www.vertica.com/docs/10.0.x/HTML/Content/Authoring/AdministratorsGuide/AdminTools/CreatingADatabase.htm#Create