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 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 including website hosting.

The "Put Bucket Website" operation specifically allows you to configure an S3 bucket to serve static website content by setting the website configuration JSON. This is useful when you want to host a static website directly from your S3 bucket, specifying index and error documents or routing rules.

Practical examples:

  • Hosting a static website on an S3 bucket by setting the index document (e.g., index.html) and error document (e.g., error.html).
  • Updating the website configuration dynamically via workflows to change site behavior or error handling.
  • Automating bucket website setup as part of deployment pipelines.

Properties

Name Meaning
Bucket Name The name of the S3 bucket to configure.
Website Configuration JSON object defining the website settings for the bucket. Typical keys include IndexDocument, ErrorDocument, and optionally RedirectAllRequestsTo and RoutingRules. Example: {"IndexDocument":{"Suffix":"index.html"},"ErrorDocument":{"Key":"error.html"}}

Output

The output JSON contains the following fields:

  • bucket: The name of the bucket configured.
  • websiteConfiguration: The parsed JSON object representing the website configuration that was applied.
  • message: Confirmation string indicating successful update, e.g., "Bucket website updated successfully".

No binary data is output by this operation.

Dependencies

  • Requires valid credentials for an S3-compatible service with permissions to modify bucket website configuration.
  • Uses AWS SDK for JavaScript v3 under the hood.
  • Requires n8n credentials configured with appropriate access keys and optional endpoint for S3-compatible services.

Troubleshooting

  • Invalid website configuration JSON format: If the provided JSON for website configuration is malformed, the node throws an error indicating invalid JSON format. Ensure the JSON is correctly structured.
  • Access denied errors: Occur if the credentials lack permission to modify bucket website settings. Verify IAM policies or equivalent permissions.
  • Bucket not found or incorrect bucket name: Confirm the bucket exists and the name is correct.
  • Network or endpoint issues: Check connectivity to the S3 endpoint and ensure the endpoint URL is correct if using a custom S3-compatible service.

Links and References

Discussion