Overview
This node enables interaction with AWS S3-compatible storage services, focusing on file operations such as copying files between buckets or paths. The "File Copy" operation allows users to copy an object from a source location in one bucket to a destination location in another (or the same) bucket. This is useful for data backup, migration, or reorganizing files within cloud storage.
Practical examples:
- Copying images from a staging bucket to a production bucket.
- Duplicating logs or reports to an archive bucket for long-term storage.
- Moving files across different regions or accounts by copying and then deleting originals.
Properties
| Name | Meaning |
|---|---|
| Provider | The cloud storage provider. Default is "aws". |
| Region | The geographical region of the storage service endpoint. Options include various AWS regions like "US East (N. Virginia) - us-east-1", "Europe (Frankfurt) - eu-central-1", etc. |
| Access Key ID | The access key identifier used for authenticating API requests. |
| Secret Access Key | The secret key corresponding to the access key ID, used for authentication. This is a password-type field. |
| Custom Endpoint | Optional custom endpoint URL for connecting to S3-compatible services other than AWS. |
| Source Path | The full path of the source object to copy, starting with a slash, followed by the bucket name and the key (e.g., /bucket-name/path/to/file.jpg). |
| Destination Path | The full path where the copied object will be placed, starting with a slash, followed by the bucket name and the key (e.g., /destination-bucket/path/to/copied-file.jpg). |
| Additional Fields | A collection of optional parameters that can modify the copy behavior, including: - requesterPays (boolean) - storageClass (e.g., STANDARD, REDUCED_REDUNDANCY) - acl (access control list settings) - grantFullControl, grantRead, grantReadAcp, grantWriteAcp (permissions) - lockLegalHold, lockMode, lockRetainUntilDate (object lock settings) - serverSideEncryption and related encryption keys/settings - taggingDirective, metadataDirective (metadata handling directives) |
Output
The output JSON contains information about the result of the copy operation. Typically, it returns an array with objects indicating success status and possibly metadata about the copied file. The exact structure depends on the underlying AWS SDK response but generally confirms whether the copy was successful.
No binary data is outputted by this operation since it deals with copying files within the storage service rather than transferring file content directly.
Dependencies
- Requires valid credentials with appropriate permissions to access and manipulate objects in the specified S3 buckets.
- Needs network access to the AWS S3 endpoints or compatible custom endpoints.
- No internal credential names are exposed; users must provide an API key and secret for authentication.
- The node uses helper functions to interact with AWS S3 APIs, relying on standard AWS SDK conventions.
Troubleshooting
- Invalid Credentials: If the access key or secret is incorrect or lacks permissions, the node will throw authentication errors. Verify credentials and ensure they have rights to read from the source and write to the destination buckets.
- Incorrect Paths: The source and destination paths must start with a slash and include both bucket and key names. Omitting these or formatting incorrectly will cause errors.
- Region Mismatch: Specifying the wrong region may lead to connection failures or permission issues. Ensure the region matches the bucket's actual location.
- Unsupported Features: Some advanced options in additional fields might not be supported by all S3-compatible providers or require specific permissions.
- Network Issues: Connectivity problems to AWS endpoints or custom endpoints will cause timeouts or failures.
- Copying Large Files: Very large files might require multipart copy operations which may not be handled automatically; check logs if copying fails for large objects.