Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: S3mini – Tiny and fast S3-compatible client, no-deps, edge-ready

github.com

Post reply on HN
Print view View original

31–40 of 105 posts

Re: Show HN: S3mini – Tiny and fast S3-compatible client, no-deps, edge-ready

#31

Post by neon_me »

akouri wrote: post #29

This is awesome! Been waiting for something like this to replace the bloated SDK Amazon provides. Important question— is there a pathway to getting signed URLs?

For now, unfortunately, no - no signed URLs are supported. It wasn't my focus (use case), but if you find a simple/minimalistic way to implement it, I can help you with that to integrate it.

From my helicopter perspective, it adds extra complexity and size, which could maybe be ideal for a separate fork/project?

Re: Show HN: S3mini – Tiny and fast S3-compatible client, no-deps, edge-ready

#32

Post by throawayonthe »

neon_me wrote: post #24
yard2010 wrote: post #21

Tangibly related: Bun has a built-in S3-compatible client. Bun is a gift, if you're using npm consider making the switch.

is there a way to wrap their s3 client for use in HonoJS/CF workers?

i assume you can just use it[0] in your project and then build (using bun) for cf workers[1]

[0] https://bun.sh/docs/api/s3

[1] https://hono.dev/docs/getting-started/cloudflare-workers \ (https://bun.sh/docs/api/workers ?)

Re: Show HN: S3mini – Tiny and fast S3-compatible client, no-deps, edge-ready

#33

Post by biorach »

ChocolateGod wrote: post #26
yard2010 wrote: post #21

Tangibly related: Bun has a built-in S3-compatible client. Bun is a gift, if you're using npm consider making the switch.

I tried to go this route of using Bun for everything (Bun.serve, Bun.s3 etc), but was forced back to switch back to NodeJS proper and Express/aws-sdk due to Bun not fully implementing Nodes APIs.

What were the most significant missing bits?

Re: Show HN: S3mini – Tiny and fast S3-compatible client, no-deps, edge-ready

#34

Post by maxmcd »

terhechte wrote: post #27
dev_l1x_be wrote: post #5

for Node. These are nice projects. I had a few rounds with Rust S3 libraries and having a simple low or no dep client is much needed. The problem is that you start to support certain features (async, http2, etc.) and your nice nodep project is starting to grow.

I had the same issue recently and used https://crates.io/crates/rusty-s3

also: https://crates.io/crates/object_store

Re: Show HN: S3mini – Tiny and fast S3-compatible client, no-deps, edge-ready

#36

Post by shortformblog »

This is good to have. A few months ago I was testing a S3 alternative but running into issues getting it to work. Turned out it was because AWS made changes to the tool that had the effect of blocking non-first-party clients. Just sheer chance on my end, but I imagine that was infuriating for folks who have to rely on that client. There is an obvious need for a compatible client like this that AWS doesn’t manage.

Re: Show HN: S3mini – Tiny and fast S3-compatible client, no-deps, edge-ready

#37

Post by huntaub »

vbezhenar wrote: post #15
tom1337 wrote: post #11

Earlier quoted context omitted.

checksumming does make sense because it ensures that the file you've transferred is complete and what was expected. if the checksum of the file you've downloaded differs from the server gave you, you should not process the file further and throw an error (worst case would probably be a man in the middle attack, not so worse cases being packet loss i guess)

TLS ensures that stream was not altered. Any further checksums are redundant.

This is actually not the case. The TLS stream ensures that the packets transferred between your machine and S3 are not corrupted, but that doesn't protect against bit-flips which could (though, obviously, shouldn't) occur from within S3 itself. The benefit of an end-to-end checksum like this is that the S3 system can store it directly next to the data, validate it when it reads the data back (making sure that nothing has changed since your original PutObject), and then give it back to you on request (so that you can also validate it in your client). It's the only way for your client to have bullet-proof certainty of integrity the entire time that the data is in the system.

Re: Show HN: S3mini – Tiny and fast S3-compatible client, no-deps, edge-ready

#38

Post by eknkc »

biorach wrote: post #33
ChocolateGod wrote: post #26

Earlier quoted context omitted.

I tried to go this route of using Bun for everything (Bun.serve, Bun.s3 etc), but was forced back to switch back to NodeJS proper and Express/aws-sdk due to Bun not fully implementing Nodes APIs.

What were the most significant missing bits?

The worst thing is issues without any visibility.

The other day I was toying with the MCP server (https://github.com/modelcontextprotocol/typescript-sdk). I default to bun these days and the http based server simply did not register in claude or any other client. No error logs, nothing.

After fiddling with my code I simply tried node and it just worked.

Re: Show HN: S3mini – Tiny and fast S3-compatible client, no-deps, edge-ready

#40

Post by pier25 »

dev_l1x_be wrote: post #5

for Node. These are nice projects. I had a few rounds with Rust S3 libraries and having a simple low or no dep client is much needed. The problem is that you start to support certain features (async, http2, etc.) and your nice nodep project is starting to grow.

for JS

> It runs on Node, Bun, Cloudflare Workers, and other edge platforms

Post reply on HN