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 integration with S3-compatible storage services, enabling a wide range of bucket and object management operations. It supports advanced features such as generating presigned URLs for secure temporary access, multipart uploads for large files, and detailed bucket configurations including policies, lifecycle rules, CORS, tagging, versioning, and more.
The "Get Bucket Policy" operation specifically retrieves the policy document associated with a given S3 bucket. This is useful for auditing, compliance checks, or dynamically adjusting workflows based on bucket permissions.
Common scenarios:
- Automating retrieval of bucket policies to verify access controls.
- Integrating bucket policy data into monitoring or reporting systems.
- Using bucket policies programmatically to enforce security standards.
Practical example:
A workflow that periodically fetches the bucket policy of critical buckets to ensure they comply with organizational security policies, alerting if unexpected changes are detected.
Properties
| Name | Meaning |
|---|---|
| Bucket Name | The name of the S3 bucket whose policy you want to retrieve. |
Output
The output JSON contains the following structure:
{
"bucket": "string", // The name of the bucket queried
"policy": { // The parsed bucket policy as a JSON object; null if no policy exists
// Bucket policy JSON structure according to AWS S3 policy specification
},
"operation": "getBucketPolicy", // The operation performed
"timestamp": "ISO8601 string", // Timestamp of execution
"success": true // Indicates successful execution
}
If the bucket has no policy set, the policy field will be null.
Dependencies
- Requires an S3-compatible storage service endpoint.
- Requires credentials with sufficient permissions to call the
GetBucketPolicyAPI on the target bucket. - The node uses AWS SDK v3 under the hood.
- Credentials must include access key ID, secret access key, and optionally session token, region, and endpoint URL.
- No additional environment variables are required beyond standard credential configuration.
Troubleshooting
Access Denied Errors:
If the node returns an access denied error, verify that the provided credentials have permission to performGetBucketPolicyon the specified bucket.Invalid Bucket Name:
Ensure the bucket name is correct and exists in the connected S3 service.No Policy Found:
If thepolicyfield isnull, it means the bucket currently has no policy attached.Network or Endpoint Issues:
Connection errors may indicate incorrect endpoint URLs or network connectivity problems.JSON Parsing Errors:
The node parses the bucket policy JSON returned by the service. Malformed policies (rare) could cause parsing issues.