Troubleshooting / FAQ

How does the Connector deal with symbolic links?

The Connector recognizes soft links as such and depending on your configuration traverses them. Hard links however, are not recognized as symbolic links by the connector.

Troubleshooting

S3 Access Denied

If the connector cannot access the S3 bucket, verify these items:

  • The bucket policy allows the Kendra index role to read objects in the bucket.

  • The connector credentials have write access to the bucket.

  • The bucket region matches the configured Region ID.

S3 Region Mismatch

If you see errors like PermanentRedirect or WrongRegion, ensure content.s3Content.regionId matches the bucket’s region.

STS Assume Role Issues

If the connector fails to assume a role:

  • Confirm the roleArn is correct and trusted by the base credentials.

  • Ensure the STS region is valid for the account.

  • Check session duration limits on the role if sessionTimeToLive is configured.

Kendra Rejects Large Documents

Amazon Kendra rejects inline documents larger than 5 MB. Enable Use S3 and set Content Size Limit below 5 MB to upload large documents to S3 instead.

Unable to access jarfile error (installation on Windows)

This error occurs when the installation path exceeds the maxium Windows path length of 260 characters. Ensure that the full path to bin\connector.bat does not exceed 260 characters.