Cloud Deployment
Auto Insights will be available at a URL of the form REGION.autoinsights.alteryxcloud.com. See Data Hosting for the currently available Auto Insights regions.
Optionally (recommended) a URL of the form CUSTOMER-REGION.autoinsights.alteryxcloud.com can be provided to support single sign-on.
Network Requirements–Allowlist
Front end—from the end users’ workstation:
Data Source Options
With an Auto Insights cloud deployment, there are three options: On-Premises Database, Cloud Database, and 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
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
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.
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:
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.
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.
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 first name, last name, email address, 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
The AAI Admin Portal feature controls user access rights. The controls can be at the user-, the group-, and organization level, and can be applied to data down to the row level.