3 ms·
This is excellent. I love the simplicity of it. I also love it that files can't be overwritten - clearly you thought this trough! I am currently appending larg
by DenisM 16y ago
This is excellent. I love the simplicity of it.
I also love it that files can't be overwritten - clearly you thought this trough! I am currently appending large random strings to my S3 uploads to avoid overwrites.
However, I would prefer to have the files stored in my own AWS account. I'm thinking I would create a special bucket, give you the credentials for it and you would run the EC2 instances required to accept the files and store them there. You would bill me per URL and for the bandwidth, while Amazon will bill me for the storage directly.
- DenisM 16y agoAlso, I need similar service for my EBS volumes - you would trigger backup of the EBS volume on set schedule and you would purge old backups as needed, AWS will bill me for storage and bandwidth directly while you will bill me a fixed sum for each volume (as you have no variable costs in this picture).
- mleonhard 16y agoI'm glad that you like the API. :) I did think a lot about it, but it still needs a lot of work. Why would you like to use your own S3 bucket as the backing store? I would love to talk with you more about this.
- DenisM 16y agoBecause I want to retain ownership of the data. Transmission is transient and I'm ok with outsourcing that to a little-known company, however storage is lasting and I want to retain meaningful control over it. I understand that ties you to AWS and restricts your future options, but this might be a good place for you to start - targeting existing AWS users who need a little bit of extra automation.