Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for AWS EventBridge Pipes #11735

Open
1 task done
bradwood opened this issue Feb 9, 2023 · 12 comments
Open
1 task done

Support for AWS EventBridge Pipes #11735

bradwood opened this issue Feb 9, 2023 · 12 comments

Comments

@bradwood
Copy link

bradwood commented Feb 9, 2023

Is there an existing issue for this?

  • I have searched existing issues, it hasn't been reported yet

Use case description

AWS recently announced EventBridge Pipes

I would like to be able to add an "Enrichment Lambda" and "Target Lambda" to an AWS EventBridge Pipe using the serverless framework.

Proposed solution (optional)

No response

@medikoo
Copy link
Contributor

medikoo commented Feb 9, 2023

@bradwood, thanks for reporting that. Can you propose how do you envision providing support for this in the Framework. What would be the new properties added to the configuration and hat would be the effect in generated CloudFormation stack?

@bradwood
Copy link
Author

bradwood commented Feb 9, 2023

@medikoo -- I don't have a strong view on it -- my interest in the serverless framework is more as a PO for a team that uses the framework.

@cmygray
Copy link

cmygray commented Feb 20, 2023

@medikoo I wrote an example configuration.

input sls template

resources:
  Resources:
    MyPipe:
      Type: AWS::Pipes::Pipe
      Properties:
        RoleArn: !Ref AllowSendingToTargetRole
        Source: !Ref MyTable
        Target: !Ref MyEventBus

output CF template

{
  "Type" : "AWS::Pipes::Pipe",
  "Properties" : {
    "RoleArn": "arn:aws:iam::000000000000:role/allow-sending-to-target-role",
    "Source": "arn:aws:dynamodb:ap-northeast-2:000000000000:table/my-table",
    "Target": "arn:aws:events:ap-northeast-2:000000000000:event-bus/my-event-bus"
  }
}

This is an example template containing only minimum properties(required).
Maybe someone can improve to use things later:

  • enrichment
  • source params
  • target params

reference:

@medikoo
Copy link
Contributor

medikoo commented Feb 20, 2023

@cmygray it clearly defines what needs to end in CF template. Do you think we need to support any dedicated configuration properties for that? If so what should they be?

@bradwood
Copy link
Author

For me the enrichment use case and binding a lambda to it is of critical importance as this is the lambda:everything_else configuration that is most important to manage inside the serverless framework.

@medikoo
Copy link
Contributor

medikoo commented Feb 21, 2023

Can you propose the Serverless Framework configuration properties that should be added to ensure the best support?

@yuhongliu82
Copy link

Hi @medikoo @cmygray @bradwood,
Could I have any updates on the issue?
I am curious about it.
Thanks

@medikoo
Copy link
Contributor

medikoo commented May 31, 2023

@yuhongliu82 please see my previous comment

@bradwood
Copy link
Author

Note that terraform support is pretty close to being released -- perhaps this can give some suggestions on an implementation approach in serverless?

hashicorp/terraform-provider-aws#28153

@s1mrankaur
Copy link

s1mrankaur commented Jun 5, 2024

+1 It's been over an year now. Are pipes still not supported?

@s1mrankaur
Copy link

Just FYI, There seems to be a plugin available https://github.com/distinction-dev/serverless-pipes, however has some existing issues and limited support for sources/targets. It'd be nice if it's available as part of the framework itself. @medikoo @bradwood

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants