mysterious-dinner-77632
08/18/2026, 11:17 AMancient-wolf-19325
08/18/2026, 11:17 AM<project>/<domain>/<run-name>/<action-name>/..., so all project data is stored under project-specific prefixes within a single bucket. However, IAM policies and bucket policies can be used to scope access to specific prefixes, enabling RBAC at the project level. This means you can restrict access so that only the appropriate service accounts or IAM roles for a given project can access their corresponding prefix in the bucket, preventing cross-project access via the object store. See Object store layout for details.
You will need to configure your cloud provider's IAM or bucket policies to enforce these prefix-based restrictions, as Flyte itself does not enforce RBAC within the bucketβthis is handled at the storage layer. Would you like more detail on how to set up these policies for AWS S3 or another provider?
Sources:
- Object store layout π 0 button π 0 button π‘ Hint: Mention @herald in the thread for followups.mysterious-dinner-77632
08/18/2026, 11:18 AMancient-wolf-19325
08/18/2026, 11:18 AMmysterious-dinner-77632
08/18/2026, 11:19 AMancient-wolf-19325
08/18/2026, 11:19 AMmysterious-dinner-77632
08/18/2026, 11:23 AMancient-wolf-19325
08/18/2026, 11:23 AMcharts directory of the Flyte GitHub repository, including subdirectories like flyte-binary, flyte-devbox, and flyteconnector. For example, see charts/flyte-binary and charts/flyte-devbox.
If you do not see them, ensure you are viewing the latest branch (such as main), as the charts are present there. Would you like more detail on the chart structure or how to use them?
Sources:
- charts/flyte-binary/README.md
- charts/flyte-devbox π 0 button π 0 button π‘ Hint: Mention @herald in the thread for followups.mysterious-dinner-77632
08/18/2026, 11:24 AMancient-wolf-19325
08/18/2026, 11:24 AM