Skip to content

S3 Object Key-Based File Access Behavior #413

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.

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

Open
FranjoMindek opened this issue Apr 2, 2025 · 0 comments
Open

S3 Object Key-Based File Access Behavior #413

FranjoMindek opened this issue Apr 2, 2025 · 0 comments
Labels
documentation Improvements or additions to documentation shouldfix

Comments

@FranjoMindek
Copy link

We allow anyone (even unauthenticated users) to download a file if they know its S3 object key. These keys are generated using a combination of user_id + UUID, making them random and hard to guess. However, once someone has access to a key, they can download the file indefinitely without additional checks.

This behavior may be acceptable in certain applications where files should be publicly accessible once their key is known. However, some use cases may require additional access controls, such as authentication or permission checks.

TODO:

  • Clearly document the current behavior in the project documentation.
  • Explain that S3 object keys alone provide access without further authorization checks.
  • Outline possible alternative approaches for stricter access control (e.g., authentication and/or authorization checks before access).
  • Consider and discuss potential use cases where this behavior is acceptable or might need modification.

This is not considered a security issue but rather a design choice that should be explicitly documented.
We should evaluate whether additional options should be provided for more restrictive access control.

@Martinsos Martinsos added documentation Improvements or additions to documentation shouldfix labels Apr 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation shouldfix
Projects
None yet
Development

No branches or pull requests

2 participants