N8N Tools - S3 Enhanced
Actions66
- Generate Presigned URL
- Generate Presigned POST
- Create Bucket
- Delete Bucket
- List Buckets
- Upload Object
- Download Object
- Delete Object
- List Objects
- Copy Object
- Get Object ACL
- Put Object ACL
- Get Bucket ACL
- Put Bucket ACL
- Get Bucket CORS
- Put Bucket CORS
- Delete Bucket CORS
- Get Bucket Lifecycle
- Put Bucket Lifecycle
- Delete Bucket Lifecycle
- Get Bucket Policy
- Put Bucket Policy
- Delete Bucket Policy
- Get Object Tagging
- Put Object Tagging
- Delete Object Tagging
- Get Bucket Tagging
- Put Bucket Tagging
- Delete Bucket Tagging
- Create Multipart Upload
- Upload Part
- Complete Multipart Upload
- Abort Multipart Upload
- List Parts
- List Multipart Uploads
- Get Bucket Versioning
- Put Bucket Versioning
- Get Bucket Logging
- Put Bucket Logging
- Get Bucket Notification
- Put Bucket Notification
- Get Bucket Replication
- Put Bucket Replication
- Delete Bucket Replication
- Get Bucket Encryption
- Put Bucket Encryption
- Delete Bucket Encryption
- Get Bucket Website
- Put Bucket Website
- Delete Bucket Website
- Get Bucket Metrics
- Put Bucket Metrics
- Delete Bucket Metrics
- Get Bucket Analytics
- Put Bucket Analytics
- Delete Bucket Analytics
- Get Bucket Inventory
- Put Bucket Inventory
- Delete Bucket Inventory
- Get Bucket Request Payment
- Put Bucket Request Payment
- Get Bucket Accelerate
- Put Bucket Accelerate
- Head Object
- Restore Object
- Select Object Content
Overview
The node "N8N Tools - S3 Enhanced" provides a comprehensive set of operations to interact with S3-compatible object storage services. It supports advanced features such as generating presigned URLs and POSTs for secure temporary access, multipart uploads for large files, bucket and object management, ACL and tagging configurations, lifecycle policies, replication, encryption, website hosting settings, analytics, inventory, and more.
This node is beneficial in scenarios where you need programmatic control over S3 buckets and objects beyond simple upload/download, including managing bucket policies, configuring notifications, or performing complex queries on object content.
Practical examples:
- Generating a presigned URL to allow temporary download access to a private file without exposing credentials.
- Uploading large files using multipart upload to improve reliability and performance.
- Retrieving the notification configuration of a bucket to monitor events like object creation.
- Managing bucket lifecycle rules to automate data retention policies.
For the provided Resource "Default" and Operation "Get Bucket Notification", this node retrieves the notification configuration of a specified S3 bucket, which includes topic, queue, and event bridge configurations.
Properties
| Name | Meaning |
|---|---|
| Bucket Name | Name of the S3 bucket from which to get the notification configuration |
Output
The output JSON object for the "Get Bucket Notification" operation has the following structure:
bucket: The name of the bucket queried.topicConfigurations: Array of topic-based notification configurations associated with the bucket.queueConfigurations: Array of queue-based notification configurations associated with the bucket.eventBridgeConfiguration: Configuration related to EventBridge notifications for the bucket.
This output provides detailed information about how the bucket is configured to send notifications on various events, useful for monitoring or triggering workflows based on bucket activity.
Dependencies
- Requires an S3-compatible service endpoint accessible via AWS SDK v3 client.
- Requires valid API credentials (access key ID and secret access key) with permissions to read bucket notification configurations.
- The node expects the user to configure these credentials securely within n8n's credential management system.
- No additional environment variables are explicitly required beyond standard AWS/S3 credentials.
Troubleshooting
Common issues:
- Invalid or missing credentials will cause authentication failures.
- Insufficient permissions on the bucket may result in access denied errors.
- Incorrect bucket name or non-existent bucket will cause errors indicating the bucket cannot be found.
- Network connectivity issues to the S3 endpoint can cause connection errors.
Error messages and resolutions:
"Access denied. Check your credentials and permissions."— Ensure the API key has permission to callGetBucketNotificationConfiguration."Cannot connect to endpoint. Check your endpoint URL and network connection."— Verify the endpoint URL and network accessibility."S3 operation failed: <message>"— General catch-all error; check the detailed message for specifics."Invalid notification configuration JSON format"— Not applicable here since this operation only reads configuration, but relevant for setting notifications.