Actions66
- Generate Presigned URL
- Generate Presigned POST
- Create Bucket
- Delete Bucket
- List Buckets
- Upload Object
- Download Object
- Delete Object
- List Objects
- Copy Object
- Get Object ACL
- Put Object ACL
- Get Bucket ACL
- Put Bucket ACL
- Get Bucket CORS
- Put Bucket CORS
- Delete Bucket CORS
- Get Bucket Lifecycle
- Put Bucket Lifecycle
- Delete Bucket Lifecycle
- Get Bucket Policy
- Put Bucket Policy
- Delete Bucket Policy
- Get Object Tagging
- Put Object Tagging
- Delete Object Tagging
- Get Bucket Tagging
- Put Bucket Tagging
- Delete Bucket Tagging
- Create Multipart Upload
- Upload Part
- Complete Multipart Upload
- Abort Multipart Upload
- List Parts
- List Multipart Uploads
- Get Bucket Versioning
- Put Bucket Versioning
- Get Bucket Logging
- Put Bucket Logging
- Get Bucket Notification
- Put Bucket Notification
- Get Bucket Replication
- Put Bucket Replication
- Delete Bucket Replication
- Get Bucket Encryption
- Put Bucket Encryption
- Delete Bucket Encryption
- Get Bucket Website
- Put Bucket Website
- Delete Bucket Website
- Get Bucket Metrics
- Put Bucket Metrics
- Delete Bucket Metrics
- Get Bucket Analytics
- Put Bucket Analytics
- Delete Bucket Analytics
- Get Bucket Inventory
- Put Bucket Inventory
- Delete Bucket Inventory
- Get Bucket Request Payment
- Put Bucket Request Payment
- Get Bucket Accelerate
- Put Bucket Accelerate
- Head Object
- Restore Object
- Select Object Content
Abort Multipart Upload
AI-generatedOverview
The node provides enhanced operations for interacting with S3-compatible object storage services. It supports a wide range of bucket and object management features, including multipart uploads, presigned URLs, bucket policies, tagging, lifecycle rules, and more.
Specifically, the Abort Multipart Upload operation allows users to cancel an ongoing multipart upload process by specifying the bucket name, object key, and the multipart upload ID. This is useful when a multipart upload is no longer needed or was started in error, helping to free up resources and avoid incomplete uploads lingering in the storage.
Common scenarios:
- Cancelling a large file upload that was interrupted or no longer required.
- Cleaning up abandoned multipart uploads to reduce storage costs.
- Managing multipart uploads programmatically as part of automated workflows.
Practical example:
You have initiated a multipart upload for a large video file but realize the file is incorrect. Using this node's Abort Multipart Upload operation, you can abort the upload by providing the bucket name, the object key, and the upload ID, effectively cancelling the upload and removing any uploaded parts.
Properties
| Name | Meaning |
|---|---|
| Bucket Name | The name of the S3 bucket where the multipart upload is taking place. |
| Upload ID | The unique identifier of the multipart upload to be aborted. |
Output
The output JSON contains the following fields:
bucket: The name of the bucket where the multipart upload was aborted.key: The object key associated with the multipart upload.uploadId: The ID of the aborted multipart upload.message: A confirmation message indicating successful abortion of the multipart upload.
Example output JSON:
{
"bucket": "my-bucket-name",
"key": "path/to/object.ext",
"uploadId": "example-upload-id",
"message": "Multipart upload aborted successfully"
}
This node does not output binary data for this operation.
Dependencies
- Requires an S3-compatible service endpoint.
- Requires credentials with sufficient permissions to abort multipart uploads on the specified bucket.
- Uses AWS SDK v3 for JavaScript under the hood.
- The node expects proper configuration of credentials (access key, secret key, optional session token) and optionally region and endpoint URL.
Troubleshooting
- Invalid or missing Upload ID: Ensure the correct multipart upload ID is provided; otherwise, the abort operation will fail.
- Access Denied errors: Verify that the credentials used have permission to abort multipart uploads on the target bucket.
- Bucket or Key not found: Confirm that the bucket and object key exist and are correctly specified.
- Network or Endpoint issues: Check network connectivity and endpoint URL correctness if connection errors occur.
- Error messages from the node: The node throws errors with descriptive messages such as "S3 operation failed: [error details]". Review these messages to identify issues.