S3¶
Creates a Carbon data connector configured for Amazon S3. This node acts as a thin integration selector that tells the Carbon pipeline to use the S3 connector; all common behavior (auth, configuration, syncing, and data retrieval) is handled by the shared Carbon data connector base logic.
Usage¶
Use this node when you need to connect and sync documents from an Amazon S3 bucket into Salt for downstream search, RAG, or analytics. Place it where your workflow collects or updates external data; pair it with nodes that trigger connection/auth flows and nodes that consume the resulting dataset or files.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| Not specified | False | Not specified | Inputs for this node are defined by the shared Carbon data connector base. This node only specifies the S3 integration type; the base layer manages actual parameters (e.g., auth, scopes, sync controls). | Not specified |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| Not specified | Not specified | Outputs are provided by the shared Carbon data connector base and typically represent a configured connector/dataset reference for downstream nodes. | Not specified |
Important Notes¶
- Integration selector: This node only selects the S3 integration; the shared Carbon data connector base handles inputs, authentication, syncing, and actual data retrieval.
- Authentication required: You must complete authentication/authorization for S3 in the Carbon connection flow before data can be accessed.
- Permissions: Ensure the S3 credentials used have at least list and read permissions on the bucket/prefix you intend to index.
- Large datasets: Initial syncs on large buckets or wide prefixes can take time; schedule accordingly.
Troubleshooting¶
- Authentication fails: Re-run the Carbon connection flow and confirm credentials are valid and not expired.
- No files returned: Verify the S3 bucket/prefix is correct and that the configured IAM user/role has list and read permissions.
- Slow or incomplete sync: Narrow the S3 prefix, reduce filters, or allow more time for the initial indexing to complete before downstream steps depend on the data.
- Access denied errors: Confirm bucket policies, ACLs, and IAM policies allow the Carbon connector to read the specified resources.