Welcome to the ElasticDW documentation!
The ElasticDW documentation is organized by its available modules
- Console - The web application. This also is where initial access is setup
- CLI - The command line application.
- Terraform - The infrastructure as code interface using Terraform
- API - The REST API interface
You can navigate the docs by using the navigation sidebar on the left.
For an introduction to the architecture and terminology used by ElasticDW, read on…
ElasticDW is a managed Database-as-a-Service platform available for the public cloud. The product is used to create and maintain a customer’s data warehouse infrastructure. The current release supports Vertica on AWS.
The ElasticDW platform resources consist of the following components and terminology.
ElasticDW Service Core
The service core and its resources, represented by the blue outline above are hosted on elasticdw.com. This set of core resources include metadata, secure API gateways, secure logs and other storage & serverless cloud resources that comprise the engine of the managed service.
ElasticDW Customer Cloud
The ElasticDW Customer Cloud represented in the yellow outline above, encompasses cloud services and artifacts created to support the managed services provided by the Service Core. These will typically be located in the customer’s AWS Account, in a designated VPC and subnet. (Full 360 can also host this environment under a sub-account under our Master AWS account)
In addition the following main AWS resources will exist in the customer account:
- S3 buckets for Vertica EON mode, if chosen.
- CloudWatch Log Groups and Logs (Vertica Logs)
- Secure Cross Account IAM Role to facilitate the ElasticDW managed service functions.
- Physical resources created by Environments and Clusters described below.
A ElasticDW Environment groups clusters together, and provides a security scope tied to an associated environment token. This allows organizations to manage the clusters in a logical fashion, e.g. Development, Production, etc. The Environment is primarily metadata, and has a limited number of associated physical resources.
A ElasticDW cluster is created by the service core and are comprised of physical nodes created and configured by the managed service based on the specified configuration using one of the modules (Console, CLI, Terraform). These include EC2 instances, Load Balancers, Security Groups etc. and run in the Customer Cloud.
Tokens are used for authentication.
There are two kinds of token available - a master token, or an environment token. The difference is in the allowed scope. A master token, as the name implies allows management of all the environments and clusters. The environment token reduces the scope to a single environment that the token was generated for.
Tokens can be created in the Console or using the CLI
- All components: Deletion protection option for clusters (0.17)
- API - Create a cluster from a backup restore (0.16)
- Console, CLI, Terraform, and API - Bring Your Own License (0.15)
About Full 360
Full 360 has been a managed service provider for Vertica on AWS since 2008. We have been building, migrating and running data warehouse workloads, since 2007. Full 360 was the only AWS partner to demonstrate the feasibility of migrating the largest (at the time, a 100+ node) Vertica cluster to AWS.
Vertica is the most mature, most proven columnar, and award winning analytical database out there.
ElasticDW is a registered trademark of Full 360 Inc. Vertica is a registered trademark of Micro Focus and/or its affiliates. All other brands or product names are the property of their respective holders.