Show HN: Till.sh, enhanced access controls for AWS S3

Hi everyone, I'm an independent developer who has been building an S3-related project over the past few months: https://till.sh. I wanted to share it in its MVP state to get others' opinions on the idea and to see if anyone is interested in being an early tester.

## What is it

The core concept is that Till provides an S3 API proxy that authenticates with its own custom keys. This enables us to build features that are not easily achievable with standard AWS credentials. Namely, we can add data limits to the keys, time-based expiration of keys, quickly surface access logs, and apply custom billing policies to auto-invoice users based on their data access.

## Why I built it

Till was born out of having built numerous custom data portals for clients in my professional work. These were typically organizations that have large interesting data sets (e.g. ML training sets, satellite imagery, etc) and want to share access to their data but needed some guard rails to prevent run-away costs, needed fine-detailed access tracking to analyze data access, or are looking to recoup costs associated with the creation and storage of the data. It felt like these needs were common enough to be turned into a project to allow people to start sharing their data within a few minutes. Being that Till provides an S3-compliant API, it immediately fits into many of the existing workflows and clients that end-users are already using.

## What I'm looking for

So that's the pitch. I'd love to get thoughts and critiques. Does this seem like a product you or someone you know would use? It's a bit niche so I'm admittedly struggling to get an estimate on the size of the market it could serve. Any obvious needs or use cases that I'm missing? At this stage, I'm trying to get as many people using the project as possible, so let me know your GitHub handle if you signup and I'll happily up your key-limit on the free tier.

Many thanks. Looking forward to hearing your thoughts.