You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When storing data in S3, it can only be stored in the root directory. Cannot store inside nested folders.
Describe the solution you'd like
Specify an option, such as Prefix, to set where the data is stored in the S3 bucket. BucketName/FolderName/index
The text was updated successfully, but these errors were encountered:
In some organizations, the S3 buckets are managed by IT, while each team only manages the contents of their own assigned bucket. Without being able to create buckets, the team could define a prefix for Loki data on their own bucket. While this use case doesn't apply specifically to me, it could provide teams with some independence.
In my particular case, I've been having permission issues after creating new buckets, and until I'm able to sort it, or as a permanent alternative, I could have had Loki run in one of the other buckets that are working fine, under a prefix.
Is your feature request related to a problem? Please describe.
When storing data in S3, it can only be stored in the root directory. Cannot store inside nested folders.
Describe the solution you'd like
Specify an option, such as
Prefix
, to set where the data is stored in the S3 bucket.BucketName/FolderName/index
The text was updated successfully, but these errors were encountered: