N8N Tools - S3 Enhanced icon

N8N Tools - S3 Enhanced

Enhanced S3 operations with presigned URLs, multipart upload, and advanced features

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 GetBucketPolicy API 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 perform GetBucketPolicy on the specified bucket.

  • Invalid Bucket Name:
    Ensure the bucket name is correct and exists in the connected S3 service.

  • No Policy Found:
    If the policy field is null, 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.


Links and References

Discussion