Overview
This node provides custom AWS S3 operations, specifically for managing files in an S3 bucket. The "Delete" operation under the "File" resource allows users to delete a specified file from an AWS S3 bucket. This is useful in scenarios where you want to automate cleanup of files, remove outdated or unnecessary data, or manage storage costs by deleting unused objects.
Practical examples include:
- Automatically deleting log files after processing.
- Removing temporary files generated during workflows.
- Cleaning up user-uploaded files after a certain event.
Properties
| Name | Meaning |
|---|---|
| Provider | The cloud provider, defaulting to "aws". |
| Region | The AWS region where the S3 bucket is located. Options include regions like "us-east-1", "eu-west-1", etc. |
| Access Key ID | The access key ID for authenticating with AWS. |
| Secret Access Key | The secret access key paired with the access key ID for authentication (input masked). |
| Custom Endpoint | Optional custom endpoint URL for connecting to S3-compatible services or specific endpoints. |
| Bucket Name | The name of the S3 bucket containing the file to delete. |
| File Key | The key (path) of the file within the bucket to delete. |
| Options | Additional optional parameters: |
| Version ID | Specific version ID of the file to delete if versioning is enabled on the bucket. |
Output
The output JSON contains the result of the delete operation for each input item. Typically, it will confirm success or provide details about the deletion status. The structure is an array of JSON objects, each corresponding to an input item processed.
No binary data is output by this operation.
Example output JSON snippet:
[
{
"success": true
}
]
Dependencies
- Requires valid AWS credentials (Access Key ID and Secret Access Key) with permissions to delete objects in the specified S3 bucket.
- Requires network access to AWS S3 endpoints in the selected region.
- No additional n8n-specific credentials are required beyond the provided keys.
- Optionally supports custom endpoints for S3-compatible services.
Troubleshooting
Common issues:
- Invalid or insufficient AWS credentials leading to authorization errors.
- Incorrect bucket name or file key causing "Not Found" errors.
- Attempting to delete a file version without specifying the correct Version ID when versioning is enabled.
- Network connectivity issues to AWS endpoints.
Error messages and resolutions:
- Access Denied: Check that the provided AWS credentials have
s3:DeleteObjectpermission on the target bucket. - NoSuchBucket: Verify the bucket name is correct and exists in the specified region.
- NoSuchKey: Confirm the file key is accurate and the object exists.
- InvalidVersionId: If using versioning, ensure the Version ID matches an existing version of the object.
- Network Timeout: Ensure your environment can reach AWS S3 endpoints and no firewall blocks the connection.
- Access Denied: Check that the provided AWS credentials have