Configure document sources for Unstructured augmentation

Learn how to configure document sources so Unstructured augmentation can access the files you want to process.

Configure a document source so that Unstructured augmentation can access files from a supported storage location for document processing.

Prerequisites

Before you begin, ensure you have met the following requirements:

You need an active Reltio tenant with Unstructured augmentation enabled.
A published extraction template must be available if you plan to use the source in a Unstructured extraction pipeline. A template is not required to configure a source for Unstructured search.
You have the required authentication details for the source you want to configure.
For AWS S3, you must have the Role ARN provided by Reltio, the bucket name, and the bucket region. Your AWS administrator must also update the bucket policy to allow that role to access the selected bucket.
For Google Cloud Storage, you must have the service account JSON credentials, bucket name, and location details.
For Google Drive, you must have the service account JSON key. The service account must have Viewer access to the folder or Shared Drive that contains the documents. For more information, see Set up Google Drive access for Unstructured augmentation.

To configure a document source

In Unstructured augmentation, select Sources from the left navigation pane. The Sources page is displayed.
Select + Configure Source to add a new source.
1. Select a source type: AWS S3, Google Cloud Storage, or Google Drive.
  If you plan to configure an AWS S3 source, update the bucket policy before you continue.
  In your S3, navigate to Buckets > your bucket > Permissions > Bucket policy. Update the bucket policy to allow this role to access the bucket. Replace <role-arn> with the Role ARN provided by Reltio and <bucket-name> with your S3 bucket name.
```
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "AllowAFUS3Role",
      "Effect": "Allow",
      "Principal": {
        "AWS": [
         "<role-arn>"
        ]
      },
      "Action": [
        "s3:GetObject",
        "s3:PutObject",
        "s3:ListBucket",
        "s3:DeleteObject"
      ],
      "Resource": [
        "arn:aws:s3:::<bucket-name>", "arn:aws:s3:::<bucket-name>/*"
      ]
    }
  ]
}
```
2. In the Source Configuration Name field, enter a unique name for the source.
3. For AWS S3 source type, confirm the Authentication Type and enter Role ARN, Bucket Region, and Bucket Name.
  
  Note: The IAM role you enter in Role ARN must have access to the selected AWS S3 bucket.
4. In the Account ID field, enter the bucket owner's AWS account ID. This is required only if the AWS S3 source is used by Unstructured search.
5. For Google Cloud Storage storage type, paste the service account JSON credentials into Service Account JSON, enter Bucket Name, and Location.
6. For Google Drive storage type, paste the complete contents of the service account JSON key into Service Account JSON.
  
  Note: Store the key securely. Paste it only into Unstructured augmentation, and don't share it through email, chat, or other unsecured channels.
7. Select Test Connection to verify that the source is accessible.
8. Select Save .

Result

The document source is configured. You can use the source when you create or configure a Unstructured extraction pipeline or create a knowledge base for Unstructured search.

Unify and manage your data

Configure document sources for Unstructured augmentation

Footer