3 ms·

Too bad they did not differentiate between Create and Overwrite (as far as I can tell) as that is a an important difference (I need to solve scenarios where ide

by skynss 12y ago

Too bad they did not differentiate between Create and Overwrite (as far as I can tell) as that is a an important difference (I need to solve scenarios where idempotency is needed - more than 1 worker may create exact same email message due to fault tolerance design, but at least AND at most 1 email should be sent to customer. I was hoping that the s3 filename/key would be the unique identifier and if there was separate notification for overwrite than from create, email could be sent only for create event only.)

jeffbarr 12y ago
You could use S3 versioning to distinguish the two operations.
- kolev 12y ago
  S3 versioning could be pricey and painful. Try deleting a versioned bucket! I wrote a tool that I'm gonna open-source if my employer okays it, but the pathetic part is that you get charged for each HTTP request - imagine a bucket with a billion objects and a gazillion versions!
  - hemancuso 12y ago
    http://docs.aws.amazon.com/AmazonS3/latest/API/multiobjectdeleteapi.html http://docs.aws.amazon.com/AmazonS3/latest/API/multiobjectde...
    - kolev 12y ago
      That's the API I use as well. The DELETEs are free, but GETs, PUTs, POSTs, and LISTs are not [1]. [1] http://aws.amazon.com/s3/pricing/ http://aws.amazon.com/s3/pricing/
  - evansd 12y ago
    If you're not in a huge hurry to delete the bucket you can easily set lifecycle rules to expire all versions older than 1 day (the minimum) and then just wait for S3 to delete them for you.