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 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 Put Bucket ACL operation specifically allows setting the Access Control List (ACL) permissions on an S3 bucket, controlling who can access the bucket and what actions they can perform.
Common scenarios:
- Setting bucket permissions to control public or private access.
- Automating bucket permission updates as part of deployment or data lifecycle workflows.
- Managing access rights in multi-user environments or across different teams.
Practical example:
- Automatically set a newly created bucket's ACL to "private" to restrict access.
- Change a bucket's ACL to "public-read" to allow public read access for hosting static website content.
Properties
| Name | Meaning |
|---|---|
| Bucket Name | The name of the S3 bucket on which to set the ACL. |
| ACL | The Access Control List permission to apply to the bucket. Options include: - Private - Public Read - Public Read Write - Authenticated Read - AWS Exec Read - Bucket Owner Read - Bucket Owner Full Control |
Output
The output JSON object for the Put Bucket ACL operation includes:
bucket: The name of the bucket whose ACL was updated.acl: The ACL permission that was applied.message: A confirmation string indicating successful update, e.g.,"Bucket ACL updated successfully".
Example output JSON:
{
"bucket": "my-bucket-name",
"acl": "private",
"message": "Bucket ACL updated successfully",
"operation": "putBucketAcl",
"timestamp": "2024-06-xxTxx:xx:xx.xxxZ",
"success": true
}
Dependencies
- Requires valid credentials with appropriate permissions to manage S3 buckets.
- Needs an API key credential for S3-compatible service authentication.
- Uses AWS SDK for JavaScript v3 under the hood.
- Configuration of region, endpoint, and optional session token may be required depending on the S3-compatible service used.
Troubleshooting
- Access Denied Errors: Ensure the provided credentials have sufficient permissions to modify bucket ACLs.
- Invalid Bucket Name: Verify the bucket name exists and is correctly spelled.
- Network/Endpoint Issues: Check network connectivity and endpoint URL if using a custom S3-compatible service.
- Invalid ACL Value: Use one of the supported ACL options; invalid values will cause errors.
- JSON Parsing Errors: Not applicable for this operation since ACL is selected from predefined options.
If the node throws an error like S3 operation failed: <message>, check the message for clues such as permission issues or invalid parameters.