Integrated Amazon S3 data

Important 

In Collibra 2024.05, we launched a new user interface (UI) for Collibra Platform! You can learn more about this latest UI in the UI overview.

Use the following options to see the documentation in the latest UI or in the previous, classic UI:

After you have synchronized the data, the integration of the Amazon S3 file system is completed.

Synchronization results

After synchronization, the resulting assets are in the domain that was specified in the crawler. By default, the assets get the Candidate status.

Warning Do not move the assets to another domain. Doing so may lead to errors during future synchronizations. This is a known limitation.

By default, the assets are shown in a plain list, but you can enable a multi-path hierarchy to show it in a tree structure. For the best result, we recommend that you use the following relations:

  1. Storage Container contains Storage Container
  2. Directory contains Directory
  3. Storage Container contains File
  4. Directory contains File Group
  5. File contains Table
  6. File Group contains Table
  7. Table contains Column

The following images shows the resulting hierarchical table.

Note In case of a partial synchronization caused by a temporary communication issue, the status of the assets that cannot be synchronized is set to Missing from source. During the next fully successful synchronization, the assets are removed or their previous status is restored, depending on their actual status in the source system.

Synchronized metadata per asset type

This table shows the metadata for each Amazon S3 asset type.

Asset type

Synchronized metadata

 Resource ID
S3 Bucket

URL

 00000000-0000-0000-0000-000000000258

Location

 00000000-0000-0000-0000-000000000203
File Storage contains/ is part of Storage Container 00000000-0000-0000-0001-002600000000
Directory

URL

 00000000-0000-0000-0000-000000000258
Storage Container contains/ is part of Storage Container 00000000-0000-0000-0001-002600000001
Directory contains/ is part of Directory 00000000-0000-0000-0001-002600000003
File Group URL 00000000-0000-0000-0000-000000000258
File Type 00000000-0000-0000-0001-002500000012
Document Size 00000000-0000-0000-0000-000000000259
Number of Files 00000000-0000-0000-0001-002500000001
Directory contains/ is part of File Group 00000000-0000-0000-0001-002600000004
File URL 00000000-0000-0000-0000-000000000258
File Type 00000000-0000-0000-0001-002500000012
Document Size 00000000-0000-0000-0000-000000000259
Storage Container contains/ contained in File 00000000-0000-0000-0000-000000007060
Table Glue database name 00000000-0000-0000-0001-000500000066
Glue table name 00000000-0000-0000-0001-000500000067

Description from source (available only if you integrate via Edge)
The description is taken from the Glue database directly. We look at the description for Table.

Note 

You can't integrate the descriptions from source directly.

  1. Create the crawlers and Glue database manually in AWS.
  2. Add the description for the Tables and the Comment for the Columns.
  3. In Collibra, complete the Glue database configuration field in the Edge S3 integration capability to integrate the Glue database.
  4. Run the synchronization.
  5. Run the synchronization with a dummy crawler.
    The crawler is not taken into account.
  1. In the Activities page, open the Synchronization Result dialog box for the S3 synchronization and check the name of the Glue database that was created.
    We create a new Glue database with every synchronization.
  2. In AWS, go to the Glue database name and add the description for the Tables and the Comment for the Columns.
  3. In Collibra, update the Edge S3 integration capability and complete the Glue database configuration field in the Edge S3 integration capability to integrate the updated Glue database.
  4. Run the synchronization again.
    The defined crawlers are no longer visible and are not taken into account.
 00000000-0000-0000-0001-000500000074
Table type (available only if you integrate via Edge) 00000000-0000-0000-0001-000500000008
File contains/ is part of Table 00000000-0000-0000-0001-002600000002
File Group contains/ is part of Table 00000000-0000-0000-0001-002600000005
Column Technical Data Type 00000000-0000-0000-0000-000000000219

Column Position (available only if you integrate via Edge)

Note The column position is not included when columns in the same table have identical names.

 00000000-0000-0000-0001-000500000020

Description from source (available only if you integrate via Edge)
The description is taken from the Glue database directly. We look at the comment for Column.

Note 

You can't integrate the descriptions from source directly.

  1. Create the crawlers and Glue database manually in AWS.
  2. Add the description for the Tables and the Comment for the Columns.
  3. In Collibra, complete the Glue database configuration field in the Edge S3 integration capability to integrate the Glue database.
  4. Run the synchronization.
  5. Run the synchronization with a dummy crawler.
    The crawler is not taken into account.
  1. In the Activities page, open the Synchronization Result dialog box for the S3 synchronization and check the name of the Glue database that was created.
    We create a new Glue database with every synchronization.
  2. In AWS, go to the Glue database name and add the description for the Tables and the Comment for the Columns.
  3. In Collibra, update the Edge S3 integration capability and complete the Glue database configuration field in the Edge S3 integration capability to integrate the updated Glue database.
  4. Run the synchronization again.
    The defined crawlers are no longer shown and are not taken into account.
 00000000-0000-0000-0001-000500000074
Column is part of/ contains Table 00000000-0000-0000-0000-000000007042