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, allowing users to perform 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 configuration management.

The "Delete Bucket" operation specifically allows users to delete an existing S3 bucket by specifying its name. This is useful in scenarios where you want to programmatically clean up unused or temporary buckets as part of automation workflows.

Practical example:

  • Automatically delete a bucket after all objects have been processed and archived elsewhere.
  • Clean up test buckets created during development or CI/CD pipelines.

Properties

Name Meaning
Bucket Name Name of the S3 bucket to delete

Output

The output JSON object for the "Delete Bucket" operation includes:

  • bucket: The name of the deleted bucket (string).
  • deleted: A boolean flag indicating successful deletion (true).
  • operation: The operation performed, here "deleteBucket".
  • timestamp: ISO string timestamp when the operation was executed.
  • success: Boolean indicating if the operation succeeded (true).

Example output JSON:

{
  "bucket": "my-bucket-name",
  "deleted": true,
  "operation": "deleteBucket",
  "timestamp": "2024-06-01T12:00:00.000Z",
  "success": true
}

No binary data is produced by this operation.

Dependencies

  • Requires valid credentials for an S3-compatible service, including access key ID and secret access key, optionally session token, region, endpoint URL, and path style setting.
  • Uses AWS SDK v3 for JavaScript under the hood.
  • The node expects proper network connectivity to the configured S3 endpoint.
  • No additional environment variables are required beyond credential configuration in n8n.

Troubleshooting

  • Common issues:

    • Attempting to delete a non-empty bucket will fail because S3 requires buckets to be empty before deletion.
    • Incorrect bucket name or permissions can cause access denied errors.
    • Network or endpoint misconfiguration may prevent connection to the S3 service.
  • Error messages and resolutions:

    • "Access denied. Check your credentials and permissions."
      Ensure the API key has permission to delete buckets.
    • "Cannot connect to endpoint. Check your endpoint URL and network connection."
      Verify the endpoint URL and network accessibility.
    • "S3 operation failed: <error message>"
      Review the error message for details; common causes include bucket not empty or invalid bucket name.
    • If the node throws "Unknown operation: deleteBucket" it indicates a misconfiguration; ensure the operation parameter is set correctly.

Links and References

Discussion