> ## Documentation Index
> Fetch the complete documentation index at: https://docs.unstructured.io/llms.txt
> Use this file to discover all available pages before exploring further.
# VAST
> Send processed data from Unstructured to [VAST](https://www.vastdata.com/).
First time creating a connector? [Read this first](/api-reference/workflow/connector-first-time-reqs).
## Requirements
You will need:
* A [VAST](https://www.vastdata.com/) user account with permissions to the bucket to which you want to connect.
* A bucket that contains the objects to which you want to connect. A bucket is a storage resource that uses Amazon's Simple Storage Service (S3) as an access protocol.
To create a bucket, see [Creating S3 Buckets](https://kb.vastdata.com/documentation/docs/creating-s3-buckets-via-vms-1) in the *VAST Cluster Administrator's Guide*.
* The path to the files in the bucket.
If the target files are in the root of the bucket, the path should be formatted as `vast://bucket/` (for example, `vast://my-bucket/`). If the target files are in a folder, format the path to the target folder as `vast://bucket/path/to/folder/` (for example, `vast://my-bucket/my-folder/`).
* The URL for the VAST region in which the bucket is located (for example, `https://vast-cluster.my-company.com`).
* An enabled access and secret key pair that grants the authenticated user permission to the VAST bucket.
To grant a user access to a bucket, and attach identity policies that define their permissions on that bucket, see [Managing S3 User Access from the VAST Web UI](https://kb.vastdata.com/documentation/docs/managing-s3-user-access-from-the-vast-web-ui-1) or [Managing S3 Access from the VAST CLI](https://kb.vastdata.com/documentation/docs/managing-s3-access-from-the-vast-cli) in the *VAST Cluster Administrator's Guide*.
VAST recommends using identity policies and bucket policies to control S3 bucket access.
* *Identity policies* are attached to users and groups, and defines the actions the users or groups can perform against buckets.
* *Bucket policies* are attached to a view, and define actions that particular users or groups can perform against the view and files or directories under the view.
For more information, see [Overview of S3 Access Management](https://kb.vastdata.com/documentation/docs/overview-of-s3-access-management) in the *VAST Cluster Administrator's Guide*.
Identity and bucket policies support a subset of elements listed in [Amazon's IAM JSON Policy Reference](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies.html). For information about the required JSON format, supported elements and identity and bucket policy examples, see [Identity and Bucket Policy Reference](https://kb.vastdata.com/documentation/docs/identity-and-bucket-policy-reference-1) in the *VAST Cluster Administrator's Guide*.
For source connectors, the authenticated user must have bucket permissions for the following S3 actions:
* `s3:ListBucket`
* `s3:GetObject`
For destination connectors, the authenticated user must have bucket permissions for the following S3 actions:
* `s3:PutObject`
VAST buckets are private by default. [Anonymous access](https://kb.vastdata.com/documentation/docs/overview-of-vast-cluster-s3-implementation-1#support-for-authenticated-or-anonymous-requests) can be explicitly enabled using bucket policies, but is not recommended.
## Examples
To create a VAST destination connector, see the following examples.
For more information on working with destination connectors using the Unstructured API, see [Destination endpoints](/api-reference/api/destination/destination-apis).
```python Python SDK theme={null}
import os
from unstructured_client import UnstructuredClient
from unstructured_client.models.operations import CreateDestinationRequest
from unstructured_client.models.shared import CreateDestinationConnector
with UnstructuredClient(api_key_auth=os.getenv("UNSTRUCTURED_API_KEY")) as client:
response = client.destinations.create_destination(
request=CreateDestinationRequest(
create_destination_connector=CreateDestinationConnector(
name="",
type="vast",
config={
"remote_url": "",
"endpoint_url": "",
"recursive": ,
"max-objects": ,
"key": "",
"secret": ""
}
)
)
)
print(response.destination_connector_information)
# ...
```
```bash curl theme={null}
curl --request 'POST' --location \
"$UNSTRUCTURED_API_URL/destinations" \
--header 'accept: application/json' \
--header "unstructured-api-key: $UNSTRUCTURED_API_KEY" \
--header 'content-type: application/json' \
--data \
'{
"name": "",
"type": "vast",
"config": {
"remote_url": "",
"endpoint_url": "",
"recursive": ,
"max-objects": ,
"key": "",
"secret": ""
}
}'
```
## Configuration settings
Replace the preceding placeholders as follows:
A unique name for this connector.
The path to the files in the bucket.
If the target files are in the root of the bucket, the path should be formatted as `vast://bucket/`. For example: `vast://my-bucket/`)
If the target files are in a folder, format the path to the target folder as `vast://bucket/path/to/folder/`. For example: `vast://my-bucket/my-folder/`
For destination connectors, the relative directory structure of files is preserved when files are uploaded. Also, files are overwritten if they already exist at the destination.
Source connectors only. Set to `true` to access sub-folders within the bucket.
Source connectors only. The maximum number of objects to index.
The VAST storage endpoint URL. For example, `https://vast-cluster.my-company.com`.
The access key ID for the authenticated user.
The secret access key corresponding to the preceding access key ID.