New serverless pattern - Stripe-EventBridge-Lambda #2297
Conversation
|
This would be useful to be submitted under the repo as an example. Please submit this to the repos directory at serverlessland.com/repos. |
| ``` | ||
| 3. From the command line, use AWS CDK to deploy the AWS resources for the pattern as specified in the app.py file. A command-line argument is needed to deploy the CDK stack, "stripeEventBusName". This argument should be the name of the **SaaS event bus** associated with your Stripe [partner event source](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-saas.html). | ||
| ``` | ||
| cdk deploy --parameters stripeEventBusName=SAAS_EVENT_BUS_NAME_HERE |
There was a problem hiding this comment.
is this missing any instructions? I am getting the below error
/serverless-patterns/stripe-eventbridge-lambda/app.py", line 3, in
import aws_cdk as cdk
ModuleNotFoundError: No module named 'aws_cdk'
There was a problem hiding this comment.
I don't believe so, I do not see that error
pputhran
requested review from
pputhran and
parikhudit
and removed request for
pputhran
| @@ -0,0 +1,61 @@ | |||
| { | |||
| "title": "Stripe EvenBridge SaaS Integration to AWS Lambda", | |||
There was a problem hiding this comment.
| "title": "Stripe EvenBridge SaaS Integration to AWS Lambda", | |
| "title": "Amazon EventBridge Stripe SaaS Integration to AWS Lambda", |
| @@ -0,0 +1,61 @@ | |||
| { | |||
| "title": "Stripe EvenBridge SaaS Integration to AWS Lambda", | |||
| "description": "Stripe Failed Payment Event Monitoring and Archiving Solution using AWS EventBridge and CDK", | |||
There was a problem hiding this comment.
Why is it specific to failed payments? Can this pattern be extended to cover additional use-cases?
| aws lambda invoke --function-name <StripeIntegrationStack-StripeProcessFailedPaymentL-nIPhn7sPQx9e> --payload file://event.json response.json | ||
| ``` |
There was a problem hiding this comment.
I think you need to add --cli-binary-format raw-in-base64-out because the input is expected to be in base64
| { | ||
| "StatusCode": 200, | ||
| "ExecutedVersion": "$LATEST" | ||
| } |
There was a problem hiding this comment.
I get an error message instead (account id redacted):
{"statusCode": 500, "body": "An error occurred (AccessDeniedException) when calling the PutItem operation: User: arn:aws:sts::123456789012:assumed-role/StripeIntegrationStack-stripecdklambdarole246618B3-lLn1HaA8rFMz/StripeIntegrationStack-StripeProcessFailedPaymentL-BwLehI3Ed8BA is not authorized to perform: dynamodb:PutItem on resource: arn:aws:dynamodb:eu-west-1:123456789012:table/StripeIntegrationStack-StripeFailedPaymentsTableC8BBF5D3-SSP3IAPIWRPJ because no identity-based policy allows the dynamodb:PutItem action"}%
|
|
||
| 2. From the Event bus list, choose the SaaS event bus associated with your Stripe partner event source. | ||
|
|
||
| 3. From the Rules list, select the "StripeIntegrationStack-StripeFailedPaymentEventsRul-cSTSp1wtPkkB" |
There was a problem hiding this comment.
The suffix is randomly generated and will not match the users resources. It's probably better to word this differently
|
Hi, do you still plan to address the requested changes? |
|
Closing due to inactivity |
Issue #, if available:
Description of changes:
This pattern demonstrates how to use the Stripe Amazon EventBridge SaaS integration and AWS Lambda to process events from Stripe.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.