Immuta SaaS FAQs
Audience: All Immuta SaaS Users
Content Summary: This page provides an overview of what you can expect from your Immuta SaaS instance.
Connecting Data in Your Instance
Databases Running in Closed Networks
You need to authorize these IP addresses in your network firewall configuration to allow Immuta to connect:
- us-east-1: 18.104.22.168
- eu-central-1: 22.214.171.124
The only data handlers available in Immuta SaaS are
Immuta SaaS provides native integrations, which allow users to query data directly within the remote database with Immuta policies enforced. These native integrations can be enabled on the App Settings page.
Native Databricks SQL Analytics Integration: By enabling the Native Databricks SQL Analytics integration, users will be provided direct access to views in Databricks.
Native Redshift SQL Integration: By enabling the Native Redshift SQL Integration, users will be provided direct access to views in Redshift.
Native Snowflake SQL Integration: By enabling the Native Snowflake SQL integration, users will be provided direct access to views in Snowflake.
"What are the account requirements for using Databricks with Immuta SaaS?"
A Premium account for Azure and an Enterprise account for AWS is required, as the Cluster Policies feature is not available in the Standard Databricks offering. You must also have table access controls (table ACLs) enabled in your workspaces.
dbt Cloud Integration (Preview Feature)
The dbt Cloud integration allows Immuta to be connected to your dbt Cloud jobs so that updates run through dbt populate in Immuta. Once dbt and Immuta are connected and a job runs to update your database, that update will automatically be applied to your Immuta instance.
For a tutorial, see Connect Data Sources Using dbt Cloud Integration.
"How do I get back to the Cloud Portal?"
To return to the Cloud Portal, navigate to https://cloud.immuta.com.