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 features such as generating presigned URLs and POSTs for secure temporary access, multipart uploads for large files, bucket and object management, access control, tagging, lifecycle policies, analytics, metrics, and more.

This node is beneficial in scenarios where you need to automate or integrate complex S3 workflows within n8n, such as:

  • Generating temporary URLs for clients to upload or download files without exposing credentials.
  • Managing buckets and objects programmatically (create, delete, copy, list).
  • Configuring bucket policies, CORS, lifecycle rules, and encryption.
  • Handling multipart uploads for large files efficiently.
  • Retrieving and setting metadata, tags, ACLs, and notifications.
  • Accessing advanced configurations like metrics, analytics, inventory, replication, and website hosting.

Example use cases:

  • Automate backup processes by uploading files to S3 with multipart upload.
  • Generate presigned URLs for users to securely download reports.
  • Manage bucket lifecycle policies to archive or delete old data automatically.
  • Configure bucket analytics and metrics for monitoring usage patterns.

Properties

Name Meaning
Bucket Name Name of the S3 bucket to operate on.
Configuration ID Identifier for specific configurations like metrics, analytics, or inventory settings.

For the Get Bucket Metrics operation specifically, these properties are relevant:

Name Meaning
Bucket Name The name of the S3 bucket whose metrics configuration you want to retrieve.
Configuration ID The unique ID of the metrics configuration to get from the specified bucket.

Output

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

  • bucket: The bucket name provided in the input.
  • configurationId: The configuration ID used to fetch the metrics.
  • metricsConfiguration: An object containing the detailed metrics configuration retrieved from the bucket.

Additionally, every output includes metadata fields:

  • operation: The operation name executed (getBucketMetrics).
  • timestamp: ISO string timestamp when the operation was performed.
  • success: Boolean indicating if the operation succeeded.

If an error occurs, the output contains:

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

No binary data is output by this operation.


Dependencies

  • Requires valid credentials for an S3-compatible service, including access key ID and secret access key.
  • Uses AWS SDK v3 for JavaScript internally to communicate with the S3 API.
  • The node expects proper network connectivity to the configured S3 endpoint.
  • No additional environment variables are required beyond credential setup in n8n.

Troubleshooting

Common Issues

  • Invalid Credentials: If the access key or secret key is incorrect, the node will fail to connect or perform operations.
  • Incorrect Bucket Name or Configuration ID: Providing a non-existent bucket or configuration ID will result in errors.
  • Network Connectivity: Endpoint URL misconfiguration or network issues can cause connection failures.
  • Malformed JSON Inputs: For operations requiring JSON inputs (not applicable here but common in other operations), invalid JSON will throw errors.

Common Error Messages

  • "S3 operation failed: <message>" — General failure during the S3 API call; check the detailed message.
  • "InvalidAccessKeyId" — The access key ID is not recognized; verify credentials.
  • "SignatureDoesNotMatch" — Secret access key mismatch; verify credentials.
  • "AccessDenied" — Insufficient permissions; ensure the credentials have required S3 permissions.
  • "Cannot connect to endpoint" — Network or endpoint URL issue; verify endpoint and network access.
  • "Invalid metrics configuration JSON format" — (For put operations) JSON input is malformed; validate JSON syntax.

To resolve errors, verify credentials, bucket names, configuration IDs, and network connectivity. Use the node's credential test feature to confirm connection success before running operations.


Links and References


If you need details about other operations or resources, feel free to ask!

Discussion