You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Was curious what it would take to wire up EventBridge support as an alternative to using webhooks for notifications.
Use Case
We leverage remotion in an AWS environment which makes frequent use of EventBridge. We had to spin up a small lambda+apigateway service to handle the webhook completion notifications from remotion. That webhook lambda is a level of abstraction that we'd rather do away with, since all it does is send an event to EventBridge.
Possible Solution
Remotion is lambda-based, and it would make sense that integration with other parts of the AWS ecosystem would be desirable. In particular, lambdas ship with the aws-sdk readily available, so sending an event to an EventBridge bus seems like it would be a low-effort operation.
Only potential gotchas I could think of off-hand would be permissions, but that could reasonably stated in documentation and left up to the user.
The text was updated successfully, but these errors were encountered:
Feature Request 🛍️
Was curious what it would take to wire up EventBridge support as an alternative to using webhooks for notifications.
Use Case
We leverage remotion in an AWS environment which makes frequent use of EventBridge. We had to spin up a small lambda+apigateway service to handle the webhook completion notifications from remotion. That webhook lambda is a level of abstraction that we'd rather do away with, since all it does is send an event to EventBridge.
Possible Solution
Remotion is lambda-based, and it would make sense that integration with other parts of the AWS ecosystem would be desirable. In particular, lambdas ship with the aws-sdk readily available, so sending an event to an EventBridge bus seems like it would be a low-effort operation.
Only potential gotchas I could think of off-hand would be permissions, but that could reasonably stated in documentation and left up to the user.
The text was updated successfully, but these errors were encountered: