Ras al jil feature eventbridge scheduler ses abandoned cart notification

[ras-al-jil]

Issue #2999, if available:

Description of changes:
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.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[marcojahn]

Hello @ras-al-jil, thank you for your contribution. I've added a few comments, pls review.

[marcojahn]

The README does not include a dedicated section for verifying that the deployment succeeded and resources were created correctly. While the Testing section covers functional testing, there is no guidance on confirming the Terraform deployment outputs, verifying the EventBridge schedule is active, or checking that the DynamoDB table was seeded correctly.

As an example:

  ## Verify Deployment

  After `terraform apply` completes, verify the resources were created:

  1. Confirm the EventBridge schedule is active:
     ```bash
     aws scheduler get-schedule --name $(terraform output -raw schedule_name)
     ```

  2. Confirm the DynamoDB table has seed data:
     ```bash
     aws dynamodb scan --table-name $(terraform output -raw dynamodb_table_name) --select COUNT
     ```
     Expected: `Count: 3`

[ras-al-jil]

Hi @marcojahn, thank you for reviewing!
I have made the suggested changes. Do let me know if this is okay