Fast Track Workshop

• First, we need to build an s3 bucket for our communal storage, and we need a key pair file.
o S3 page – build an S3 page – build an s3 bucket
▪ Bucket name needs to be unique
o Make a note of the name of their S3 bucket.
o EC2 console – “Key Pairs”
• -Go to : https://aws.amazon.com/marketplace
• Search for “Vertica”

• Describe the various options returned

o Vertica BYOL (Bring Your Own License) – traditional Vertica implementation. You can use
the community edition license, if necessary. Eon or Enterprise mode.
o Vertica By the Hour – exactly what it sounds like.
o You can find details on each by clicking on the option
o Amazon Linux is cheaper than Red Hat Linux
• Choose “Vertica BYOL, Amazon Linux”
• Describe some of the features of the page, including pricing, links to resources, and
configuration options available
• Click on “Continue to Subscribe”
• Sign in (if required)
o You need a IAM user name
o You need an Account ID
• Here, you can view the license agreement. The CE license allows for up to 1 terabyte of data,
and up to 3 nodes.
• “click accept the terms” if you have not already done so
• Click on “Continue to Configuration”
• For “Delivery Method”, choose “CloudFormation Template”
o An AMI is an “Amazon Machine Image” and tells AWS how to configure an individual
node, or nodes.
o A CloudFormation Template can utilize AMIs, but also can be used to configure the VPC
and the state of the cluster itself.
• Choose “Management Console with 3-node Eon Cluster”
o There are other options here as well
o You can create an older version if you need to
• Pick a region
o You can read the release notes if you like
• Click “Continue to Launch”
o Review the settings you’ve chosen
• Choose “Launch CloudFormation”
• Click “Launch”
 Create Stack
• Click “Next”
• Enter a stack name “Verticaworkshop-MMDDYYYY” (e.g., “Verticaworkshop-11202020”)
o If you ran into an issue the first time, the Stack name will already exist from the prior
attempt, and this name will now need to be unique – (add a “b” to the end, or
something)
• Database name “verticadb” is perfectly OK
• Communal Storage –
o The root path of this must already exist
o Name is s3://verticaworkshop/communalMMDDYYYY
• Password – can NOT be “dbadmin” – set it to “vertica”
• Instance type set to “c5.4xlarge”
• MC Password – set to “vertica”
• Key Pair – choose your key pair
o This must already exist
o The key pair must exist in the same region
o You can create one, advance this page, and then come back and it will refresh with it
available
• EC2 type for Management Console for “c5.large”
• CIDR Range of 0.0.0.0/0 is no longer valid
o Try “44.0.0.0/0”
• Pick an availability zone (it doesn’t matter which one)
• Pick “Yes” under “Accept Terms and Conditions”
• Click “Next”
• Click “Next”
o Review everything
o Check “I acknowledge that AWS …”
• Click “Create Stack”
• Wait 10 minutes
Creation Complete

Slide presentation
Verify was good

• Click “outputs”
• Click the link for the MC
o Or open in new tab
o Click “advanced”
o Click “proceed”
• Uidbadmin
• Vertica
Security Questions and change your password
Logout and log back in with new password