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 bucket management, object manipulation, access control, lifecycle policies, multipart uploads, presigned URLs, and advanced features like inventory, analytics, and replication configurations.
This node is beneficial in scenarios where you need to automate or integrate complex S3 workflows within n8n, such as:
- Creating and deleting buckets programmatically.
- Uploading, downloading, copying, and deleting objects.
- Managing bucket and object permissions (ACLs).
- Configuring bucket policies, CORS, lifecycle rules, and encryption.
- Handling large files via multipart upload.
- Generating presigned URLs for secure temporary access without exposing credentials.
- Managing advanced bucket configurations like metrics, analytics, inventory, replication, and notifications.
Practical example:
You can use this node to automatically upload processed files to an S3 bucket, generate a presigned URL for sharing the file securely with external users, and then clean up old files using lifecycle rules — all within an automated workflow.
Properties
| Name | Meaning |
|---|---|
| Bucket Name | Name of the S3 bucket to operate on. |
| Configuration ID | Identifier for specific configurations like metrics, analytics, or inventory settings. |
For the Delete Bucket Inventory operation specifically, the relevant properties are:
| Name | Meaning |
|---|---|
| Bucket Name | The name of the S3 bucket from which the inventory configuration will be deleted. |
| Configuration ID | The ID of the inventory configuration to delete from the specified bucket. |
Output
The output JSON structure varies depending on the operation performed. For the Delete Bucket Inventory operation, the output includes:
bucket: The name of the bucket where the inventory configuration was deleted.configurationId: The ID of the deleted inventory configuration.message: A confirmation string indicating successful deletion.
Additionally, every output includes metadata fields:
operation: The name of the operation executed (deleteBucketInventory).timestamp: ISO timestamp when the operation was performed.success: Boolean indicating if the operation succeeded (true).
If an error occurs and the node is configured to continue on failure, the output will contain:
error: Error message describing what went wrong.success:falseoperation: The attempted operation name.timestamp: When the error occurred.
No binary data is output 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, and path style configuration.
- Uses AWS SDK v3 clients internally to communicate with the S3 API.
- The node expects proper network connectivity to the S3 endpoint.
- No additional environment variables are required beyond credential setup in n8n.
Troubleshooting
Common Issues
- Invalid Credentials: If the access key or secret key is incorrect, the node will fail to authenticate.
- Access Denied: Insufficient permissions on the S3 bucket or inventory configuration may cause errors.
- Configuration ID Missing or Incorrect: Deleting an inventory configuration requires a valid configuration ID; omitting or providing an invalid ID will cause failure.
- Network Connectivity: Endpoint misconfiguration or network issues can prevent connection to the S3 service.
Common Error Messages and Resolutions
"S3 operation failed: Invalid Access Key ID"
Check that the access key ID provided in credentials is correct."S3 operation failed: SignatureDoesNotMatch"
Verify the secret access key matches the access key ID."S3 operation failed: AccessDenied"
Ensure the credentials have permission to delete inventory configurations on the target bucket."S3 operation failed: Cannot connect to endpoint"
Confirm the endpoint URL is correct and reachable from your network."Invalid inventory configuration JSON format"(for other related operations)
Make sure any JSON input for inventory configuration is well-formed.