> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.4/settings/connector-settings.md).
# Connector Settings
Workspace-wide settings for individual connectors: the S3 staging area for Redshift, Modern Snowflake authentication, and Spark public IP discovery for firewall allowlists.
Under **Settings → Modules → Data → Connector Settings**, super users set options that apply to one kind of connector across the whole workspace. The page has three sections, **Redshift**, **Snowflake** and **Spark public IP discovery**. Select a section's header to open it. Opening one section closes the one that was open.
**Save** at the top right applies the changes in all three sections at once, and a message confirms the update. **Cancel** restores the saved values. If you leave the page with unsaved changes, Tellius asks whether to keep editing or discard them.
{% hint style="info" %}
These settings are for the workspace. The details of each connection, such as its host, user and password, are set when someone creates the connection on **Data → Connect**. To choose which connectors are offered at all, see [Connectors](/tellius-6.4/settings/connectors.md).
{% endhint %}
### Redshift
To read data from Amazon Redshift into Tellius, Tellius stages it in Amazon S3 first. This section sets that S3 staging area. The fields are named by the text shown in them while they are empty, and each has an information icon that explains it.
* **Enter Access Key ID:** the public identifier of the AWS credentials Tellius uses to reach the staging location. Use an IAM user or role that has only the S3 permissions it needs.
* **Enter Secret Access Key ID:** the private key that pairs with the access key. It is masked.
* **Enter Bucket Prefix:** the folder, or prefix, inside the bucket where Tellius writes temporary files while it moves data out of Redshift.
* **Enter Bucket Prefix Name:** the S3 bucket used as the temporary staging area. Tellius must be able to read, write and delete temporary files in it.
* **Enter Endpoint:** the endpoint of the S3 service, for example `s3.amazonaws.com`.
{% hint style="success" %}
**Keep the staging area separate.** Use a bucket, or at least a prefix, that holds nothing but Tellius staging files, and give the IAM user access to that location only. Tellius deletes its temporary files there, so nothing else should depend on that folder.
{% endhint %}
### Snowflake
**Modern Snowflake:** when it is on, new Snowflake connections can use only **Key Pair** or **OAuth** authentication. **Direct Authentication** isn't offered when someone creates a new connection.
{% hint style="success" %}
**When to turn on Modern Snowflake.** Turn it on when your security team wants Snowflake connections to use key pairs or single sign-on through OAuth instead of a user name and password. See [Connecting to Snowflake](/tellius-6.4/data/create-new-datasource/connecting-to-snowflake.md).
{% endhint %}
### Spark public IP discovery
When this is on, Tellius discovers the public IP addresses of its Spark driver and executors when they start. Administrators can then add those addresses to the allowlist on a data source's firewall, so Tellius can reach the source.
* **Extract Spark public IPs on startup:** when it is on, the Tellius server calls the discovery service below at startup. When it is off, Tellius makes no network call for this.
* **Public IP discovery service URL** (the field under the switch): the HTTP or HTTPS address of a service that returns the public IP of the host that calls it. Each Spark driver and executor calls it when it starts, and the addresses it returns are shown in the connector IP allowlist panel. The field is available only while the switch is on. If the address isn't a valid HTTP or HTTPS URL, Tellius shows an error and doesn't save it.
{% hint style="warning" %}
**Air-gapped or private network?** Turn **Extract Spark public IPs on startup** off when your deployment is air-gapped or runs behind a private network. With it off, Tellius makes no call to the discovery service.
{% endhint %}
### Who can see this page
Only super users see **Connector Settings** in Settings. A custom role reaches it with **Manage system** under **Administration**. See [Custom roles](/tellius-6.4/settings/users-and-access/custom-roles.md).
### Related pages
* [Connectors](/tellius-6.4/settings/connectors.md)
* [Connecting to Snowflake](/tellius-6.4/data/create-new-datasource/connecting-to-snowflake.md)
* [Storage & Cache](/tellius-6.4/settings/storage-and-cache.md)
---
# 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://help.tellius.com/tellius-6.4/settings/connector-settings.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.
