Add the AWS Bedrock AI capability
After you have created a connection to Amazon Bedrock in your Edge site, you have to add the AWS Bedrock AI capability to the connection.
Prerequisites
In your Collibra environment:
- You created and installed an Edge site.
- You have created a connection to Amazon Bedrock in your Edge site.
- You have a global role that has the Manage connections and capabilities global permission, for example, Edge integration engineer.
- When Status validation is activated for your Collibra environment, the synchronization does not complete if your integration's Default Asset Status is set to a status that is not assigned to the ingested asset types. For example, Implemented is no longer assigned to AI-related asset types. To avoid this, do one of the following:
- In your integration's Synchronization configuration or Metadata inbound tab, set Default Asset Status to No Status.
- In Collibra Console, set Status validation to False (default). This setting is in the Knowledge Graph Validation group of the Data Governance Center service configuration.
Steps
- Open a site.
-
On the main toolbar, click
→
Settings.
The Settings page opens. -
In the tab pane, click Edge.
The Sites tab opens and shows a table with an overview of your sites. - In the table, click the name of the site whose status is Healthy.
The site page opens.
-
On the main toolbar, click
- In the Capabilities section, click Add capability.
The Create capability page appears. - Select AWS Bedrock AI.
- Enter the required information.
- No Status (default, recommended): With the first synchronization, assets receive the first status listed in the Operating Model statuses. During a resynchronization, the status is not updated. For example, if you change an asset status from Candidate to Review before resynchronization, the status remains Review.
- Implemented: All assets get the Implemented status. Before you select this option, turn off Status validation in Collibra Console. Otherwise, the synchronization does not complete for asset types that no longer have the Implemented status assigned. For more information, go to the Data Governance Center service configuration options.
- Only complete the fields Save Input Metadata, Logging configuration, Memory (MiB), and JVM arguments on request of or together with Collibra Support.
- Only use Log level if your data source is a commercial JDBC offering. For more information, go to the Collibra Marketplace.
- Click Add.
The capability is added to the Edge site.
The fields become read-only.
| Field | Description | Required |
|---|---|---|
| Capability |
This section contains general information about the capability. |
|
|
Name |
The name of the capability. |
|
|
Description |
The description of the capability. |
|
| AWS Connection | The AWS connection to be used. |
|
| Save Input Metadata |
Select the checkbox if you want to save the input metadata extracted from the data source in ZIP files. The files can be useful for troubleshooting. Select this option only on request of Collibra Support. If this option is selected, you can download the files from the Synchronization Result dialog box once the synchronization activity is completed. |
|
|
Default Asset Status |
Define the status that assets need to receive during the integration synchronization. |
|
| Advanced Configuration |
These configuration options help when investigating issues with the capability. Important
|
|
|
Debug |
This field is ignored when you integrate metadata from Amazon Bedrock. An option to automatically send Edge infrastructure log files to Collibra Platform Self-Hosted. By default, this option is set to false. Note We highly recommend to only send Edge infrastructure log files to Collibra Platform Self-Hosted when you have issues with Edge. If you set it to true, it will automatically revert to false after 24h.
|
|
|
Log level |
Only complete this field on the request of or together with Collibra Support. An option to determine the verbosity level of Catalog connector log files. By default, this option is set to No logging. |
|