Skip to content

You are viewing documentation for Immuta version 2022.1.

For the latest version, view our documentation for Immuta SaaS or the latest self-hosted version.

Chapter 4 - Connecting Data

Audience: Data Owners and Data Governors

Content Summary: This page sets the context to create and manage data sources. There is an outline of best practices, a use case scenario, chapter objectives, and links to tutorials.

Prerequisites:

Introduction

You have your integrations installed, users set up, and Global Policies created, and you are ready to start creating data sources.

A data source is how Data Owners expose their data to other Immuta users. Throughout this process, the data is not copied. Instead, Immuta uses metadata from the data source to determine how to expose the data; a data source is a virtual representation of data that exists in a remote data storage technology.

When a data source is exposed, policies (written by Data Owners and Data Governors) redact and mask information depending on the attributes or groups of the user accessing the data. Once the data source is exposed and subscribed to, the data can be accessed across analytics and visualization tools with Immuta policies applied.

Best Practices: Connecting Data

  1. Two-way SSL configuration is the most secure configuration for a custom blob store handler endpoint.
  2. Although not required, it is recommended that all connections use SSL. Additional connection string arguments may also be provided.
  3. It is recommended that path not be used in the resource restrictions. Additionally, single-bucket source data is the only tested configuration. Athena databases with source data in multiple buckets may work, but would require that additional resources be specified in the below policy anywhere your-source is referenced.

Use Case Scenario

Use Case

This use case is presented throughout this chapter in a call-out to illustrate a specific Local Policy. The solutions presented can be adjusted to meet your specific needs.

A project manager wants access to her data sources to be more restrictive than the organization's compliance requirements suggest. Because these further restrictions do not need to be made globally, she should add Local Policies to her data sources.

Chapter Objectives

In this chapter, you will complete tutorials that demonstrate how to

  1. add data sources to your Immuta instance.
  2. properly manage your data sources.
  3. apply local policies to your data sources.

Chapter Contents

Concept Overviews: Each of these pages explains a concept and how it connects to other features in Immuta.

Tutorials: Each of these pages provides step-by-step instructions for using a feature in Immuta.

Policy as Code: API Reference Guides: These pages detail how to access Immuta through the API.