4) Put secrets in that bucket (duh)
39 karma · joined December 11, 2015
Concepts are a dime a dozen and while these are nice pieces of art I can't really take them seriously as App designs.
Focus on real products and the people making them.
Secure infrastructure isn't the one and only solution, but it certainly means that "vulnerabilities" like this are pointless unless your malicious attacker either has the remote server certs or has cracked TLS.
2) Create a S3 bucket
3) Write a bucket policy that whitelists specific IAM Roles to specific key paths within the bucket.
The way I see it, it's really a timing issue more than anything. If I were a homeowner, I could consider an equity line on my home to cover a couple months of expenses (plus I wouldn't be paying rent...), or if I had a longer credit history I could open a big card with the understanding that I would either have a good exit with the company or leave for a well-paying, more stable job at a larger company at some point and be able to repay the debt either way.
It's just the wrong time in my life to take this risk, unfortunately. It's not even the long-term effects of the risk, either, it's the change to the near-term status quo that I don't think I'll be able to handle.
From a circumstantial standpoint we're in a significant pivot that's gotten really good response but we're running short on runway on our first seed round from 1+ year ago (hence the emphasis on lessened salary).