Auto Insights Cloud

Last modified: July 07, 2022

Cloud Deployment

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

Network Requirements–Domain Name
We recommend <region>.autoinsights.alteryxcloud.com for a cloud deployment. If needed, a human-readable domain name familiar to your end users can be accommodated (for example, yourcompany.autoinsights.com). This option requires the provisioning 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–Allowlists

Front end - from the end users’ workstation:

Cloud Deployment: Data Source Options

With an Auto Insights cloud deployment there are three options: On-Premises Database, Cloud Database, CSV Files.

On-Premises Database

Auto Insights can connect to databases from a range of vendors in the client ecosystem. Allowlist Auto Insights' NAT-protected IP address:

UK–20.117.221.132
US–20.69.129.11
SG–40.90.184.35
AU–52.187.224.60

Provide the following database information to Auto Insights:

  • Database type

  • Database server name / URL / IP

  • Port

  • Database schema name

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

  • Names of the tabled or views to be used by Auto Insights

Supported On-Premises Databases

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

Cloud Database

Auto Insights can connect to the client’s Cloud database. Allowlist Auto Insights' NAT-protected IP address:

UK–20.117.221.132
US–20.69.129.11
SG–40.90.184.35
AU–52.187.224.60

Provide the following database information to Auto Insights:

  • Database type

  • Database server name / URL / IP

  • Port

  • Database schema name

  • Username and 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.

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 effortfully and delayed manual extraction

  • Connecting to the data source of truth reduces the 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

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 no_reply@autoinsights.alteryx.com, the AutoInsights.alteryx.com domain should be allowlisted 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 . In this case, Auto Insights requires access to the nominated email account to access the client email server, and the Auto Insights VM requires access to the client email server.

Auto Insights' IP address will need to be allowlisted 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 organization’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 or personally identifiable data except the username and organization 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 organization level, and can be applied to data down to the row level.

 

Was This Page Helpful?

Running into problems or issues with your Alteryx product? Visit the Alteryx Community or contact support. Can't submit this form? Email us.