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
To submit a template to the Serverless Patterns Collection, submit an issue with the following information.
IMPORTANT
Patterns are intended to be primarily IaC-focused implementations of 2-4 AWS services, with minimum custom code. They should be commonly used combinations that help developers get started quickly. If you have a utility, demo, or application, submit these to the Serverless Repos Collection instead.
ONLY SUBMIT ONE PATTERN CHANGE PER PR. Multiple patterns or files spanning multiple pattern directories will be automatically rejected.
Patterns may take up to 4-6 weeks to review, test, and merge but there is no SLA and can take significantly longer due to other work the team has.
THIS PROCESS HAS BEEN SIMPLIFIED. All the information below must be provided in the "example-pattern.json" file cloned from the model **
Note the following information for the model:
Description (intro.text) should be a 300-500 word explanation of how the pattern works.
Resources should like to AWS documentation and AWS blogs related to the post (1-5 maximum).
Author bio may include a LinkedIn and/or Twitter reference and a 1-sentence bio.
You must ensure that the sections of the model README.md are completed in full.
DESCRIPTION
This project sets up an integration between Stripe, a popular online payment processing platform, and AWS services to effectively manage and respond to failed payment events. The core of the solution is a CDK (Cloud Development Kit) application that provisions the necessary infrastructure, including an EventBridge event bus, CloudWatch log groups, DynamoDB table and a Lambda function. The CDK application establishes an EventBridge rule that specifically captures payment_failed events from the Stripe Partner Event Source and directs them to the Lambda function. The Lambda function then extracts the relevant details from the Stripe event, such as the payment intent ID, customer email, payment method, and error message, and stores this information in a DynamoDB table for further analysis or processing. This pattern allows the system to proactively identify and respond to failed payment attempts, enabling businesses to take appropriate actions, such as notifying customers, retrying payments, or updating customer records. By leveraging the power of AWS services and the flexibility of the CDK framework, this solution provides a scalable and efficient way to integrate Stripe's payment processing capabilities with a robust event-driven architecture.
To submit a template to the Serverless Patterns Collection, submit an issue with the following information.
IMPORTANT
Patterns are intended to be primarily IaC-focused implementations of 2-4 AWS services, with minimum custom code. They should be commonly used combinations that help developers get started quickly. If you have a utility, demo, or application, submit these to the Serverless Repos Collection instead.
ONLY SUBMIT ONE PATTERN CHANGE PER PR. Multiple patterns or files spanning multiple pattern directories will be automatically rejected.
Patterns may take up to 4-6 weeks to review, test, and merge but there is no SLA and can take significantly longer due to other work the team has.
To learn more about submitting a pattern, read the publishing guidelines page.
Use the model template located at https://github.com/aws-samples/serverless-patterns/tree/main/_pattern-model to set up a README, template and any associated code.
THIS PROCESS HAS BEEN SIMPLIFIED. All the information below must be provided in the "example-pattern.json" file cloned from the model **
Note the following information for the model:
You must ensure that the sections of the model README.md are completed in full.
DESCRIPTION
This project sets up an integration between Stripe, a popular online payment processing platform, and AWS services to effectively manage and respond to failed payment events. The core of the solution is a CDK (Cloud Development Kit) application that provisions the necessary infrastructure, including an EventBridge event bus, CloudWatch log groups, DynamoDB table and a Lambda function. The CDK application establishes an EventBridge rule that specifically captures payment_failed events from the Stripe Partner Event Source and directs them to the Lambda function. The Lambda function then extracts the relevant details from the Stripe event, such as the payment intent ID, customer email, payment method, and error message, and stores this information in a DynamoDB table for further analysis or processing. This pattern allows the system to proactively identify and respond to failed payment attempts, enabling businesses to take appropriate actions, such as notifying customers, retrying payments, or updating customer records. By leveraging the power of AWS services and the flexibility of the CDK framework, this solution provides a scalable and efficient way to integrate Stripe's payment processing capabilities with a robust event-driven architecture.
Resources
Author bio
Name: Mohamed Mohamud
Photo URL: https://media.licdn.com/dms/image/C5603AQF0k1SsVlO5GQ/profile-displayphoto-shrink_400_400/0/1634687266785?e=1721260800&v=beta&t=W5HaXkh4Yzf3MjbYfNd29s8qR-pvDtKaDR0e3tGa-r8
Linkedin: https://www.linkedin.com/in/mohamed-mohamud-80370a149/
Description: Partner Solutions Architect @ AWS. Data Analytics with a focus in Streaming Analytics.
GitHub PR for template:
#2297
The text was updated successfully, but these errors were encountered: