Skip to content

docs: document S3_ADDRESS_STYLE variable and add Tigris example #734

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
RiskeyL merged 3 commits into from
Apr 9, 2026
Merged

docs: document S3_ADDRESS_STYLE variable and add Tigris example #734

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e1422ae
add fix to s3 config
davidmyriel Apr 8, 2026
373ff6e
docs: add S3_ADDRESS_STYLE variable, remove provider-specific content
RiskeyL Apr 9, 2026
24648f1
translate: sync S3_ADDRESS_STYLE variable to zh and ja
RiskeyL Apr 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion en/self-host/configuration/environments.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -361,7 +361,8 @@ For all available schemes and their configuration options, see the [OpenDAL serv
| `S3_BUCKET_NAME` | `difyai` | S3 bucket name. |
| `S3_ACCESS_KEY` | (empty) | S3 Access Key. Not needed when using IAM roles. |
| `S3_SECRET_KEY` | (empty) | S3 Secret Key. Not needed when using IAM roles. |
| `S3_USE_AWS_MANAGED_IAM` | `false` | Use AWS IAM roles (EC2 instance profile, ECS task role) instead of explicit access key/secret key. When enabled, boto3 auto-discovers credentials from the instance metadata. |
| `S3_ADDRESS_STYLE` | `auto` | S3 addressing style: `auto`, `path`, or `virtual`. Controls whether bucket names appear in the URL path (`path`) or as a subdomain (`virtual`). Only applies when `S3_USE_AWS_MANAGED_IAM` is `false`. |
| `S3_USE_AWS_MANAGED_IAM` | `false` | Use AWS IAM roles (EC2 instance profile, ECS task role) instead of explicit access key/secret key. When enabled, credentials are auto-discovered from the instance metadata. |

</Accordion>

Expand Down
3 changes: 2 additions & 1 deletion ja/self-host/configuration/environments.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -363,7 +363,8 @@ Difyがアップロードファイル、データセットドキュメント、
| `S3_BUCKET_NAME` | `difyai` | S3バケット名。 |
| `S3_ACCESS_KEY` | （空） | S3 Access Key。IAMロール使用時は不要です。 |
| `S3_SECRET_KEY` | （空） | S3 Secret Key。IAMロール使用時は不要です。 |
| `S3_USE_AWS_MANAGED_IAM` | `false` | 明示的なaccess key/secret keyの代わりにAWS IAMロール（EC2インスタンスプロファイル、ECSタスクロール）を使用します。有効時、boto3がインスタンスメタデータから資格情報を自動検出します。 |
| `S3_ADDRESS_STYLE` | `auto` | S3アドレッシングスタイル：`auto`、`path`、または `virtual`。バケット名をURLパスに含める（`path`）か、サブドメインとして使用する（`virtual`）かを制御します。`S3_USE_AWS_MANAGED_IAM` が `false` の場合のみ有効です。 |
| `S3_USE_AWS_MANAGED_IAM` | `false` | 明示的なaccess key/secret keyの代わりにAWS IAMロール（EC2インスタンスプロファイル、ECSタスクロール）を使用します。有効時、インスタンスメタデータから資格情報を自動検出します。 |

</Accordion>

Expand Down
3 changes: 2 additions & 1 deletion zh/self-host/configuration/environments.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -363,7 +363,8 @@ sentinel://<redis_username>:<redis_password>@<sentinel_host>:<sentinel_port>/<re
| `S3_BUCKET_NAME` | `difyai` | S3 存储桶名称。 |
| `S3_ACCESS_KEY` | （空） | S3 Access Key。使用 IAM 角色时不需要。 |
| `S3_SECRET_KEY` | （空） | S3 Secret Key。使用 IAM 角色时不需要。 |
| `S3_USE_AWS_MANAGED_IAM` | `false` | 使用 AWS IAM 角色（EC2 实例配置文件、ECS 任务角色）代替显式的 access key/secret key。启用后 boto3 从实例元数据自动发现凭证。 |
| `S3_ADDRESS_STYLE` | `auto` | S3 寻址方式：`auto`、`path` 或 `virtual`。控制存储桶名称出现在 URL 路径中（`path`）还是作为子域名（`virtual`）。仅在 `S3_USE_AWS_MANAGED_IAM` 为 `false` 时生效。 |
| `S3_USE_AWS_MANAGED_IAM` | `false` | 使用 AWS IAM 角色（EC2 实例配置文件、ECS 任务角色）代替显式的 access key/secret key。启用后从实例元数据自动发现凭证。 |

</Accordion>

Expand Down
Loading