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 versioning, lifecycle, CORS, policies, tagging, logging, notifications, replication, encryption, website hosting, metrics, analytics, inventory, request payment, and acceleration.

The "Get Bucket Versioning" operation specifically retrieves the versioning configuration of a specified S3 bucket, including whether versioning is enabled or suspended and the status of MFA delete protection.

Common scenarios:

• Checking if versioning is enabled on a bucket before performing operations that depend on object versions.
• Auditing bucket settings to ensure compliance with data retention policies.
• Automating infrastructure checks in workflows that manage S3 buckets.

Practical example:
A workflow could use this node to verify that versioning is enabled on a backup bucket before uploading critical files, ensuring that previous versions are retained for recovery purposes.

Properties

Output

The output JSON object for the "Get Bucket Versioning" operation includes:

• bucket: The name of the bucket queried.
• status: The versioning status of the bucket. Possible values typically include "Enabled" or "Suspended".
• mfaDelete: The MFA (Multi-Factor Authentication) delete status, indicating whether MFA delete protection is "Enabled" or "Disabled".

Example output JSON:

{
  "bucket": "my-bucket-name",
  "status": "Enabled",
  "mfaDelete": "Disabled",
  "operation": "getBucketVersioning",
  "timestamp": "2024-06-01T12:00:00.000Z",
  "success": true
}

Dependencies

• Requires an S3-compatible service endpoint accessible via network.
• Needs credentials providing access key ID, secret access key, and optionally session token.
• The node uses AWS SDK clients internally to communicate with the S3 API.
• Proper permissions must be granted to the credentials to perform the GetBucketVersioning API call.
• No additional environment variables are required beyond standard credential configuration.

Troubleshooting

• Common issues:

  • Invalid or missing credentials can cause authentication failures.
  • Network connectivity problems or incorrect endpoint URLs may prevent connection.
  • Insufficient permissions on the provided credentials will result in access denied errors.
  • Specifying a non-existent bucket will cause errors from the S3 service.

• Error messages and resolutions:

  • "Access denied. Check your credentials and permissions."
    Ensure the credentials have permission to call GetBucketVersioning on the target bucket.
  • "Cannot connect to endpoint. Check your endpoint URL and network connection."
    Verify the endpoint URL and network accessibility.
  • "S3 operation failed: <error message>"
    Review the specific error message for details; it often indicates misconfiguration or permission issues.

Links and References

• AWS S3 GetBucketVersioning API Documentation
• AWS SDK for JavaScript v3 - S3 Client
• Amazon S3 Versioning Overview