new plugin RWs3

[gitpoldan]

Plugin Submission

Plugin information

• Author: gitpoldan
• Plugin name: RWs3
• Version: 0.0.1
• Source repository: https://github.com/gitpoldan/dify/tree/main/polden-plugins/RWs3
• Contact: bv2020donch@gmail.com

Submission type

• New plugin
• Version update

What changed

Simple S3/MinIO tool plugin with four operations: list, read, write, delete.
Connects to user-configured AWS S3 or MinIO (path-style for custom endpoints).
Optional credential prefix guards all keys inside a namespace. Structured
{ ok, data } / { ok, error } responses for LLM workflows and agents.

Uniqueness vs generic S3 tools: MinIO path-style + AWS S3 from one provider,
prefix guard, configurable read/write byte limits, idempotent delete.

Risk level

• Low risk
• Medium risk
• High risk

Required checks

• I have read and followed the Marketplace submission requirements.
• I have read and comply with the Plugin Developer Agreement.
• I tested this plugin on Dify Community Edition and Dify Cloud, or documented any limitation below.
• The package contains only files needed at runtime.
• The package does not contain secrets, local credentials, .env files, .git directories, virtual environments, caches, logs, or IDE files.
• The package does not contain executables or bundled binaries, or I explained why they are required below.
• The plugin README includes setup steps, usage instructions, required APIs or credentials, connection requirements, and the source repository link.
• The plugin includes PRIVACY.md or a hosted privacy policy, and manifest.yaml references it.
• All user-facing text is primarily in English, with any localized README files following the i18n guidance.

Security and privacy notes

This plugin connects to object storage endpoints configured by the workspace
admin (Amazon S3 or MinIO). S3 credentials (access key, secret key, bucket,
endpoint) are stored in the Dify tool provider and used only to authenticate
against the user's own bucket.

• Third-party exposure: AWS S3 and/or MinIO (user-configured endpoint).
  Object keys and file content from tool calls are transmitted to that endpoint
  for list, read, write, and delete operations.
• Sensitive operations: read, write, and delete objects in the user's bucket;
  optional prefix guard restricts keys to a namespace inside the bucket.
• No author infrastructure: the plugin does not persist, log, or transmit
  data to the plugin author. No telemetry or analytics.
• Credentials: handled by the Dify runtime; not sent to third parties other
  than the configured storage endpoint.
• User control: workspace admins choose bucket, endpoint, and credentials.
  See PRIVACY.md in the package for full details.

Local validation

• pip install -r requirements.txt — OK
• pytest tests/ — OK (FakeS3Store, no network)
• Package built with forward-slash zip paths (python package.py)
• Credential validation via head_bucket() on provider save

Reviewer notes

Four tools: s3_list, s3_read, s3_write, s3_delete. Text-only write (UTF-8)
in v0.0.1; read responses may be truncated by max_read_bytes.

Russian documentation: readme/README_ru_RU.md inside the package.

Maintenance

I will triage issues at https://github.com/gitpoldan/dify/issues (plugin path:
polden-plugins/RWs3) and respond to Marketplace feedback.

Test plan

• Credentials validation (head_bucket) against MinIO
• s3_write → s3_read → s3_list → s3_delete roundtrip
• Prefix guard rejects path traversal

[gitpoldan]

Metadata updated in the package; please approve the workflow run for pre-check.

[gitpoldan]

The missing sections have been added to the PR.