New serverless pattern - eventbridge-scheduler-ses-abandoned-cart-notification

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.

1. 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.

2. 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.
  This pattern demonstrates how to use Amazon EventBridge Scheduler to drive per-customer abandoned cart email notifications on an hourly cadence. A Lambda function, invoked by the scheduler, queries a DynamoDB GSI for customers with abandoned carts that have not yet been notified, sends each a personalised HTML email via Amazon SES, and marks the record as notified to prevent duplicate emails. The pattern includes idempotent notification logic, seed test data, a dead-letter queue for failed scheduler invocations, and least-privilege IAM policies scoped to the specific SES identity and DynamoDB table.

• Resources should like to AWS documentation and AWS blogs related to the post (1-5 maximum).
  https://docs.aws.amazon.com/ses/latest/dg/creating-identities.html
  https://docs.aws.amazon.com/ses/latest/dg/request-production-access.html

• Author bio may include a LinkedIn and/or Twitter reference and a 1-sentence bio.
  Name: Rajil Paloth
  Bio: ProServe Delivery Consultant at AWS
  LinkedIN: https://www.linkedin.com/in/paloth/

You must ensure that the sections of the model README.md are completed in full.

GitHub PR for template:

https://github.com/aws-samples/serverless-patterns/pull/2998

Inizia con i file _pattern-model e PUBLISHING.md, quindi esamina le sezioni di example-pattern.json e README richieste per la sottomissione. Confronta il pattern proposto con EventBridge Scheduler, Lambda, DynamoDB, SES e una dead-letter-queue con PR #2998; il lavoro è completo quando il README del modello e i metadati del pattern sono completi e il template viene inviato come un’unica modifica al pattern.