Back to Search AI connectors listThe Amazon S3 Connector allows seamless integration between Amazon S3 and Search AI, enabling the ingestion of files stored in Amazon S3 buckets into the Search AI platform. By connecting to an Amazon S3 account, users can retrieve and make their content available for intelligent search and analysis.
Specification
Details
Repository type
Cloud
Supported content
Files in buckets (.pdf, .txt, .ppt, .docx)
RACL support
No
Content filtering
Yes (Advanced Filters for paths and file extensions)
To integrate Search AI with the Amazon S3 account and ingest data from it, follow the steps listed below.
Generate an Access Key for the Amazon S3 account from which content is to be ingested.
After successfully connecting the Search AI connector to the Amazon S3 account, go to the Configuration tab and set up content synchronization. For immediate sync, use the Sync Now option and the Schedule Sync option to set up a scheduler to sync the content in the future.Upon sync, Search AI ingests all the files (in supported formats) from the buckets accessible to the user used to log into the connector. This content is then accessible to all the users of Search AI.
Paths is a filter that allows users to directly specify folder paths to sync. This enables the connector to sync only the specified paths, which improves sync performance and provides greater flexibility when syncing specific folders. Users can add multiple paths.Example: ftp.kore.d/web/web/korehome/kore_file.support/pdf/!!!note
The path should always start from the bucket name. In the above example URL, the bucket name is ftp.kore.d.
File Extensions is a filter that allows users to sync files based on specific extensions. During the sync process, users can choose to include only particular file types. This helps in limiting the sync to only the required file types.
Ensures that the connector syncs only the resources that the configured access token has permission to access. This helps maintain proper access control and improves security during the sync process.To enable this functionality, the connector requires permissions to identify the IAM user and its associated policies. The required IAM permissions are listed in the Prerequisites section above.