WingNews logo WingNews GitHub [2]
top | item 8602955

Event Notifications for Amazon S3

61 points| degio | 11 years ago |aws.amazon.com | reply

20 comments

order
[+] dozy|11 years ago|reply
I was very excited when I saw this headline, as for a while I've hosted various things on s3 and have wanted an easy way to track when/how/by whom those things have been downloaded. Alas, that isn't a supported...I'm looking for something like: "s3:ObjectViewed:Get". Or am I mistaken and that already exists in some other form...?
[+] mritun|11 years ago|reply
S3 already has a feature where you can configure per-bucket apache style access logs which log every operation and may solve your purpose. This feature provides realtime messaging for uploads.
[+] mathgladiator|11 years ago|reply
Of all the features that S3 has shipped, this is by far my favorite. I look forward to utilizing Lambda and S3 to build an ultra cheap content management service to drive the cost of my website management to less than a $1/mo.
[+] kolev|11 years ago|reply
How is this idea any better (and cheaper) than a static site generator like Jekyll?
[+] toomuchtodo|11 years ago|reply
You could definitely kill shared hosting services (with static sites) with this sort of offering. They could never compete at S3 pricing.
[+] kolev|11 years ago|reply
Nice feature, but, again, not available in CloudFormation. I understand the challenge to coordinate releases, I can live with a week or two lag, but usually it's months - CloudFormation still doesn't support basic AWS services. I really am considering abandoning this gem, which is highly neglected and underutilized. Terraform [1] looks like something I can extend myself easily if the upstream doesn't support something just yet and contribute it as a pull request.

[1] https://terraform.io/

[+] skynss|11 years ago|reply
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|11 years ago|reply
You could use S3 versioning to distinguish the two operations.
[+] hemancuso|11 years ago|reply
Very cool!

Are there any ordering guarantees for these notifications? Specifically the order in which objects were created? It would be nice to be able to generate a meaningful event log.

[+] johne20|11 years ago|reply
At first glance, this combined with Lambda would make for an awesome server-less image transformation setup.
[+] strick|11 years ago|reply
Have I missed something or is there no way to get notified when an object gets deleted?