Cloud Deployment

For a deployment to Auto Insights cloud the following is required:

Network requirements: Domain Name
Use of anna.hyperanna.com is recommended for a cloud deployment.

If needed, a human-readable domain name familiar to your end users can be accommodated (e.g. yourcompany.hyperanna.com). This option will require provision of an SSL Certificate for the selected Domain Name.

This domain name should point to the Auto Insights Hosted VM on the Cloud.

Network requirements - whitelists

Front end - from the end users’ workstation:

Cloud Deployment: Data Source Options

With a Auto Insights cloud deployment there are three options:

1: On-Premise Database

Auto Insights can connect to databases from a range of vendors in the client ecosystem.
Auto Insights' NAT protected IP address will need to be whitelisted.

The following database information will need to be provided to Auto Insights:

  • Database type

  • Database server name / URL / IP

  • Port

  • Database schema name

  • Username & password with read access(Additionally, write access is required if data transformation needs to be done by Auto Insights)

  • Names of the table(s) or view(s) to be used by Auto Insights

Supported On-Premise Databases

For a full list of supported databases, please refer to this list.

2: Cloud database:

Auto Insights can connect to the client’s Cloud database. Auto Insights' NAT protected IP address will need to be whitelisted

The following database information will need to be provided to Auto Insights:

  • Database type

  • Database server name / URL / IP

  • Port

  • Database schema name

  • Username & password with read access(Additionally, write access is required if data transformation needs to be done by Auto Insights)

  • Names of the table(s) or view(s) to be used by Auto Insights

Supported On-Cloud Databases

For a full list of supported databases, please refer to this list.

3: .csv files

.csv or zipped .csv files can be uploaded to Auto Insights.

Note: The delimiter used in the flat file must be unambiguous and must not clash with data values and column names. We recommend putting double quotes around all values.

For all options, we suggest a Data Guide describing the meaning of each of the columns in the data, and an overview of the subject matter, ought to be provided.

There are benefits to connecting to a database and not a flat file:

  • Reuse database views containing business logic and data transformation logic

  • Speed up exploration and consumption of additional data for new use cases

  • Automate data refresh and eliminate effortful and delayed manual extraction

  • Connecting to the data source of truth reduces risk of data integrity issues

Unstructured data is currently not supported.

For further detail on loading datasets via flat file see data preparation.

Cloud Deployment: Email service requirements

In order to support functions including sharing of Missions summary, and any other future email-based features of Auto Insights, the following is required:

Where emails will be coming from anna@hyperanna.com, the hyperanna.com domain should be whitelisted on the email server so that Auto Insights' replies are not filtered incorrectly or placed in spam.

From the Auto Insights VM:

  1. Enable outbound access to smtp.gmail.com on port 587

  2. Enable outbound access to imap.gmail.com on port 995

Alternatively, emails can be set up to come from anna@client.com. In this case, Auto Insights will require access to the nominated email account to access the client email server, and the Auto Insights VM will require access to the client email server.

Auto Insights' IP address will need to be whitelisted for access to the client email server.

Email Security for Cloud and On-Premises Deployment

Email encryption: Auto Insights supports email transfer through an encrypted channel. Auto Insights does not currently support email content encryption.

Client data

Client data (your organisation’s data) is segregated into different files - meaning a client’s data will not exist in the same file as a different client, and is protected by:

  • User access control in Auto Insights

  • O/S user security using SSH public key (and not password)

  • VM security, firewall security, and network security Client data files are not encrypted.

Access control data

Access control data such as user logins and passwords are logically segregated in the Auto Insights database. This is secure because passwords are one-way hashed - meaning that no-one within or outside Auto Insights can see the password.

The database does not contain any client data nor personally identifiable data except the username and organisation name.

The database contains metadata for the client datasets to be used in Auto Insights.

Access control data other than passwords are not encrypted.

Access control

User access rights are controlled through Auto Insights' Admin Portal feature. The controls can be at the user-, group-, and organisation level, and can be applied to data down to the row level.

Did this answer your question?