HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
dan-v
cloudshell-store
Go2026–2026
dan-v / cloudshell-store

cloudshell-store

A distributed file store built on AWS CloudShell's free persistent storage

2Distinct people
2Mentions
0Explicit recommenders
59GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A distributed file store built on AWS CloudShell's free persistent storage

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2026-03-19 08:20:25 UTC to 2026-03-20 02:03:11 UTC.

012026-03-19 08:00:00 UTC to 2026-03-19 09:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMar 19, 08:002026-03-19 09:00:00 UTC to 2026-03-19 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-19 10:00:00 UTC to 2026-03-19 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-19 11:00:00 UTC to 2026-03-19 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-19 12:00:00 UTC to 2026-03-19 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-19 13:00:00 UTC to 2026-03-19 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-19 14:00:00 UTC to 2026-03-19 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-19 15:00:00 UTC to 2026-03-19 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-19 16:00:00 UTC to 2026-03-19 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-19 17:00:00 UTC to 2026-03-19 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 19, 17:002026-03-19 18:00:00 UTC to 2026-03-19 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-19 19:00:00 UTC to 2026-03-19 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-19 20:00:00 UTC to 2026-03-19 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-19 21:00:00 UTC to 2026-03-19 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-19 22:00:00 UTC to 2026-03-19 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-19 23:00:00 UTC to 2026-03-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-20 00:00:00 UTC to 2026-03-20 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-20 01:00:00 UTC to 2026-03-20 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-20 02:00:00 UTC to 2026-03-20 03:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMar 20, 02:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 19, 08:002026-03-19 08:00:00 UTC2026-03-19 09:00:00 UTC110
Mar 19, 09:002026-03-19 09:00:00 UTC2026-03-19 10:00:00 UTC000
Mar 19, 10:002026-03-19 10:00:00 UTC2026-03-19 11:00:00 UTC000
Mar 19, 11:002026-03-19 11:00:00 UTC2026-03-19 12:00:00 UTC000
Mar 19, 12:002026-03-19 12:00:00 UTC2026-03-19 13:00:00 UTC000
Mar 19, 13:002026-03-19 13:00:00 UTC2026-03-19 14:00:00 UTC000
Mar 19, 14:002026-03-19 14:00:00 UTC2026-03-19 15:00:00 UTC000
Mar 19, 15:002026-03-19 15:00:00 UTC2026-03-19 16:00:00 UTC000
Mar 19, 16:002026-03-19 16:00:00 UTC2026-03-19 17:00:00 UTC000
Mar 19, 17:002026-03-19 17:00:00 UTC2026-03-19 18:00:00 UTC000
Mar 19, 18:002026-03-19 18:00:00 UTC2026-03-19 19:00:00 UTC000
Mar 19, 19:002026-03-19 19:00:00 UTC2026-03-19 20:00:00 UTC000
Mar 19, 20:002026-03-19 20:00:00 UTC2026-03-19 21:00:00 UTC000
Mar 19, 21:002026-03-19 21:00:00 UTC2026-03-19 22:00:00 UTC000
Mar 19, 22:002026-03-19 22:00:00 UTC2026-03-19 23:00:00 UTC000
Mar 19, 23:002026-03-19 23:00:00 UTC2026-03-20 00:00:00 UTC000
Mar 20, 00:002026-03-20 00:00:00 UTC2026-03-20 01:00:00 UTC000
Mar 20, 01:002026-03-20 01:00:00 UTC2026-03-20 02:00:00 UTC000
Mar 20, 02:002026-03-20 02:00:00 UTC2026-03-20 03:00:00 UTC110

What Hacker News says

2 sources

Show HN: I built a distributed file store on top of AWS CloudShell

AWS CloudShell gives you a free Linux environment with ~1GB of persistent home storage in each region. I wondered: what if you could stitch a bunch of these together into a single erasure-coded storage pool? Files are split into chunks, encoded with Reed-Solomon (6 data + 3 parity shards), encrypted with AES-256-GCM, and scattered across regions. Any 6 of 9 shards can reconstruct the original - so you can lose entire regions and still get your files back. The fun technical bits: * CloudShell has no public API - I reverse-engineered the browser's console calls to programmatically create environments, manage sessions, and send heartbeats. * CloudShell instances are behind NAT with no inbound access. Both sides use STUN to discover their public endpoints, then punch UDP holes toward each other. QUIC runs over the punched connection. * A Pyth
Read the rest
on agent gets deployed to each environment over the SSM session, handling shard storage and the QUIC server. GitHub: https://github.com/dan-v/cloudshell-store
2 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.