N8N Tools - S3 Enhanced icon

N8N Tools - S3 Enhanced

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

Overview

The node "N8N Tools - S3 Enhanced" provides a comprehensive set of operations to interact with S3-compatible object storage services. It supports advanced bucket and object management features such as generating presigned URLs for secure temporary access, multipart uploads for large files, bucket configuration management (CORS, lifecycle, replication, encryption, website, logging, notifications, tagging, versioning, metrics, analytics, inventory), and object-level operations including ACLs, tagging, copying, restoring archived objects, and querying object content using SQL expressions.

This node is beneficial in scenarios where users need fine-grained control over their S3 buckets and objects beyond simple upload/download. For example:

  • Generating presigned URLs to allow temporary access to private objects without exposing credentials.
  • Managing bucket replication or encryption settings programmatically.
  • Performing multipart uploads to efficiently upload large files in parts.
  • Querying object contents directly using SQL expressions without downloading entire files.
  • Automating bucket lifecycle policies or CORS configurations.

Practical example: A user can automate the process of enabling replication on a bucket by providing the replication configuration JSON, or generate a presigned URL that allows a client to upload a file securely within a limited time window.


Properties

Name Meaning
Bucket Name Name of the S3 bucket to operate on.

For the Get Bucket Replication operation specifically, only the "Bucket Name" property is required.


Output

The output JSON structure for the Get Bucket Replication operation includes:

  • bucket: The name of the bucket queried.
  • replicationConfiguration: The replication configuration object retrieved from the bucket, containing details about replication rules and roles.

Additionally, every output includes metadata fields added by the node:

  • operation: The operation performed (e.g., "getBucketReplication").
  • timestamp: ISO string timestamp when the operation was executed.
  • success: Boolean indicating if the operation succeeded (true).

If an error occurs, the output JSON will contain:

  • error: Error message describing the failure.
  • success: false
  • operation: The attempted operation.
  • timestamp: Timestamp of the failure.

No binary data is output for this operation.


Dependencies

  • Requires an S3-compatible service endpoint accessible via AWS SDK v3 clients.
  • Requires credentials with sufficient permissions to call GetBucketReplication API on the specified bucket.
  • The node expects an API key credential (access key ID and secret access key) configured in n8n for authentication.
  • Optional parameters like region, endpoint URL, session token, and force path style can be configured in the credentials.

Troubleshooting

Common Issues

  • Invalid Credentials: If the access key or secret key is incorrect, connection tests or operations will fail.
  • Access Denied: Insufficient permissions on the bucket to retrieve replication configuration.
  • Invalid Bucket Name: Specifying a non-existent or incorrectly named bucket will cause errors.
  • Network/Endpoint Issues: Incorrect endpoint URL or network connectivity problems can prevent communication with the S3 service.

Common Error Messages and Resolutions

  • "S3 connection failed: Invalid Access Key ID. Please check your credentials."
    Check that the access key ID is correct and properly configured.

  • "S3 connection failed: Invalid Secret Access Key. Please check your credentials."
    Verify the secret access key matches the access key ID.

  • "S3 connection failed: Access denied. Check your credentials and permissions."
    Ensure the credentials have permission to perform the requested operation on the bucket.

  • "S3 operation failed: <message>"
    Review the specific error message for details; it may indicate invalid input, missing bucket, or other issues.

  • "Invalid replication configuration JSON format" (for put operations)
    Make sure the replication configuration JSON is valid and correctly structured.


Links and References


If you need summaries for other operations or resources, please provide their names.

Discussion