N8N Tools - S3 EnhancedInstall

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 logging, lifecycle, CORS, policies, tagging, versioning, and more.

The "Get Bucket Logging" operation specifically retrieves the logging configuration of a specified S3 bucket, which is useful for auditing and monitoring access to the bucket. This can help users understand where access logs are being stored and verify if logging is enabled.

Common scenarios:

• Auditing bucket access by retrieving current logging settings.
• Verifying compliance by checking if logging is properly configured.
• Integrating bucket logging status into automated workflows or dashboards.

Example:
A user wants to check if their "my-bucket-name" has logging enabled and where the logs are sent. Using this node with the "Get Bucket Logging" operation and specifying the bucket name will return the logging configuration details.

Properties

Output

The output JSON contains the following fields:

• bucket: The name of the bucket queried.
• loggingEnabled: An object representing the logging configuration of the bucket. If logging is enabled, it includes details such as:
  • TargetBucket: The destination bucket where logs are stored.
  • TargetPrefix: The prefix applied to log file names in the target bucket.

If logging is not enabled, this field may be empty or null.

Additionally, the output includes metadata fields added by the node execution logic:

• operation: The operation performed (e.g., "getBucketLogging").
• timestamp: ISO string timestamp when the operation was executed.
• success: Boolean indicating whether the operation succeeded.

Dependencies

• Requires an S3-compatible storage service accessible via AWS SDK v3.
• Requires credentials providing access key ID, secret access key, and optionally session token, region, endpoint URL, and path style setting.
• The node depends on the AWS SDK client for S3 and related presigning utilities.
• Proper permissions must be granted to the credentials to perform the GetBucketLogging API call.

Troubleshooting

• Common issues:

  • Invalid or missing credentials: Ensure that the API key and secret are correctly configured.
  • Insufficient permissions: The credentials must have permission to call GetBucketLogging on the specified bucket.
  • Incorrect bucket name: Verify the bucket name is correct and exists in the connected S3 service.
  • Network or endpoint errors: Check network connectivity and endpoint URL if using a custom S3-compatible service.

• Error messages:

  • "S3 operation failed: <message>": General failure during the API call; inspect the message for details.
  • "Access denied. Check your credentials and permissions.": Permissions issue; update IAM policies or credentials.
  • "Cannot connect to endpoint. Check your endpoint URL and network connection.": Network or endpoint misconfiguration.
  • "Invalid Access Key ID. Please check your credentials." or "Invalid Secret Access Key. Please check your credentials.": Credential errors.

To resolve errors, verify credentials, permissions, bucket existence, and network connectivity.

Links and References

• AWS S3 GetBucketLogging API Documentation
• AWS SDK for JavaScript v3 - S3 Client
• Amazon S3 Bucket Logging Overview