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, tagging, bucket policies, lifecycle rules, and more. It is designed to facilitate comprehensive interaction with S3-compatible storage services within n8n workflows.
The "Put Bucket Tagging" operation specifically allows users to set or update tags on an existing S3 bucket. Tags are key-value pairs that help organize and manage buckets by categorizing them according to environment, project, cost center, or other criteria.
Common scenarios where this node is beneficial:
- Automating the organization of S3 buckets by applying consistent tagging schemes.
- Managing metadata for billing or access control purposes.
- Integrating bucket tagging into deployment or infrastructure automation pipelines.
Practical example:
You have multiple buckets for different projects and environments. Using this node's "Put Bucket Tagging" operation, you can automatically tag a bucket named "my-bucket-name" with {"Environment":"Production","Project":"MyApp"} to easily identify and filter buckets in your AWS console or billing reports.
Properties
| Name | Meaning |
|---|---|
| Bucket Name | The name of the S3 bucket to which the tags will be applied. |
| Tags | JSON object representing tags as key-value pairs to assign to the bucket. Example: {"Environment":"Production","Project":"MyApp"} |
Output
The output JSON object for the "Put Bucket Tagging" operation includes:
bucket: The name of the bucket that was tagged.tags: The JSON object of tags that were applied.message: A confirmation string indicating successful update, e.g.,"Bucket tags updated successfully".
Example output JSON:
{
"bucket": "my-bucket-name",
"tags": {
"Environment": "Production",
"Project": "MyApp"
},
"message": "Bucket tags updated successfully",
"operation": "putBucketTagging",
"timestamp": "2024-06-01T12:00:00.000Z",
"success": true
}
Dependencies
- Requires valid credentials for an S3-compatible service (access key ID, secret access key, optional session token).
- Uses AWS SDK for JavaScript v3 under the hood.
- The node expects proper configuration of credentials in n8n to authenticate requests.
- Network connectivity to the S3 endpoint is required.
Troubleshooting
- Invalid tags JSON format: If the tags input is not valid JSON, the node throws an error
"Invalid tags JSON format". Ensure the tags are correctly formatted as a JSON object with string keys and values. - Access denied errors: These indicate insufficient permissions for tagging the bucket. Verify that the API key or credentials used have the necessary IAM permissions (
s3:PutBucketTagging). - Bucket not found or incorrect bucket name: Confirm the bucket name is correct and exists in the target S3 account.
- Network or endpoint issues: Errors related to connection failures suggest checking the endpoint URL and network access.
- General S3 operation failure: The node wraps errors with messages like
"S3 operation failed: <error message>". Review the detailed error message for clues.
Links and References
- AWS S3 Bucket Tagging Documentation
- AWS SDK for JavaScript v3 - PutBucketTaggingCommand
- Amazon S3 Concepts - Tagging
If you need details about other operations or resources, feel free to ask!