Add support for custom S3 endpoints in `plugin-node`
Is your feature request related to a problem? Please describe.
The plugin-node gives you an S3-compatible API. However, it assumes you're using AWS S3; it doesn't let you use S3-compatible tooling because the request URL is not configurable.
Describe the solution you'd like
We should allow the plugin to take an additional (optional) env var called AWS_S3_ENDPOINT, which if set, will use the URL for bucket operations. The plugin-node only needs a small change to handle the URL, ensuring the setup is backward compatible.
Describe alternatives you've considered
Using existing AWS S3 configuration only, but this limits flexibility.
Additional context
Implementing this feature will enhance compatibility with other S3-compatible services, improving the usability of the plugin-node for diverse storage solutions.
Related Issues/PRs