## Feature Request ### Description <!-- A clear and concise description of the proposed feature. --> ### Problem or Use Case <!-- What problem does this feature solve, or how does it enhance Chorus (e.g., S3 compatibility, performance, usability)? --> ### Proposed Solution <!-- Describe the feature or enhancement in detail. Include: - How it should work. - Any specific requirements (e.g., support for a new S3 provider, configuration options). --> ### Alternatives Considered <!-- Any alternative approaches or solutions you’ve considered. --> ### Backwards compatibility <!-- Mention how this feature may affect backwards-compatibility with current chorus version: - API changes - Redis metadata --> ### Additional Context <!-- Any other relevant information (e.g., examples from other tools, diagrams, or references). **Note**: By submitting this issue, you agree to follow our [Code of Conduct](CODE_OF_CONDUCT.md) and license contributions under the [Apache 2.0 License](LICENSE). -->
Feature Request
Description
Problem or Use Case
Proposed Solution
Alternatives Considered
Backwards compatibility
Additional Context