> ## Documentation Index
> Fetch the complete documentation index at: https://support.entegrata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Understand connections and how they link Entegrata to your data sources

## Overview

Connections represent Entegrata's link to your data sources. Each connection securely stores authentication credentials and defines default collection settings for all resources within that data source.

## Key Concepts

### What is a Connection?

A **Connection** provides the secure bridge between Entegrata and a data source (database, API, file system). Each connection includes:

<ResponseField name="Authentication" type="credentials" required>
  Secure credentials (username/password, API keys, tokens) used to access your data source
</ResponseField>

<ResponseField name="Connection Parameters" type="configuration" required>
  Technical details needed to reach your data source (host, port, database name, API endpoint)
</ResponseField>

<ResponseField name="Collection Schedule" type="schedule">
  Default schedule that determines when resources collect data (can be overridden per resource)
</ResponseField>

<ResponseField name="Status" type="enum" required>
  Current state of the connection:

  * **Active** - Connection is operational and resources can collect
  * **Inactive** - Connection is paused; no data collection occurs
</ResponseField>

### Connection Lifecycle

<Steps>
  <Step title="Creation">
    Add a new connection by providing data source type and authentication details
  </Step>

  <Step title="Discovery">
    Entegrata automatically discovers available resources (tables, views, endpoints)
  </Step>

  <Step title="Configuration">
    Set connection-level collection defaults (schedule, throttling, status)
  </Step>

  <Step title="Active Use">
    Resources collect data according to configured schedules
  </Step>

  <Step title="Maintenance">
    Update credentials, adjust settings, or troubleshoot issues as needed
  </Step>

  <Step title="Deletion">
    Remove connection when no longer needed (preserves collected data)
  </Step>
</Steps>

<Info>
  Each data source type has specific authentication requirements and available connection parameters.
</Info>

## Connection vs. Resources

It's important to understand the relationship:

| Aspect             | Connection                              | Resource                        |
| ------------------ | --------------------------------------- | ------------------------------- |
| **Authentication** | Stored at connection level              | Inherited from connection       |
| **Schedule**       | Default for all resources               | Can override connection default |
| **Discovery**      | Discovers all resources                 | Discovered within connection    |
| **Enable/Disable** | Determines if any resources can collect | Only affects specific resource  |

## Authentication Methods

### SQL Authentication

Username and password-based authentication for SQL databases:

* Standard login credentials
* Password expiration tracking
* Connection string parameters

### Windows Authentication (coming soon)

Domain-based authentication for on-premise SQL Server:

* Uses Windows domain credentials
* No password required (trusted connection)
* Requires domain connectivity

### API Keys and Tokens

Token-based authentication for cloud APIs:

* API keys for various services
* OAuth tokens for various platforms
* Bearer tokens for REST APIs

### Azure Entra ID (Managed Identity)

Passwordless authentication for Azure-hosted environments:

* No credentials required — authentication is handled by your Azure tenant
* Uses the managed identity assigned to the hosting environment
* Recommended for Azure-hosted data sources

### Azure Entra Service Principal

Application-based authentication for Azure services:

* Requires Tenant ID, Client ID, and either a Client Secret or Client Certificate from an Azure AD app registration
* Credentials must be rotated before expiration
* Use when Managed Identity is not available

## Connection Settings

### Collection Schedule

Determines when resources in this connection collect data:

* **Interval-based**: Regular time intervals (minutely, hourly, daily)
* **Time-based**: Specific times (e.g., "Daily at 2:00 AM")

<Tip>
  Individual resources can override the connection's default schedule.
</Tip>

### Throttle Profile

Controls collection speed to manage source system load:

* **Safe** - Slower collection to reduce impact on source systems (least resource intensive)
* **Standard** - Normal collection speed for most use cases (default)
* **Faster** - Faster collection for time-sensitive data (medium resource intensive)
* **Fastest** - Fastest collection from read replicas (most resource intensive)

### Secret Expiration

Track when authentication credentials expire:

* Set expiration date for passwords and API keys
* Receive notifications before expiration
* Plan credential rotation in advance

## Connection Status

### Active

* Collection is allowed
* Resources can collect according to schedule
* Discovery runs automatically every 3 hours

### Inactive

* Collection is paused
* All resources stop collecting (even if individually enabled)
* Discovery does not run

<Warning>
  Setting a connection's collection status to Inactive pauses ALL resource collection within that connection, regardless of individual resource settings.
</Warning>

## Getting Started

<CardGroup cols={2}>
  <Card title="Creating Connections" icon="plus" href="/data/collector/connections/creating-connections">
    Step-by-step guide to add a new data source connection
  </Card>

  <Card title="Viewing Connections" icon="eye" href="/data/collector/connections/viewing-connections">
    Browse and search your configured connections
  </Card>

  <Card title="Editing Connections" icon="pen" href="/data/collector/connections/editing-connections">
    Update credentials and connection settings
  </Card>

  <Card title="Collection Settings" icon="gear" href="/data/collector/connections/collection-settings">
    Configure schedules and collection behavior
  </Card>
</CardGroup>

## Next Steps

Once your connection is created:

<Steps>
  <Step title="Discovery">
    Wait for automatic discovery or trigger it manually to find resources
  </Step>

  <Step title="Configure Resources">
    Enable the specific tables, views, or endpoints you want to collect
  </Step>

  <Step title="Monitor Jobs">
    Track collection execution and performance
  </Step>
</Steps>

<CardGroup cols={2}>
  <Card title="Managing Resources" icon="table" href="/data/collector/resources/overview">
    Configure individual resources within your connection
  </Card>

  <Card title="Discovery" icon="magnifying-glass" href="/data/collector/discovery/overview">
    Learn how Entegrata discovers resources
  </Card>
</CardGroup>