> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity.md). # Setup & Connectivity Setup & Connectivity defines the complete process to establish and configure connections to data sources securely and efficiently. It covers all required prerequisites, including driver setup, network access, user permissions, environment configuration, and credential management. This process enables reliable metadata extraction through crawling and data profiling to support accurate data governance. **Key Features:** * Whitelisting IP addresses and ports to ensure secure and uninterrupted connectivity. * Assigning necessary permissions to service accounts for metadata crawling, profiling, and lineage building. * Configuring environment-specific variables to manage multiple deployment contexts such as production or staging. * Using secure credential managers like OE Credential Manager, AWS Secrets Manager, HashiCorp Vault, or Azure Key Vault for encrypted, real-time credential access. * Creating and validating connectors, then saving configurations to enable ongoing metadata extraction. * Extracting metadata including schema information, tables, columns, views, stored procedures, and other metadata objects through crawling. * Collecting statistical data about the contents of tables and columns via profiling to support data governance and quality assessment. *** Copyright © 2025, OvalEdge LLC, Peachtree Corners GA USA --- # 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.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity.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.