Overview
This node provides custom integration with AWS S3-compatible storage services, allowing users to perform various file operations such as moving files between buckets or paths. The Move File operation specifically enables relocating a file from one bucket/path to another within the same or different buckets.
Typical use cases include:
- Organizing files by moving them into different folders or buckets based on workflow logic.
- Archiving or backing up files by moving them to designated storage locations.
- Automating file management tasks in cloud storage environments.
For example, you might move an image from a temporary upload bucket to a permanent archive bucket after processing it.
Properties
| Name | Meaning |
|---|---|
| Provider | The cloud storage provider. Default is "aws" for Amazon Web Services. |
| Region | The geographical region of the storage service endpoint. Choose from multiple AWS regions like "US East (N. Virginia) - us-east-1", "Europe (Frankfurt) - eu-central-1", etc. |
| Access Key ID | Your access key identifier for authenticating with the cloud storage service. |
| Secret Access Key | The secret key corresponding to the access key, used for authentication. This is a password-type field and kept confidential. |
| Custom Endpoint | Optional custom endpoint URL if using an S3-compatible service other than AWS or a specific endpoint override. |
| Source Path | The full source path of the file to move, including bucket and key, formatted as /bucket/key. For example: /my-source-bucket/images/photo.jpg. |
| Destination Path | The full destination path where the file should be moved, including bucket and key, formatted as /bucket/key. For example: /my-destination-bucket/archives/photo.jpg. |
| Additional Fields | A collection of optional additional parameters that can modify the move operation, such as access control lists (ACLs), storage class, encryption settings, tagging directives, legal hold options, and requester pays flag. |
Output
The node outputs JSON data indicating the result of the move operation. The output structure typically includes success status and metadata about the moved file. Each item corresponds to an input item processed.
If the operation is successful, the output JSON will confirm success; otherwise, errors are thrown.
No binary data is output by this operation.
Dependencies
- Requires valid credentials with access key ID and secret access key for the target AWS S3 or compatible service.
- Must specify the correct region matching the bucket location.
- Optionally supports custom endpoints for non-AWS S3-compatible services.
- No additional external dependencies beyond standard AWS S3 API access.
Troubleshooting
- Invalid Credentials: If authentication fails, verify that the access key ID and secret access key are correct and have sufficient permissions.
- Incorrect Paths: Ensure that both
sourcePathanddestinationPathstart with a slash (/) and follow the format/bucket/key. Missing or malformed paths will cause errors. - Region Mismatch: Using a region that does not match the bucket's actual region may lead to failures. Confirm the bucket's region and select accordingly.
- Permission Denied: Moving files requires appropriate permissions on both source and destination buckets. Check IAM policies or equivalent access controls.
- Unsupported Features: Some advanced additional fields (like object lock modes or server-side encryption options) require the bucket to support those features; otherwise, the operation may fail.
- Requester Pays Buckets: If the source bucket has requester pays enabled, set the corresponding flag in additional fields to avoid access errors.
Common error messages will relate to authorization failures, missing buckets or keys, or invalid parameter formats. Reviewing these details usually resolves issues.