N8N Tools - S3 EnhancedInstall

Overview

This node provides enhanced operations for managing and interacting with S3-compatible storage buckets and objects. It supports a wide range of bucket and object management features such as creating/deleting buckets, uploading/downloading objects, managing access control lists (ACLs), configuring bucket policies, CORS, lifecycle rules, tagging, multipart uploads, versioning, logging, notifications, replication, encryption, website hosting, metrics, analytics, inventory, request payment settings, accelerate configuration, and more.

The "Put Bucket Request Payment" operation specifically allows you to configure who pays for requests and data transfer costs on an S3 bucket — either the bucket owner or the requester.

Common scenarios where this node is beneficial:

• Automating S3 bucket and object management tasks within workflows.
• Configuring advanced bucket settings like lifecycle policies, CORS, and replication.
• Managing access permissions and tags programmatically.
• Handling large file uploads via multipart upload.
• Generating presigned URLs for secure temporary access to objects.
• Setting who bears the cost of requests and data transfer on buckets.

Practical example for "Put Bucket Request Payment":

You want to set your S3 bucket so that the requester (instead of the bucket owner) pays for the data transfer costs when accessing objects. This can be useful in scenarios where you provide public access but want users to bear the cost of their requests.

Properties

Output

The output JSON object for the "Put Bucket Request Payment" operation includes:

• bucket: The name of the bucket configured.
• payer: The payer setting applied ("Requester" or "BucketOwner").
• message: Confirmation message indicating the update was successful.
• operation: The operation performed (e.g., "putBucketRequestPayment").
• timestamp: ISO string timestamp of when the operation was executed.
• success: Boolean indicating if the operation succeeded (true).

If an error occurs, the output will contain:

• error: Error message describing the failure.
• success: false
• operation: The attempted operation.
• timestamp: Timestamp of the failure.

Dependencies

• Requires an S3-compatible API endpoint with valid credentials (access key ID and secret access key).
• The node uses AWS SDK v3 clients internally to communicate with the S3 service.
• Credentials must have permission to perform the PutBucketRequestPayment action on the specified bucket.
• No additional environment variables are required beyond standard credential configuration.

Troubleshooting

• Common issues:

  • Invalid or missing credentials will cause authentication errors.
  • Insufficient permissions on the bucket will result in access denied errors.
  • Incorrect bucket names or non-existent buckets will cause not found errors.
  • Providing invalid values for the payer property will cause validation errors.

• Error messages and resolutions:

  • "Access denied. Check your credentials and permissions."
    Ensure the credentials used have the necessary permissions for modifying bucket request payment settings.
  • "Invalid Access Key ID. Please check your credentials."
    Verify the access key ID is correct and active.
  • "Invalid Secret Access Key. Please check your credentials."
    Verify the secret access key matches the access key ID.
  • "Cannot connect to endpoint. Check your endpoint URL and network connection."
    Confirm the endpoint URL is reachable and correctly configured.
  • "S3 operation failed: <error message>"
    Review the detailed error message for specific issues; ensure all parameters are valid.

Links and References

• AWS S3 PutBucketRequestPayment API Documentation
• AWS S3 Requester Pays Buckets
• AWS SDK for JavaScript v3 - S3 Client