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, encryption, lifecycle rules, and more. It is designed to facilitate comprehensive S3 management within n8n workflows.

The Delete Bucket Encryption operation specifically deletes the server-side encryption configuration from a specified S3 bucket. This can be useful when you want to remove encryption settings from a bucket, for example, if you no longer require encrypted storage or need to reset encryption configurations.

Practical examples:

  • Removing encryption from a bucket before migrating data to another system.
  • Resetting bucket encryption settings as part of an automated compliance or audit workflow.
  • Managing bucket configurations dynamically based on environment or policy changes.

Properties

Name Meaning
Bucket Name Name of the S3 bucket from which the encryption configuration will be deleted.

Output

The output JSON object for the Delete Bucket Encryption operation contains:

  • bucket: The name of the bucket where encryption was deleted.
  • message: A confirmation message indicating successful deletion of the bucket encryption configuration.

Example output:

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

No binary data is output by this operation.

Dependencies

  • Requires valid AWS S3-compatible credentials with permissions to delete bucket encryption configurations.
  • Uses AWS SDK for JavaScript v3 (@aws-sdk/client-s3).
  • The node expects proper configuration of credentials in n8n that provide access key ID, secret access key, and optionally session token, region, and endpoint.

Troubleshooting

  • Common issues:

    • Insufficient permissions: The AWS credentials used must have permission to perform DeleteBucketEncryption on the target bucket.
    • Invalid bucket name: Ensure the bucket name is correct and exists.
    • Network or endpoint errors: 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.
    • Credential-related errors such as invalid keys or access denied will be surfaced during credential testing or execution.
  • Resolution tips:

    • Confirm IAM policies attached to the credentials allow deleting bucket encryption.
    • Double-check the bucket name spelling and existence.
    • Test connection using the node's credential test feature.
    • Review network settings if connecting to non-AWS endpoints.

Links and References

Discussion