> For the complete documentation index, see [llms.txt](https://annotationdocs.telusinternational.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://annotationdocs.telusinternational.com/secure-attachment-access/hybrid-cloud.md).
# Hybrid Cloud
If you don't want TELUS International to access your data and only want to restrict access to your own annotators and team members, you can opt for the hybrid cloud approach.
In our usual approach, you host your raw data (images, point-clouds) in an s3 bucket and share it with TELUS International. TELUS International then copies the data over to its own bucket and serves it to annotators via signed URLs.
In the hybrid approach, you host your raw data in your AWS/GCP/Azure file storage or even your local file storage and don't share access with TELUS International. You then share just the URLs while creating jobs in TELUS International. You have to ensure that your annotators have access to objects in your file storage. This can be done by whitelisting the annotators' IP range if using AWS s3, GCS or Azure Blob storage or by adding your annotators in your local network.
You can also create a signed URL with an expiry date and send that signed URL as part of the job creation POST request.
To enable Hybrid cloud, you will have to make sure attachment validation is off in the workflow. You can go to the workflow settings and disable attachment validation.
Apart from raw data, there is another type of data, i.e. labels. These are stored either in database or s3 of TELUS International (eg. pixel-wise segmentation masks). In the hybrid approach, TELUS International will only store the labels, and not the raw data. Once a job is completed, You will be able to GET the labels via API and store it back in your file storage or database.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://annotationdocs.telusinternational.com/secure-attachment-access/hybrid-cloud.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.