> For the complete documentation index, see [llms.txt](https://docs.ubiquity.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ubiquity.co.nz/documentation/data-and-integrations/connectors/connection-setup.md).

# Connection Setup

How to configure UbiQuity's connection to your SFTP server, Azure Blob container, or Amazon S3 bucket.

Each Connector requires a secure connection to a storage location that you host and manage within your own environment. The configuration steps vary depending on your storage type.

Select your storage type below to get started.

***

### Amazon S3

Connect UbiQuity to an Amazon S3 bucket using IAM role assumption. No permanent access keys are stored in UbiQuity.

Setting Up Your [Amazon S3 Connection →](/documentation/data-and-integrations/connectors/connection-setup/s3-connection.md)

***

#### Microsoft Azure Blob Storage

Connect UbiQuity to an Azure Blob container using a service principal or SAS token.

Setting Up Your [Azure Blob Storage Connection →](/documentation/data-and-integrations/connectors/connection-setup/azure-blob-storage-connection.md)

***

#### SFTP

Connect UbiQuity to an SFTP server using SSH key authentication.

Setting Up Your [SFTP Connection →](/documentation/data-and-integrations/connectors/connection-setup/sftp-connection.md)

***

> **Not sure which storage type to use?** This decision is usually made by your IT or cloud platform team. See [Before You Begin](/documentation/data-and-integrations/connectors/before-you-begin.md) for guidance on involving the right people.


---

# 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.ubiquity.co.nz/documentation/data-and-integrations/connectors/connection-setup.md?ask=<question>&goal=<user_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.