Simple AWS REST Application. You choose the topic. If you have pre-existing application that incorporates business requirements, that will work!

Business Requirements
The business requirements are largely dependent on your topic selection. However, the following requirements must be followed regardless of topic. Be sure the business requirements you generate will lead you to build something useful and complete.
1. Your system must have at least one user interface client application. This can be a web application, a mobile application, or some other type of locally installed or embedded application (NO console-based UI for this app). THIS CAN BE AS SIMPLE AS YOU WOULD LIKE AS LONG AS IT IS SOME TYPE OF UI.
2. Cloud-based data persistence is required. You must use at least TWO forms of cloud based data persistence. While you may use data persistence engines of your choice, at least one should be either a key/value database or file system and the other must be one of the following: SQL-based, Document-based, or Columnar.
3. A cloud-based REST API is required for your client's access.
4. Authentication and role-based authorization having at least TWO distinct roles (i.e. USER and ADMIN, or DIRECTOR and PERFORMER). Note: some functionality may be open to un-authenticated users. That does not count as one of the two roles.
5. Your system must include at least ONE FAAS execution (Lambda) that is triggered by an event other than an API request.
6. You may use FAAS (lambda) as backing logic for your API, or you may use EC2 instances, or another cloud execution platform of your choosing.
7. Your system must include at least ONE message queue (SQS is acceptable) and a valid justification/use case for it's implementation.
8. Your system must send email notifications to users for a specific purpose that makes sense in your project domain.
9. Your system must include at least one instance of a timed task execution (Cron/CloudWatch/EventBridge rule)