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 operations for managing and interacting with S3-compatible object storage buckets and objects. It supports a wide range of bucket and object management tasks such as creating, deleting, listing buckets and objects, uploading and downloading files, managing access control lists (ACLs), configuring bucket policies, lifecycle rules, CORS, versioning, replication, encryption, logging, notifications, metrics, analytics, inventory, multipart uploads, and more.

The "Put Bucket Metrics" operation specifically allows users to set or update the metrics configuration for an S3 bucket. This is useful for enabling detailed monitoring and analytics on bucket usage, which can help optimize storage costs, track access patterns, and improve security auditing.

Common scenarios where this node is beneficial:

  • Automating bucket setup and configuration in cloud workflows.
  • Managing large file uploads using multipart upload features.
  • Generating presigned URLs for secure temporary access to private objects.
  • Configuring bucket-level settings like lifecycle policies, encryption, and logging.
  • Integrating S3 storage management into broader automation pipelines without manual AWS console interaction.

Practical example for "Put Bucket Metrics":

  • A user wants to enable metrics collection on a specific bucket to monitor requests filtered by a prefix (e.g., only documents folder). They provide a JSON metrics configuration specifying the filter and ID, and the node updates the bucket's metrics settings accordingly.

Properties

Name Meaning
Bucket Name Name of the S3 bucket where the metrics configuration will be applied.
Configuration ID Identifier for the specific metrics configuration to create or update.
Metrics Configuration The metrics configuration details provided as a JSON object. This defines filters and settings for the metrics.

Example of Metrics Configuration JSON:

{
  "Id": "MetricsConfigurationId",
  "Filter": {
    "Prefix": "documents/"
  }
}

Output

The output JSON contains the following fields:

  • bucket: The name of the bucket where the metrics configuration was applied.
  • configurationId: The ID of the metrics configuration that was set.
  • metricsConfiguration: The JSON object representing the metrics configuration that was applied.
  • message: Confirmation message indicating successful update.
  • operation: The operation performed, here it will be "putBucketMetrics".
  • timestamp: ISO string timestamp when the operation was executed.
  • success: Boolean indicating if the operation succeeded (true).

No binary data is output by this operation.

Example output JSON snippet:

{
  "bucket": "my-bucket-name",
  "configurationId": "MetricsConfigurationId",
  "metricsConfiguration": {
    "Id": "MetricsConfigurationId",
    "Filter": {
      "Prefix": "documents/"
    }
  },
  "message": "Bucket metrics updated successfully",
  "operation": "putBucketMetrics",
  "timestamp": "2024-06-01T12:00:00.000Z",
  "success": true
}

Dependencies

  • Requires an S3-compatible storage service with API support for bucket metrics configuration.
  • Requires credentials with permissions to modify bucket metrics configurations.
  • Uses AWS SDK for JavaScript v3 under the hood.
  • Node expects credentials providing access key ID, secret access key, optional session token, region, and optionally endpoint URL for custom S3-compatible services.
  • No additional environment variables are required beyond standard credential configuration.

Troubleshooting

  • Invalid metrics configuration JSON format:
    If the provided metrics configuration JSON is malformed, the node throws an error indicating invalid JSON format. Ensure the JSON is valid and matches the expected structure for S3 metrics configuration.

  • Access denied or insufficient permissions:
    Errors related to access permissions may occur if the credentials do not have rights to put bucket metrics. Verify IAM policies or equivalent permissions allow s3:PutBucketMetricsConfiguration.

  • Bucket not found or incorrect bucket name:
    Ensure the bucket name is correct and exists in the connected S3 service.

  • Network or endpoint connection issues:
    Check network connectivity and endpoint URL if using a custom S3-compatible service.

  • General AWS SDK errors:
    The node surfaces AWS SDK errors with messages; consult AWS documentation or your S3 provider for specific error codes.


Links and References

Discussion