Event Notifications for Object Storage

[quentinhayot]

As a user, I would like to have Event Notifications for Object Storage. Like AWS does with S3, it would be nice to be able to trigger things from events happening in the containers, like object creation or deletion. Since OVH does not offer Lambda functions (yet !), one could define a custom endpoint to post to when an event is triggered.

For example, today, if a user wants to upload something to my service, I have 2 options:

• They post the file to a HTTP endpoint of mine, I forward it to S3 and I list that file in my service's database for operational stuff. This sucks because I can't take advantage of direct multi-part uploads to S3. OR
• They ping a HTTP endpoint of mine to get a signed upload URL to S3, they upload the file directly to S3 and then they ping my service again to make it aware that the upload succeeded so it can update the database. This sucks because if this last call fails, the state becomes incoherent.

With event notifications, I could have something like this:

1. Get a signed URL from the service
2. Upload directly to S3
3. S3 pings my service about the object creation

What do you guys think ?

[lason-ovh]

Hi, this is a good idea. There are few things we must consider first, namely OVH does not have a service similar to SNS/SQS or lambda. From that:

• on the short term, we could allow a user to configure a callback url in his event notification configuration
• on the long term, we could offer new services akin to SNS/SQS

What do you guys think?

[quentinhayot]

A callback URL would be AWESOME for now ! (and solve so many issues we're having right now) Notification/Queues would be PERFECT later on !

[lason-ovh]

A callback URL would be AWESOME for now ! (and solve so many issues we're having right now) Notification/Queues would be PERFECT later on !

We might need more exploration for the callback url for there are key points that need to be addressed (interface contract, authentification/authorization) --> we want to avoid developping an overly complex system knowing that it will be discarded when we will have a SNS-like product

[quentinhayot]

The callback payload could be the same as an SNS event: minimum overhead for you and almost nothing to change for the customer once the SNS service is ready. For authorization, you could just ask the customer to provide an api-key of their choice that will be passed in callback's headers.

[kikefdezl]

I could also really make use of this feature

[franjfgcarmo]

Hi @lason-ovh, is there a date to implement this feature? Thanks.

[mwullink]

This is an essential feature for many use cases, any updates on this?

[lason-ovh]

Hi @mwullink @franjfgcarmo @kikefdezl, unfortunately, this feature will not be planned this year as we have already 2 major features planned (bucket lifecycle, bucket policies) However, do not hesitate to upvote or encourage people to upvote this feature to help us prioritize it for next year