Create and Connect to a Database

Once you have set up an account, you can create and connect to your first database.

Create Database

To create your first database, navigate to the Accelerator Home page, select Add Database, and follow the instructions in the Accelerator UI. Be sure to pick the database name and password you are happy with, as they cannot be changed.

Note that when selecting the region and availability zone for the database, although you can pick any region from the list, it is advisable to pick one geographically closer to majority of your database users.

IP Address Options

When creating a database, you will be asked to specify the IP addresses that are able to access the database. Your options are as follows:

  1. To enter a range of addresses, choose Custom, enter the desired CIDR range, and select Add.

  2. To restrict access to your IP, choose My IP and select Add.

  3. To make the database publicly accessible , choose Public and select Add.

You can also choose to change the IP addresses later if needed. See Database Configuration_ for details.

EC2 Instance Types Supported By Accelerator

Vertica Accelerator currently supports the following Amazon EC2 instance types: i3.2xlarge, i3.4xlarge, i3.8xlarge, i3.16xlarge, i3en.2xlarge, i3en.3xlarge, i3en.6xlarge, i3en.12xlarge, i3en.24xlarge, i4i.2xlarge, i4i.4xlarge, i4i.8xlarge, i4i.16xlarge, and i4i.32xlarge. This instance family is storage-optimized for low latency and delivers high IOPS at a low cost. To learn more, visit AWS EC2 i3 Instances. To best match the database workload, you can later change the cluster size and/or the EC2 instance type as well.

Small Medium Large
Number of nodes 3 6 12
Data Caching 1x 2x 4x
Concurrency Low Moderate High

See Amazon EC2 Pricing for more information on the pricing for EC2 Instances.

Connect To Database

Vertica provides the flexibility of choosing your preferred client application or programming language for working with your database. To do so, your Vertica database (i.e., the primary subcluster) first needs to be connected with the preferred client driver.

Note: If you have configured your database’s autoscaling policy to Elastic Autoscaling, you will have to connect to the autoscaler DNS.

The connection process requires that you select a preferred connection method. In most cases, connecting with Vertica SQL (vSQL) is optimal for you to manage and administer a Vertica database. However, you also have the option of connecting via another interface as well. If you decide to connect using a preferred Partner Tool, review the full list of Vertica Technology Partner Integrations and follow their respective connection instructions on your Command Prompt.

Bring your own Network

You can leverage existing network infrastructure by using an existing VPC that already contains an Accelerator instance or by providing a CIDR block to build your cluster on the provided network.

Deploy Multiple Accelerator Databases on a Single VPC

To host multiple Accelerator databases on the same VPC, use the same VPC ID when creating a new Accelerator database. When you drop a database from a VPC containing multiple Accelerator databases, the VPC continues to run with the remaining Accelerator databases.

Deploy a cluster with a Custom CIDR range

Instead of a VPC, you can also provide a CIDR range and let Accelerator create the network. Nodes are created with the provided CIDR range. You must provide a CIDR range that is large enough to allocate 100 EIPs per database for large clusters or busy AWS accounts. If Accelerator creates the network, you must provide the following:

Bring Your Own Bucket

You can use an existing AWS bucket as communal storage for your new database. To use an S3 Bucket that already exists in the same AWS account as your Vertica Accelerator, submit a support ticket through the Micro Focus support portal.