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
Get Bucket Analytics
AI-generatedOverview
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, and configuration of bucket policies, lifecycle, analytics, metrics, inventory, and more.
This node is beneficial in scenarios where users need to automate complex S3 workflows within n8n, including:
- Uploading and downloading objects securely without exposing credentials by using presigned URLs.
- Managing bucket configurations like CORS, lifecycle rules, encryption, replication, and logging.
- Handling large file uploads efficiently via multipart upload.
- Querying object content using SQL expressions.
- Managing access control lists (ACLs) and tags on buckets and objects.
- Retrieving analytics, metrics, and inventory configurations for buckets.
Practical example:
A user can generate a presigned URL to allow a client application to upload a file directly to an S3 bucket without sharing AWS credentials. Another example is automating the retrieval of bucket analytics configuration to monitor usage patterns.
Properties
| Name | Meaning |
|---|---|
| Bucket Name | Name of the S3 bucket to operate on. |
| Configuration ID | Identifier for specific configurations like metrics, analytics, or inventory related to the bucket. |
For the Get Bucket Analytics operation specifically, the relevant input properties are:
| Name | Meaning |
|---|---|
| Bucket Name | The name of the S3 bucket from which to retrieve the analytics configuration. |
| Configuration ID | The unique ID of the analytics configuration to retrieve. |
Output
The output JSON structure for the Get Bucket Analytics operation includes:
bucket: The name of the bucket queried.configurationId: The ID of the analytics configuration requested.analyticsConfiguration: The detailed analytics configuration object returned by the S3 service.
Additionally, every output includes metadata fields:
operation: The operation performed (getBucketAnalytics).timestamp: ISO string timestamp when the operation was executed.success: Boolean indicating if the operation succeeded.
Example output snippet:
{
"bucket": "my-bucket-name",
"configurationId": "config-id-123",
"analyticsConfiguration": {
/* analytics configuration details */
},
"operation": "getBucketAnalytics",
"timestamp": "2024-06-01T12:00:00.000Z",
"success": true
}
The node does not output binary data for this operation.
Dependencies
- Requires an API key credential with access to an S3-compatible service.
- Uses AWS SDK clients internally to communicate with the S3 API.
- The node expects proper configuration of credentials including access key, secret key, region, and optionally endpoint and session token.
- No additional environment variables are required beyond standard n8n credential setup.
Troubleshooting
Common Issues
- Invalid Credentials: Errors related to access keys or secret keys will occur if credentials are incorrect or lack necessary permissions.
- Invalid Configuration ID: If the provided configuration ID does not exist or is malformed, the operation will fail.
- Network/Endpoint Issues: Connection errors may arise if the endpoint URL is incorrect or unreachable.
- JSON Parsing Errors: For operations requiring JSON input (not applicable here), invalid JSON format causes errors.
Error Messages and Resolutions
"S3 operation failed: <message>": General failure during the S3 API call. Check the message for specifics."Invalid Access Key ID. Please check your credentials.": The access key is incorrect or missing."Invalid Secret Access Key. Please check your credentials.": The secret key is incorrect."Access denied. Check your credentials and permissions.": The credentials do not have permission for the requested operation."Cannot connect to endpoint. Check your endpoint URL and network connection.": Network or endpoint misconfiguration.
To resolve errors, verify credentials, ensure the bucket and configuration ID exist, and confirm network connectivity.
Links and References
- AWS S3 GetBucketAnalyticsConfiguration API
- AWS SDK for JavaScript v3 - S3 Client
- Amazon S3 Analytics Configuration
If you need summaries for other operations or resources, please provide their names.