Unsupported Screen Size: The viewport size is too small for the theme to render properly.

AWS Lake Formation Bidirectional Collibra Integration

Published by: Collibra Marketplace
Latest version: 1.0.1
Released: April 12, 2022
Package Documentation
Community Offering

Your use of Community Offerings is subject to the Collibra Marketplace License Agreement. Read more.

Overview

AWS Lake Formation is a service that helps you set up, secure, and manage your data lake. The service makes it possible to discover, cleanse, transform, and ingest data into your data lake from various sources. You can also define highly customizable permissions at the database, table, or column level and then share controlled, secure access across analytic, machine learning, and ETL services.

Lake Formation capabilities

Lake Formation provides the following capabilities, either directly or through other AWS services, to reduce the time to deploy data lakes from many months to a few days or weeks:

  • Ingest and organize data.
  • Cleanse data.
  • Catalog and index data.
  • Analyze data.
  • Secure data at the database, table, or column level.
  • Grant data access to users from a central location.
  • Orchestrate data flows.

Lake formation services

AWS Lake Formation uses the following services:

  • Amazon Simple Storage Service (S3) buckets and paths as your data lake.
  • AWS Glue to orchestrate jobs with triggers to transform data using transforms.
  • AWS Identity and Access Management (IAM) to secure data using Lake Formation permissions to grant and revoke access.
  • The Data Catalog is the central metadata repository across several services.
  • Amazon Athena to query and explore data.
  • Amazon SageMaker to analyze data.
  • AWS Glue machine learning transforms to cleanse data.

This integration will map object tags to Collibra Standards, Domains, and Data Categories, but could well be extended and applied to any available asset type with little to no effort. If you wish to do that, please note that data access requesters will need to understand their access requirements and how those can be completed. Data access approvers will need to know exactly what granting that access entails.

The integration targets those customers who have or would like to have their data lakes in AWS and aim to deliver controlled and secure access to their data.

To receive support on this item, you can engage our Professional Services team or post any questions in the Data Citizens Community.

Media

More details

Release Notes
  • Updated the Spring Boot Starter Parent version to 2.5.12
  • Updated the Collibra Integration Library version to 1.1.5
Compatibility
  • Spring Boot Framework
  • Eclipse IDE
  • Collibra Cloud
  • Collibra 5.7.5 and newer
Dependency
  • Java Runtime Environment 1.8
  • Spring Boot Integration Library
  • Spring Boot Framework
License and Usage Requirements
  • Collibra Catalog

Release History

Version 1.0.0
March 21, 2022
Release Notes

Initial release:

This bi-directional Spring Boot integration consumes AWS Lake Formation entities and upserts the transformed data as assets to the Collibra platform. The other direction extract assets and synchronizes data with AWS.

Compatibility
  • Spring Boot Library
  • Eclipse IDE
  • Collibra Cloud
  • Collibra 5.7.5 and newer
Dependency
  • Java Runtime Environment 1.8
  • Spring Boot Integration Library
  • Spring Boot framework
License and Usage Requirements
  • Collibra Catalog

To receive support on this item, you can engage our Professional Services team or post any questions in the Data Citizens Community.

The following terms shall apply to the extent you receive the source code to this offering.

Notwithstanding the terms of the Binary Code License Agreement under which this integration template is licensed, Collibra grants you, the Licensee, the right to access the source code to the integrated template in order to copy and modify said source code for Licensee’s internal use purposes and solely for the purpose of developing connections and/or integrations with Collibra products and services.

Solely with respect to this integration template, the term “Software,” as defined under the Binary Code License Agreement, shall include the source code version thereof. Except with respect to the foregoing, all remaining terms of the Binary Code License Agreement shall apply to the license of integration template hereunder.

Reviews

Rating
Leave a review