N8N Tools - S3 EnhancedInstall

Overview

This node provides enhanced operations for managing Amazon S3 buckets and objects, including advanced features like presigned URLs, multipart uploads, bucket policies, tagging, lifecycle rules, and more. It is designed to interact with S3-compatible storage services, allowing users to perform a wide range of bucket and object management tasks programmatically within n8n workflows.

The Delete Bucket Tagging operation specifically deletes all tags associated with a given S3 bucket. This can be useful when you want to clear metadata tags from a bucket, for example, to reset environment labels or remove obsolete classification tags.

Common scenarios:

• Cleaning up bucket tags before re-tagging or repurposing a bucket.
• Automating bucket maintenance by removing tags as part of a workflow.
• Managing compliance by ensuring no tags remain on buckets that should not have metadata.

Practical example:
You have an S3 bucket used for temporary data storage during a project. After the project ends, you want to remove all tags from the bucket to avoid confusion in future projects. Using this node's Delete Bucket Tagging operation, you can automate this cleanup step in your workflow.

Properties

Output

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

• bucket: The name of the bucket from which tags were deleted.
• message: A confirmation string indicating successful deletion of bucket tags.

Example output JSON:

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

No binary data is output by this operation.

Dependencies

• Requires valid credentials for an S3-compatible service (access key ID, secret access key, optional session token).
• The node uses AWS SDK v3 clients internally to communicate with the S3 API.
• Proper permissions are required to delete bucket tagging (e.g., s3:DeleteBucketTagging permission).
• No additional environment variables are needed beyond credential configuration in n8n.

Troubleshooting

• Common issues:

  • Invalid or missing credentials will cause authentication failures.
  • Insufficient permissions may result in Access Denied errors.
  • Specifying a non-existent bucket will cause errors indicating the bucket was not found.
  • Network or endpoint misconfiguration can lead to connection errors.

• Error messages and resolutions:

  • "S3 operation failed: Access denied": Check that the API key has permission to delete bucket tagging.
  • "S3 operation failed: NoSuchBucket": Verify the bucket name is correct and exists.
  • "S3 operation failed: InvalidAccessKeyId" or "SignatureDoesNotMatch": Confirm credentials are correct.
  • "Cannot connect to endpoint": Validate the endpoint URL and network connectivity.

• If the node is set to continue on fail, errors will be returned in the output JSON with success: false and an error message.

Links and References

• AWS S3 DeleteBucketTagging API
• AWS SDK for JavaScript v3 - S3Client
• Amazon S3 Bucket Tagging