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
This node provides enhanced operations for managing and interacting with S3-compatible object storage services. It supports a wide range of bucket and object management features, including creating and deleting buckets, uploading and downloading objects, managing access control lists (ACLs), configuring bucket policies, lifecycle rules, CORS, versioning, logging, notifications, replication, encryption, website hosting, metrics, analytics, inventory, request payment, acceleration, multipart uploads, and more.
The "Put Bucket Versioning" operation specifically allows users to enable or suspend versioning on an S3 bucket and configure MFA delete settings. This is useful for scenarios where you want to maintain multiple versions of objects in a bucket for data protection, auditing, or recovery purposes.
Practical example:
- Enable versioning on a bucket to keep track of all changes to objects, allowing rollback to previous versions if needed.
- Suspend versioning temporarily without deleting existing versions.
- Configure MFA delete to add an extra layer of security by requiring multi-factor authentication for version deletion.
Properties
| Name | Meaning |
|---|---|
| Bucket Name | The name of the S3 bucket on which to set the versioning configuration. |
| Versioning Status | The desired versioning state for the bucket. Options: Enabled, Suspended. |
| MFA Delete | The MFA delete status for the bucket. Options: Enabled, Disabled. |
Output
The output JSON object for the "Put Bucket Versioning" operation includes:
bucket: The name of the bucket whose versioning was updated.versioningStatus: The versioning status that was set (EnabledorSuspended).mfaDelete: The MFA delete status that was set (EnabledorDisabled).message: A confirmation message indicating the bucket versioning was updated successfully.operation: The operation performed (putBucketVersioning).timestamp: The ISO timestamp when the operation was executed.success: Boolean indicating whether the operation succeeded (true).
No binary data output is produced by this operation.
Dependencies
- Requires an S3-compatible service endpoint accessible via AWS SDK v3 client.
- Requires credentials with sufficient permissions to modify bucket versioning settings.
- The node expects an API key credential (access key ID and secret access key) configured in n8n for authentication.
- Optional session token and custom endpoint can be provided.
- No additional environment variables are required beyond standard credential setup.
Troubleshooting
Common issues:
- Invalid or insufficient permissions on the provided credentials may cause access denied errors.
- Incorrect bucket name or non-existent bucket will result in errors.
- Network connectivity issues or incorrect endpoint URL can cause connection failures.
- Providing invalid values for versioning status or MFA delete options will cause validation errors.
Error messages and resolutions:
"Access denied. Check your credentials and permissions."
Ensure the API key has permission to performPutBucketVersioningon the target bucket."Cannot connect to endpoint. Check your endpoint URL and network connection."
Verify the endpoint URL and network accessibility."S3 operation failed: <error message>"
Review the detailed error message for specifics; check bucket existence and parameter correctness."Invalid versioning status"or similar validation errors
Confirm that the versioning status is eitherEnabledorSuspended."Invalid MFA delete status"
Confirm that MFA delete is set toEnabledorDisabled.