> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdc-admin/ldc-manage-data-sources-cp.md).
# Manage data sources
With Pentaho Data Catalog, you can process data from file systems and relational databases.
To process data from these systems, Data Catalog establishes a data source definition. This data source stores the connection information to your sources of data, including their access URLs and user credentials. The number of data sources you can add is determined by your license agreement.
**Note:** Refer to the product release notes for the latest supported versions.
The following data sources are supported:
{% hint style="info" %}
If you encounter an error while connecting to a data source, refer to the data source provider's documentation for more information about the error.
{% endhint %}
***
1 AWS S3, HCP, Minio, and VSP One data sources support **Skip SSL validation** when the data source uses a self-signed SSL certificate. Use this option only in non-production environments. To enable SSL validation, install user-provided SSL certificates into Data Catalog instead. For more information, see [Advanced configuration](/pdc-admin/ldc-advanced-configuration-ut_cp.md#install-user-provided-ssl-certificates).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.pentaho.com/pdc-admin/ldc-manage-data-sources-cp.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.