N8N Tools - S3 Enhanced icon

N8N Tools - S3 Enhanced

Enhanced S3 operations with presigned URLs, multipart upload, and advanced features

Overview

This node provides enhanced integration with S3-compatible object storage services, enabling a wide range of bucket and object management operations. It supports advanced features such as generating presigned URLs for secure temporary access, multipart uploads for large files, and detailed bucket configurations (e.g., lifecycle, CORS, policies).

The "Delete Object" operation specifically allows users to delete a single object from a specified bucket by providing the bucket name and the object's key (path). This is useful in scenarios where you want to programmatically remove files or data stored in an S3 bucket, such as cleaning up outdated backups, removing user-uploaded files, or managing storage costs.

Practical example:

  • Automatically deleting a file after processing it in a workflow.
  • Removing temporary files uploaded during a session.
  • Cleaning up objects that match certain criteria after a batch job completes.

Properties

Name Meaning
Bucket Name Name of the S3 bucket from which the object will be deleted.
Object Key Complete path/key of the object within the bucket to delete (e.g., folder/file.pdf).

Output

The output JSON contains the following fields:

  • bucket: The name of the bucket where the object was deleted.
  • key: The key (path) of the deleted object.
  • deleted: A boolean value (true) indicating that the deletion was successful.
  • operation: The string "deleteObject" indicating the performed operation.
  • timestamp: ISO 8601 timestamp when the operation was executed.
  • success: Boolean true indicating the operation succeeded.

If the operation fails and "Continue On Fail" is enabled, the output will contain an error message and success: false.

No binary data is output for this operation.

Dependencies

  • Requires valid credentials for an S3-compatible service, including access key ID and secret access key, optionally with region, endpoint, and session token.
  • Uses AWS SDK clients internally to communicate with the S3 API.
  • The node expects proper configuration of these credentials in n8n before use.

Troubleshooting

  • Common issues:

    • Invalid or missing bucket name or object key parameters.
    • Insufficient permissions to delete objects in the specified bucket.
    • Network or endpoint connectivity problems.
    • Incorrect credentials leading to authentication errors.
  • Common error messages and resolutions:

    • "S3 operation failed: Access denied": Check that the API key has permission to delete objects in the bucket.
    • "S3 operation failed: NoSuchBucket": Verify the bucket name exists and is correctly spelled.
    • "S3 operation failed: NoSuchKey": Confirm the object key exists in the bucket.
    • "S3 operation failed: InvalidAccessKeyId" or "Invalid Secret Access Key": Recheck your credentials.
    • Connection errors like "Cannot connect to endpoint": Validate network access and endpoint URL.

Enabling "Continue On Fail" can help workflows proceed even if some deletions fail, allowing error handling downstream.

Links and References

Discussion