{"id":14873,"date":"2020-10-15T09:16:34","date_gmt":"2020-10-15T07:16:34","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/getting-started-with-exasol-a-multi-node-cluster-in-aws\/"},"modified":"2020-10-15T09:16:34","modified_gmt":"2020-10-15T07:16:34","slug":"getting-started-with-exasol-a-multi-node-cluster-in-aws","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/getting-started-with-exasol-a-multi-node-cluster-in-aws\/","title":{"rendered":"Getting started with Exasol \u2013 A multi node cluster in AWS"},"content":{"rendered":"

As of now, all the previous posts worked with the Community Edition of Exasol<\/a>. While that is great for getting started quickly (the Community Edition comes with all the features, except multi node support and a limit of 200GB of data) there are some limitations: Can you not really test how data is distributed across cluster nodes because there is only one. You do not have a real access to the operating system as the password for the root user is not given out<\/a>. My hope is to have more control over Exasol on AWS on the one hand, and being able to test the advanced features of Exasol in a real multi node cluster on the other hand. This post will mainly explain how the setup on AWS works, and the following posts will dig into the advanced features afterwards. <\/p>\n

<\/p>\n

When it comes to Exasol on AWS there are two deployment options:<\/p>\n

    \n
  1. Exasol’s Cloud Deployment Wizard<\/a><\/li>\n
  2. CloudFormation templates<\/a><\/li>\n<\/ol>\n

    We’ll be using Exasol’s Cloud Deployment Wizard for the scope of this post, as CloudFormation templates require a bit more knowledge. Before we head over to the deployment we need to create SSH-Keys in AWS, that will be used during the deployment and you will need them to connect to the nodes after everything is setup (very much the same as you know it from standard EC2 instances<\/a>). As key pairs belong to EC2, the option to create new ones is in the EC2 homepage:
    \n    \"\"<\/a>
    \n    \"\"<\/a><\/p>\n

    If you are on Windows and use Putty, switch the format to ppk, otherwise pem is fine:
    \n    \"\"<\/a><\/p>\n

    Make sure that you download the private key, if you lose that you will have no option to connect and you will need to start from scratch:
    \n    \"\"<\/a><\/p>\n

    Important: Before you try to deploy Exasol on AWS you need to subscribe to the Exasol offering in the AWS market place<\/a>. If you don’t do this, your deployment will fail:
    \n    \"\"<\/a><\/p>\n

    Having the key pair ready, head over to the Exasol Coud Deployment Wizard<\/a>, select AWS and choose your preferred AWS region<\/a>:
    \n    \"\"<\/a><\/p>\n

    We’ll go with the minimal configuration which is 1TB of raw data size and the basic settings.
    \n    \"\"<\/a><\/p>\n

    In the advanced configuration section we chabge a few settings:<\/p>\n