Installing Infoworks on AWS
Prerequisites
- Ensure that you have signed up for an AWS account.
- Use Amazon Linux 2 AMI to launch a new Virtual Machine. The AMI depends on what is available in your region, and what your corporate policy allows. If you are configuring Infoworks with Databricks then the region must match with the Databricks workspace you plan to use.
- The recommended minimum hardware requirements are 64 GB RAM, 8 vCPUs, and 200 GB disk space.
- Infoworks can be installed in the same VPC as that of the Databricks workspace, to allow access between Infoworks and Databricks clusters. This is the recommended setup. Ensure to create an inbound security group rule to allow all ingress traffic within the VPC network. For more details on configuring Infoworks with AWS Databricks, refer to the below section.
Prerequisites for Configuring Infoworks with AWS Databricks
- Ensure that you have signed up for a Databricks subscription. For signing up to Databricks, click here.
- Establish the connection between Databricks and your AWS account. For more details, see here.
- Ensure that the Databricks token is created for your workspace.
- Ensure that the Databricks workspace, Virtual Private Cloud (VPC), and the Infoworks VM are configured in the same region.
Prerequisites for Configuring Infoworks with AWS EMR
There are no separate pre-installation prerequisites for configuring Infoworks to run with AWS EMR. Proceed with installing Infoworks on AWS as documented below.
Installation Procedure
Step 1: Create an inbound security group rule to allow access to port 3000 for your whitelisted IPs. For more details, see here.
Step 2: Log in to the launched instance using SSH.
Step 3: Ensure that the hostname alias set for the Infoworks edge node instance has less than 63 characters. Postgres database has a character limit on hostnames. Run the following command to verify the same on the edge node:
xxxxxxxxxxhostname -AStep 4: Switch to root user using the following command, before you perform the following steps:
xxxxxxxxxxsudo su -Step 5: Switch the current working directory to /opt using the following command:
xxxxxxxxxxcd /optStep 6: To proceed with your Infoworks installation, create a user named infoworks and change to that user, using Step 7.
Step 7: Execute the following command:
xxxxxxxxxxsudo useradd -m -s /bin/bash -p $(openssl rand -base64 14) infoworksStep 8: Download the installation package by executing the following command:
- To use Amazon Linux 2, execute the following command:
xxxxxxxxxxwget https://iw-saas-setup.s3.us-west-2.amazonaws.com/5.5/iwx_installer_amazonlinux2_5.5.2.tar.gzStep 9: Untar the package by executing the following commands:
- For Amazon Linux 2, execute the following command:
xxxxxxxxxxtar xvf iwx_installer_amazonlinux2_5.5.2.tar.gzStep 10: Open configure.sh file in the directory.
Step 11: Configure the following parameters as described in the table, and then save the file:
| Field | Description | Details |
|---|---|---|
| IW_USER | The Infoworks user name. The value is infoworks. | This field will be auto-filled. |
| IW_PLATFORM | Name of the Infoworks platform. The value to be entered in this field is saas. | This field will be auto-filled. |
| IW_HOME | Location where Infoworks will be installed. The value is /opt/infoworks. | This field will be auto-filled. |
| IW_CLOUD_PROVIDER | Name of the cloud provider. | Enter aws. |
| IW_EDGENODE_IP | The IP address where Infoworks needs to be launched. | Provide the private IP of the virtual machine created. |
| METADB_MANAGED | This flag indicates whether the Mongo Installation is managed by Infoworks | If managed by Infoworks, enter Y (default). If managed by an external mongo, enter N. |
| METADB_USE_SRV | This flag indicated whether the MONGO_HOST corresponds to a DNS SRV record | Enter N (default) for No (prefix “mongodb://”), or Y for Yes (prefix “mongodb+srv://”) |
Step 12: Configure the following parameters as described in the table, and then save the file:
| Field | Description | Details |
|---|---|---|
| METADB_FORCE_DROP | This flag indicates whether the Installer should overwrite any existing Databases | Enter N (default) for No(the provided databases must be empty), or Y to allow dropping of databases. |
| MONGO_HOST | The Mongo Host URL to connect to. | Enter the Mongo Server or Seed DNS hostname (without prefix) |
| MONGO_USER | The Mongo User to authenticate as. | Enter a user that has at least read/write permissions over the databases mentioned.(defaults to Infoworks) |
| MONGO_PASS | The Password of the aforementioned MONGO_USER | Enter the Password of the MONGO_USER (defaults to Infoworks Mongo Password) |
| MONGO_DB | The Database Name that will store Infoworks MetaData | Enter a valid database name. |
| MONGO_QUARTZDB | The Database Name that will store Quartzio MetaData | Enter a valid database name. |
Step 13: Ensure that configure.sh and bootstrap.sh files have executable permissions. If the files do not have the permissions, run the following command:
xxxxxxxxxxchmod u+x configure.sh bootstrap.shStep 14: Using command prompt execute the following commands as root user:
xxxxxxxxxxsource configure.sh./bootstrap.shThis installs Infoworks in the required environment.
For details on how to navigate through Infoworks, see Navigating Infoworks.
Step 1: To access Infoworks user interface, go to http://IP-address:3000.
Step 2: The default credentials to access Infoworks are:
Username: admin@infoworks.io
Password: admin