Cloud Deployment

For a deployment to Hyper Anna’s 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. anna.yourcompany.com). This option will require provision of an SSL Certificate for the selected Domain Name.

This domain name should point to the Hyper Anna Hosted VM on the Cloud.

Network requirements - whitelists

Front end - from the end users’ workstation:

Cloud Deployment: Data Source Options

With a Hyper Anna cloud deployment there are three options:

1: On-Premise Database

Anna can connect to databases from a range of vendors in the client ecosystem.
Anna’s NAT protected IP address will need to be whitelisted.

The following database information will need to be provided to Hyper Anna:

  • 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 Hyper Anna)
  • Names of the table(s) or view(s) to be used by Anna

Supported On-Premise Databases

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

2: Cloud database:

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

The following database information will need to be provided to Hyper Anna:

  • 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 Hyper Anna)
  • Names of the table(s) or view(s) to be used by Anna

Supported On-Cloud Databases

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

3: Cloud - upload via CSV file.

Anna can also connect to a flat file uploaded to Hyper Anna’s Azure Secure Storage by the client.

Hyper Anna will provide a login for the client to use to conduct the upload.

Anna currently supports these data formats:

  • CSV
  • CSV in Zip

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 a PDF 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 email Anna, Share Insight, and any other future email-based features of Anna, the following is required.

Option 1 - email via anna@hyperanna.com. Questions from users can be sent to anna@hyperanna.com and replies will be returned to the sender’s email address. This is the preferred option.

The hyperanna.com domain should be whitelisted on the email server so that Anna’s replies are not filtered incorrectly or placed in spam.

Option 2 - Client email address managed by Anna (e.g.: anna@client.com)

Questions from users can be sent to anna@client.com and Anna’s replies will be sent to the sender’s email address.

Anna will require access to the nominated email account and access to the client email server.

Anna’s IP address will need to be whitelisted for access to the client email server.

Email Security for Cloud and On-Premises Deployment

Email encryption: Anna supports email transfer through an encrypted channel. Anna 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 Anna
  • 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 Anna database. This is secure because passwords are one-way hashed - meaning that no-one within or outside Hyper Anna 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 Anna.

Access control data other than passwords are not encrypted.

Access control

User access rights are controlled through Anna’s 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?