Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Kendra] use of CUSTOM connector type not documented for create_data_source #4281

Closed
ssmails opened this issue Sep 24, 2024 · 3 comments
Closed
Assignees
Labels
closing-soon This issue will automatically close in 4 days unless further comments are made. documentation This is a problem with documentation. kendra p2 This is a standard priority issue response-requested Waiting on additional information or feedback. service-api This issue is caused by the service API, not the SDK implementation.

Comments

@ssmails
Copy link

ssmails commented Sep 24, 2024

Describe the issue

How is the type 'CUSTOM' defined here to be used ?
Can it be used to create all data sources that are currently present in kendra, but not listed explicitly here. Eg. redshift ?
or is its purpose different ?

response = client.create_data_source(
    Name='string',
    IndexId='string',
    Type='S3'|'SHAREPOINT'|'DATABASE'|'SALESFORCE'|'ONEDRIVE'|'SERVICENOW'|'CUSTOM'|'CONFLUENCE'|'GOOGLEDRIVE'|'WEBCRAWLER'|'WORKDOCS'|'FSX'|'SLACK'|'BOX'|'QUIP'|'JIRA'|'GITHUB'|'ALFRESCO'|'TEMPLATE',
    Configuration={

Per the docs link listed in this issue, it is not clear. Appreciate if docs are updated and example is provide for the same for create_data_source. What should be provided in replacement of the configuration object and the create_data_source input?

  1. For redshift (if it is supported via this mechanism or any other)
Configuration (dict) –
Configuration information to connect to your data source repository.

You can’t specify the Configuration parameter when the Type parameter is set to CUSTOM. If you do, you receive a ValidationException exception.

The Configuration parameter is required for all other data sources.

Links

https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/kendra/client/create_data_source.html

@ssmails ssmails added documentation This is a problem with documentation. needs-triage This issue or PR still needs to be triaged. labels Sep 24, 2024
@tim-finnigan tim-finnigan self-assigned this Sep 26, 2024
@tim-finnigan
Copy link
Contributor

Thanks for reaching out. The create_data_source command makes a request to the CreateDataSource API, so any improvements to the documentation would need to be provided by the Kendra team.

Generally we recommend using the Provide feedback links at the bottom of API pages to send feedback directly to the appropriate team, and any documentation updates would be reflected in SDK documentation. But we can also try reaching out to the service team internally for more information.

In the Kendra User Guide, I found this page on custom data source connectors: https://docs.aws.amazon.com/kendra/latest/dg/data-source-custom.html, but didn't see anything on Redshift specifically. I found an internal feature request for Amazon Kendra to add a native connector for Redshift, that doesn't have much activity but I could add your +1 and use case to that.

@tim-finnigan tim-finnigan added response-requested Waiting on additional information or feedback. p2 This is a standard priority issue service-api This issue is caused by the service API, not the SDK implementation. kendra and removed needs-triage This issue or PR still needs to be triaged. labels Sep 26, 2024
Copy link

github-actions bot commented Oct 7, 2024

Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.

@github-actions github-actions bot added the closing-soon This issue will automatically close in 4 days unless further comments are made. label Oct 7, 2024
@ssmails ssmails closed this as completed Oct 8, 2024
Copy link

github-actions bot commented Oct 8, 2024

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closing-soon This issue will automatically close in 4 days unless further comments are made. documentation This is a problem with documentation. kendra p2 This is a standard priority issue response-requested Waiting on additional information or feedback. service-api This issue is caused by the service API, not the SDK implementation.
Projects
None yet
Development

No branches or pull requests

2 participants