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

The "Delete Bucket CORS" operation specifically deletes the Cross-Origin Resource Sharing (CORS) configuration from a specified S3 bucket. This is useful when you want to remove any existing CORS rules that allow cross-origin requests to your bucket, effectively disabling CORS for that bucket.

Common scenarios:

• Removing outdated or incorrect CORS settings from an S3 bucket.
• Resetting bucket CORS configuration as part of security hardening.
• Automating bucket configuration cleanup in deployment pipelines.

Practical example:
You have a bucket used by a web application that previously allowed cross-origin requests from multiple domains. You now want to restrict access and remove all CORS rules. Using this node's "Delete Bucket CORS" operation, you can programmatically delete the CORS configuration without manually accessing the AWS console.

Properties

Output

The output JSON object for the "Delete Bucket CORS" operation contains:

• bucket: The name of the bucket where the CORS configuration was deleted.
• message: A confirmation string indicating successful deletion of the bucket's CORS configuration.

Example output JSON:

{
  "bucket": "my-bucket-name",
  "message": "Bucket CORS configuration deleted successfully"
}

No binary data is produced by this operation.

Dependencies

• Requires valid credentials for an S3-compatible service with permissions to delete bucket CORS configurations.
• The node uses the AWS SDK for JavaScript v3 under the hood.
• Requires configuration of an API key credential with accessKeyId, secretAccessKey, optional sessionToken, region, and optionally endpoint and forcePathStyle parameters.
• Network connectivity to the S3-compatible endpoint is necessary.

Troubleshooting

Common issues:

• Invalid or missing credentials: The operation will fail if the provided API keys are incorrect or lack sufficient permissions to modify bucket CORS settings.
• Bucket not found: If the specified bucket does not exist or is inaccessible, the operation will throw an error.
• Network connectivity problems: Endpoint misconfiguration or network issues can prevent communication with the S3 service.

Error messages and resolutions:

• "S3 operation failed: AccessDenied"
  Cause: Insufficient permissions.
  Resolution: Verify that the API key has permission to delete bucket CORS configurations.

• "S3 operation failed: NoSuchBucket"
  Cause: The specified bucket does not exist.
  Resolution: Check the bucket name for typos and ensure it exists.

• "S3 operation failed: InvalidAccessKeyId" or "SignatureDoesNotMatch"
  Cause: Incorrect access key or secret key.
  Resolution: Confirm the correctness of the API credentials.

• "S3 operation failed: ENOTFOUND" or "ECONNREFUSED"
  Cause: Cannot reach the endpoint URL.
  Resolution: Verify the endpoint URL and network connectivity.

Links and References

• AWS S3 DeleteBucketCors API Documentation
• AWS SDK for JavaScript v3 - S3Client
• Cross-Origin Resource Sharing (CORS) in Amazon S3