VolcEngineTos Node icon

VolcEngineTos Node

Interact with VolcEngine Cloud Object Storage (TOS/TOD)

Overview

This node interacts with VolcEngine Cloud Object Storage (TOS) to generate pre-signed URLs for files stored in the cloud. A pre-signed URL allows temporary, secure access to a file without requiring direct authentication. This is useful for scenarios such as:

  • Providing users with time-limited download links.
  • Allowing clients to upload files directly to storage without exposing credentials.
  • Sharing files securely with external parties.

For example, you can generate a GET pre-signed URL to let a user download a file within 30 minutes or create a PUT pre-signed URL so an application can upload a file directly to TOS.

Properties

Name Meaning
File Path The path and name of the file in TOS for which the pre-signed URL will be generated.
HTTP Method The HTTP method for the pre-signed URL: GET to download/view the file, or PUT to upload.
Expires (Seconds) Duration in seconds before the pre-signed URL expires. Default is 1800 seconds (30 minutes).
Version ID Optional specific version ID of the object to target a particular file version.
Content Type Optional override for the Content-Type header in the response when accessing the file.
Content Disposition Optional override for the Content-Disposition header in the response (e.g., attachment filename).

Output

The node outputs JSON data containing the generated pre-signed URL and related metadata. The exact structure typically includes at least a field with the URL string that can be used to access or upload the file depending on the HTTP method chosen.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for VolcEngine Cloud Object Storage with appropriate permissions.
  • Uses the official VolcEngine TOS SDK (@volcengine/tos-sdk) to interact with the storage service.
  • Node configuration must include valid credentials with access key, secret key, region, endpoint, and bucket information.

Troubleshooting

  • Missing Credentials: If no credentials are provided or invalid, the node throws an error "No credentials returned!" Ensure the API key credential is configured correctly.
  • Invalid File Path: Providing an incorrect or non-existent file path may cause errors or invalid URLs.
  • Expired URLs: Using a very short expiration time might cause URLs to expire before use; adjust the "Expires (Seconds)" property accordingly.
  • Permission Issues: Insufficient permissions on the API key may result in authorization errors when generating URLs.
  • Unsupported HTTP Method: Only GET and PUT methods are supported for pre-signed URLs; using others will not work.

Links and References

Discussion