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 operations for managing Amazon S3 buckets and objects, including advanced features like presigned URLs, multipart uploads, bucket policies, CORS, lifecycle rules, tagging, versioning, website configuration, and more. It is designed to facilitate comprehensive S3 management within n8n workflows.

The Delete Bucket Website operation specifically deletes the website configuration from a specified S3 bucket. This is useful when you want to disable static website hosting on an S3 bucket or remove any existing website settings.

Common scenarios:

  • Disabling static website hosting on an S3 bucket.
  • Cleaning up website configurations before deleting or repurposing a bucket.
  • Automating bucket configuration management in deployment pipelines.

Practical example:
You have an S3 bucket configured to serve a static website, but you want to stop hosting it as a website. Using this node's Delete Bucket Website operation, you can programmatically remove the website configuration without manually accessing the AWS console.


Properties

Name Meaning
Bucket Name Name of the S3 bucket where the website configuration will be deleted.

Output

The output JSON object contains:

  • bucket: The name of the bucket from which the website configuration was deleted.
  • message: A confirmation string indicating successful deletion of the website configuration.

Example output JSON:

{
  "bucket": "my-bucket-name",
  "message": "Bucket website deleted successfully"
}

Dependencies

  • Requires valid credentials with permissions to manage S3 buckets (including deleting website configurations).
  • Uses AWS SDK for JavaScript v3 (@aws-sdk/client-s3).
  • Requires an API key credential for S3-compatible service access.
  • The node expects proper configuration of region, endpoint (optional), and authentication tokens if applicable.

Troubleshooting

  • Common issues:

    • Insufficient permissions: The user or role must have permission to delete the bucket website configuration.
    • Incorrect bucket name: Ensure the bucket name is correct and exists.
    • Network or endpoint misconfiguration: Verify network connectivity and endpoint URL if using custom S3-compatible services.
  • Error messages:

    • "S3 operation failed: <error message>": General failure during the operation; check the detailed error message for specifics.
    • "Invalid bucket name" or "NoSuchBucket": The specified bucket does not exist or is misspelled.
    • "Access denied": Credentials lack required permissions; update IAM policies accordingly.

To resolve errors, verify credentials, bucket existence, and permissions. Also, ensure the node's input parameters are correctly set.


Links and References

Discussion