Cloud file conversion security model (S3-only, 24h retention)
Cloud file conversion security model (S3-only, 24h retention)
Hi HN — I’m building Docpose.cloud (online file conversion + API). File processing is a trust problem, so I wrote a security + processing architecture page that explains exactly how files move through the system. Highlights: S3-only pipeline: workers read from object storage and write results back No permanent local disk persistence on workers Source files deleted immediately after processing Converted files expire after 24 hours by default Operational logs kept up to 30 days (metadata only, no file contents) I’m posting this because security questions come up every time someone evaluates file-processing infrastructure. Feedback welcome — especially on what you’d want clarified for a vendor security review.
Share cardActual performance
Launch Intel predictions
Analyze your own launch →Correct prediction on native model
Similar products
Viewing S3 File on LocalStack
JuiceFS 1.0, A POSIX, HDFS, and S3 compliant cloud file system
Kev – S3 and Redis as Datastores (with Redis Indexing)
Cache for S3
S3Drizzle – S3 Logs File Exfiltration PoC
Your go-to file conversion platform
S3tk – A Security Toolkit for Amazon S3
File conversion service
S3Scanner – Find and dump open S3 buckets
Kev 0.7 – S3 as Datastore (now with S3-only back end)