Skip to content
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

Update page.md #310

Merged
merged 3 commits into from
Dec 15, 2023
Merged

Update page.md #310

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c94a753
Update page.md
amozoss Dec 15, 2023
11e3ae7
Update page.md
amozoss Dec 15, 2023
31c2db3
Merge branch 'main' into amozoss-patch-2
amozoss Dec 15, 2023
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
2 changes: 1 addition & 1 deletion app/learn/concepts/multi-tenant-data/page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ Here, you will notice that two tenants are sharing a single bucket. Each tenant

In this model, using tenant-identifying information in the Object Key Path Prefix is acceptable as all Object Key Path Prefix data is encrypted.

Note that it is possible to store data in an encrypted state but enable unencrypted metadata storage to support lexicographical sorting. Not that when using this option, it’s extremely important to be thoughtful about how authorization and access restrictions are implemented to avoid inadvertent disclosure of tenant-specific path-prefix information.
Note that it is possible to store data in an encrypted state but enable unencrypted metadata storage to support lexicographical sorting. Note that when using this option, it’s extremely important to be thoughtful about how authorization and access restrictions are implemented to avoid inadvertent disclosure of tenant-specific path-prefix information.

One challenge that can surface is that the activity for your S3 keys is unlikely to be evenly distributed across your tenants. In this model, you will need to separately monitor and meter usage per tenant. Storj does not aggregate usage information at the Object Key Path Prefix level.

Expand Down