Uploaded image for project: 'Solution Center'
  1. Solution Center
  2. SOL-377

EXASOL on AWS: Getting Started (Single Node, AWS Marketplace)

    XMLWordPrintable

    Details

    • Type: How To
    • Status: Published
    • Affects Version/s: EXASolution 5.0.15
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Solution:
      Hide

      You can easily install an Exasol Single Node database through the AWS Marketplace or AWS Console.

      • AWS Marketplace - This is a 1-Click launch. This helps you quickly install an Exasol Single Node database with preloaded configurations such as Instance Type, VPC Setting, and so on. 
      • AWS EC2 Console -  Installation of  Exasol Single Node from the EC2 console allows you to manually configure or select the desired VPC, Storage, Security Groups based on your requirements.   

      Installing Exasol from AWS Market Place (1-Click Launch)

      To install Exasol on AWS using 1-Click Launch, you can follow these steps: 

      1. Open AWS Marketplace and log in to your AWS account.
      2. In the search bar search for Exasol
      3. Click Exasol Analytic Database (Single Node and Cluster, Community Support)
      4. Click Continue to Subscribe
      5. You will see the Launch on EC2 page with the preloaded configurations for Region, EC2 Instance Type, VPC Settings, Security Groups. You further make changes to these configurations by selecting the options listed in their respective drop-downs. 
      6. Once you have reviewed the configurations, click Launch with 1-click
      7. The Exasol database instance is initiated and the progress can be viewed in the EC2 Console. 

      A Public IP address is automatically assigned. You can use this IP address to access the database once the instance is running through EXAoperations Console. For more information on launching the instance, see Launching Instance.

      When launching EXASOL through the AWS Marketplace no drives are initially attached to you database instance.
      In this case data is stored in a 50GiB area located in the root volume.

      For operational use we recommend to launch EXASOL through the AWS console and attach EBS volumes as described in the next section. 
      However, you may also start the instance through "1-Click-Launch" and attach EBS volumes later, but before you finalize the database configuration using the EXASOL web frontend.

      Installing Exasol from EC2 Console

      If you are installing Exasol from the AWS Console, make sure you have read the Preparation section. Installing and configuring Exasol single node on AWS includes the following steps: 

      1. Login to AWS
      2. Select AMI
      3. Select Instance Type
      4. Configuring the Instance 
      5. Adding Storage
      6. Configuring Security Groups
      7. Launching Instance
      8. Logging to EXAoperation
      9. Connecting to EXAplus

      Step 1: Login to AWS

      Login to AWS if you already have an AWS account. If you don't have an AWS account, create one at http://aws.amazon.com by following the on-screen instructions. Next, at the top right corner, select the region where you want to install Exasol on AWS from the drop-down list.

      Step 2: Select the AMI

      1. In the AWS Console, select EC2
      2. In the EC2 Console, click Launch Instance.
      3. Select the Exasol AMI. 
        1. Click the AWS Marketplace tab and enter 'Exasol' in the search field. 
        2. Click the Select button next to Exasol Analytic Database (Single Node and Cluster,  Community Support) or Exasol Analytic Database (Single Node and Cluster, BYOL) based on your license. 

      Step 3: Select Instance Type

      The Choose Instance Type page lists all the instance type optimized for your Exasol AMI. Based on your requirements select the instance type. 

      As a rule of thumb, the RAM size of the selected instance should correspond to approximately 10-15% of your raw data. 
      Note

      For detailed Information on how to select an appropriate instance please refer to links provided in the corresponding section of the FAQ Solution document

      EXASOL supports all EC2 instances with >15GB Main Memory.
      We recommend that you use instance types of category r3,c4 or m4 with >30 GB main memory.

      If we assume that your raw data (uncompressed) is about 500 GB in size, the following instances could be a good choice:

      • r3.2xlarge, 8 vcores, 61 GB main memory*

      Please note:

      • The sizing "rule of thumb" used above may not be appropriate for your use case. Based on your specific use case, you may need more memory.
      • For more information on sizing please refer to: EXASOL Sizing and the corresponding section in the FAQ document on installation and configuration

      After you have selected the Exasol AMI, select the required instance type and click Next: Configure Instance Details

      Step 4: Configuring Instance

      In the Configure Instance Details page, you can configure the instance to suit your requirements. You can: 

      • Specify the number of instances you want to launch. 
      • Select the VPC to be used from the Network drop-down if you already have a VPC configured. If you do not have a VPC configured, you can create a new VPC by clicking the Create New VPC option. 
      • Select the Subnet to be used from the Subnet drop-down, choose a subnet for the availability zone. 
      • In the Auto-assign Public IP drop-down, choose Enable, if you want to access your database instance from the internet. 

      Note
      A single node instance cannot be started successfully if it is in the subnet range: 27.1.0.0/16. Make sure the VPC selected does not match this range. 

      Once you have all the configurations you need, click Next: Add Storage

      Step 5: Adding Storage

      Add storage to your instance based on your needs. Exasol recommends using EBS storage for fail-safe persistence.

      The data storage volume should be able to store the compressed data as well as index structures and space for temporary data.

      As a rule of thumb the disk space for a single node (therefore without data redundancy) should be approximately 0.7x of the amount of raw data that should be managed by the node.

      In our example: 500GB * 0.7 = 350GB. The attached storage should be therefore not smaller than 350 GB.

      For more information on sizing please refer to: EXASOL Sizing

      Additionally you have to attach a system volume of 200GB size.

       Therefore we add the following volumes:

      • A 200GB EBS volume (GP2 or better) that serves as the additional system volume. This volume has to be attached to /dev/sdb. 
      • A data volume of size 350GB (see sizing considerations above). The volume has to be attached to /dev/sdc.

      Click Next: Add Tags button. * Tags allow you to associate name-value pairs with an instance. Add any required tags. Click the *Next: Configure Security Group button.

      Step 6: Configuring Security Group

      A security group consists of the ports that are opened for communication and acts as a virtual firewall to control the inbound and outbound traffic. In the Configuring Security Group page, you can either create a new security group or use an existing security group from the Security group name drop-down list. 

      Exasol uses following ports for communication:

      • Port: 443 - for the web frontend 
      • Port: 8563 - for the database connection (via JDBC, ODBC, etc)

      If you are launching Exasol from the AWS console, the above-mentioned ports must be manually configured in the Configure Security Group page. 

      Click the Review and Launch button. The Review Instance Launch page is displayed. Review your instance details and click Launch. A key pair dialog box is displayed as shown below: 

      Configure your key pair and click Launch Instances. A Launch Status page is displayed. Click on View Instances to view the instance in the EC2 Console. 

      Step 7: Launching Instance 

      Once the instance is in running state, you can connect to it using the IP address or the DNS name displayed in the console. To launch the instance, follow these steps: 

      1.  Copy and paste the IP address or the DNA name of the instance in a browser. 
      2. You will receive a digital certificate to confirm. Once you have confirmed this, you will see the following screen: 

      1. Enter the following details: 
        1. License Server instance ID: This is ID under Instance ID Column in the EC2 Instances console. 
        2. EXAoperation Administrator: Enter the name of the EXAoperation Administrator. This user will be able to log in to the EXAoperation management front-end. 
        3. Confirm Password: Enter the password for the admin user. 
        4. EXASolution  Administrator: Enter the name of the EXASolution Administrator. This user is 'sys' database user. 
        5. Confirm Password: Enter the password for the 'sys' user. 
      1. Click Proceed, this will start the database initialization. This will take a few minutes based on the instance type and size. 

      After the database is successfully initialized, you will be automatically redirected to the EXAoperation login screen. 

      Step 8: Logging into EXAoperation 

      After the database is successfully initialized, you will be automatically redirected to the EXAoperation login screen on the browser. You can log in to EXAoperation using the username 'admin' and the password defined for this user. 

      The status of the Exasol instance is displayed green when all the configuration process is successfully completed. If the status is displayed yellow, then the database is still starting up. In this case, please wait a moment and refresh the page to see the updated status. 

      Note
       If you have selected Exasol Analytic Database (Single Node and Cluster, BYOL) AMI, then you need to upload your license. Select Software → License tab → License Upload. 

      Once the license is uploaded, you need to restart the database. 

      Step 9: Connecting to EXAplus

      You need to first download and install EXAplus, which is the standard SQL client from Exasol. You can download EXAplus from Exasol Download Section

      If you are connecting from outside AWS, make sure that the port 8563, which is Exasol's standard communication port is available. This can be changed in the security group configured. 

      Open EXAplus and log in with your Sys username and password, which you created in the previous step. 

       

      Show
      You can easily install an Exasol Single Node database through the  AWS Marketplace  or  AWS Console . AWS Marketplace - This is a 1-Click launch. This helps you quickly install an Exasol Single Node database with preloaded configurations such as Instance Type, VPC Setting, and so on.  AWS EC2 Console -  Installation of  Exasol Single Node from the EC2 console allows you to manually configure or select the desired VPC, Storage, Security Groups based on your requirements.    Installing Exasol from AWS Market Place (1-Click Launch) To install Exasol on AWS using 1-Click Launch, you can follow these steps:  Open  AWS Marketplace  and log in to your AWS account. In the search bar search for  Exasol .  Click  Exasol Analytic Database (Single Node and Cluster, Community Support) .  Click  Continue to Subscribe .  You will see the  Launch on   EC2  page with the preloaded configurations for Region, EC2 Instance Type, VPC Settings, Security Groups. You further make changes to these configurations by selecting the options listed in their respective drop-downs.  Once you have reviewed the configurations, click  Launch with 1-click .  The Exasol database instance is initiated and the progress can be viewed in the EC2 Console.  A Public IP address is automatically assigned. You can use this IP address to access the database once the instance is running through EXAoperations Console. For more information on launching the instance, see  Launching Instance . When launching EXASOL through the AWS Marketplace no drives are initially attached to you database instance. In this case data is stored in a 50GiB area located in the root volume. For operational use we recommend to launch EXASOL through the AWS console and attach EBS volumes as described in the next section.  However, you may also start the instance through "1-Click-Launch" and attach EBS volumes later, but before you finalize the database configuration using the EXASOL web frontend. Installing Exasol from EC2 Console If you are installing Exasol from the AWS Console, make sure you have read the  Preparation  section. Installing and configuring Exasol single node on AWS includes the following steps:  Login to AWS Select AMI Select Instance Type Configuring the Instance  Adding Storage Configuring Security Groups Launching Instance Logging to EXAoperation Connecting to EXAplus Step 1: Login to AWS Login to AWS if you already have an AWS account. If you don't have an AWS account, create one at  http://aws.amazon.com  by following the on-screen instructions. Next, at the top right corner, select the region where you want to install Exasol on AWS from the drop-down list. Step 2: Select the AMI In the AWS Console, select  EC2 .  In the EC2 Console, click  Launch Instance . Select the Exasol AMI.  Click the  AWS Marketplace  tab and enter 'Exasol' in the search field.  Click the  Select  button next to  Exasol Analytic Database (Single Node and Cluster,  Community Support)  or  Exasol Analytic Database (Single Node and Cluster, BYOL)  based on your license.  Step 3: Select Instance Type The Choose Instance Type page lists all the instance type optimized for your Exasol AMI. Based on your requirements select the instance type.  As a rule of thumb, the RAM size of the selected instance should correspond to approximately 10-15% of your raw data.  Note For detailed Information on how to select an appropriate instance please refer to links provided in the corresponding section of the FAQ Solution document EXASOL supports all EC2 instances with >15GB Main Memory. We recommend that you use instance types of category r3,c4 or m4 with >30 GB main memory. If we assume that your raw data (uncompressed) is about 500 GB in size, the following instances could be a good choice: r3.2xlarge, 8 vcores, 61 GB main memory* Please note: The sizing "rule of thumb" used above may not be appropriate for your use case. Based on your specific use case, you may need more memory. For more information on sizing please refer to:  EXASOL Sizing  and the corresponding section in the FAQ document on installation and configuration After you have selected the Exasol AMI, select the required instance type and click  Next: Configure Instance Details Step 4: Configuring Instance In the  Configure Instance Details  page, you can configure the instance to suit your requirements. You can:  Specify the number of instances you want to launch.  Select the VPC to be used from the  Network  drop-down if you already have a VPC configured. If you do not have a VPC configured, you can create a new VPC by clicking the  Create New VPC  option.  Select the Subnet to be used from the  Subnet  drop-down, choose a subnet for the availability zone.  In the  Auto-assign Public IP  drop-down, choose  Enable , if you want to access your database instance from the internet.  Note A single node instance cannot be started successfully if it is in the subnet range:  27.1.0.0/16 . Make sure the VPC selected does not match this range.  Once you have all the configurations you need, click  Next: Add Storage .  Step 5: Adding Storage Add storage to your instance based on your needs. Exasol recommends using EBS storage for fail-safe persistence. The data storage volume should be able to store the compressed data as well as index structures and space for temporary data. As a rule of thumb the disk space for a single node (therefore without data redundancy) should be approximately 0.7x of the amount of raw data that should be managed by the node. In our example: 500GB * 0.7 = 350GB. The attached storage should be therefore not smaller than 350 GB. For more information on sizing please refer to:  EXASOL Sizing Additionally you have to attach a system volume of 200GB size.  Therefore we add the following volumes: A 200GB EBS volume (GP2 or better) that serves as the additional system volume. This volume has to be attached to /dev/sdb.  A data volume of size 350GB (see sizing considerations above). The volume has to be attached to  /dev/sdc . Click  Next: Add Tags  button. *  Tags allow you to associate name-value pairs with an instance. Add any required tags. Click the *Next: Configure Security Group  button. Step 6: Configuring Security Group A security group consists of the ports that are opened for communication and acts as a virtual firewall to control the inbound and outbound traffic. In the  Configuring Security Group  page, you can either create a new security group or use an existing security group from the  Security group name  drop-down list.  Exasol uses following ports for communication: Port: 443 - for the web frontend  Port: 8563 - for the database connection (via JDBC, ODBC, etc) If you are launching Exasol from the AWS console, the above-mentioned ports must be manually configured in the  Configure Security Group  page.  Click the  Review and Launch  button. The Review Instance Launch page is displayed. Review your instance details and click  Launch . A key pair dialog box is displayed as shown below:  Configure your key pair and click  Launch Instances . A Launch Status page is displayed. Click on  View Instances  to view the instance in the EC2 Console.  Step 7: Launching Instance   Once the instance is in running state, you can connect to it using the IP address or the DNS name displayed in the console. To launch the instance, follow these steps:   Copy and paste the IP address or the DNA name of the instance in a browser.  You will receive a digital certificate to confirm. Once you have confirmed this, you will see the following screen:  Enter the following details:  License Server instance ID:  This is ID under Instance ID Column in the EC2 Instances console.  EXAoperation Administrator:  Enter the name of the EXAoperation Administrator. This user will be able to log in to the EXAoperation management front-end.  Confirm Password:  Enter the password for the admin user.  EXASolution  Administrator:  Enter the name of the EXASolution Administrator. This user is 'sys' database user.  Confirm Password:  Enter the password for the 'sys' user.  Click  Proceed , this will start the database initialization. This will take a few minutes based on the instance type and size.  After the database is successfully initialized, you will be automatically redirected to the EXAoperation login screen.  Step 8: Logging into EXAoperation   After the database is successfully initialized, you will be automatically redirected to the EXAoperation login screen on the browser. You can log in to EXAoperation using the username 'admin' and the password defined for this user.  The status of the Exasol instance is displayed green when all the configuration process is successfully completed. If the status is displayed yellow, then the database is still starting up. In this case, please wait a moment and refresh the page to see the updated status.  Note  If you have selected  Exasol Analytic Database (Single Node and Cluster, BYOL)  AMI, then you need to upload your license. Select Software → License tab → License Upload.  Once the license is uploaded, you need to restart the database.  Step 9: Connecting to EXAplus You need to first download and install EXAplus, which is the standard SQL client from Exasol. You can download EXAplus from  Exasol Download Section .  If you are connecting from outside AWS, make sure that the port 8563, which is Exasol's standard communication port is available. This can be changed in the security group configured.  Open EXAplus and log in with your Sys username and password, which you created in the previous step.   
    • Category 1:
      Plattform Support - EXASOL on AWS
    • Category 2:
      Cluster Administration - Installation

      Attachments

        Issue Links

        1. aws_ec2_configlogin.png
          aws_ec2_configlogin.png
          570 kB
        2. aws_ec2_instance.png
          aws_ec2_instance.png
          56 kB
        3. aws_ec2_storage.png
          aws_ec2_storage.png
          154 kB
        4. exaoperation_login.png
          exaoperation_login.png
          34 kB
        5. exaoperation-instance.png
          exaoperation-instance.png
          51 kB
        6. exaplus.png
          exaplus.png
          125 kB
        7. exaplus-connected.png
          exaplus-connected.png
          95 kB
        8. screenshot-1.png
          screenshot-1.png
          273 kB

          Activity

            People

            • Assignee:
              CaptainEXA Captain EXASOL
              Reporter:
              CaptainEXA Captain EXASOL
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: