Task 6. SQS & SNS, Async Microservices Communication

[Guria]

Task 6 assignment

Note for reviewers

• I use this issue instead of PR to collect everything about this task and all referenced PR are merged already.
• I use single monorepo with both BE and FE for a good reason: FE build uses outputs of BE stacks. Organizers have confirmed that it is acceptable.
• Check Task 2. Serve SPA in AWS S3 and Cloudfront Services #3, Task 3. First API with AWS API Gateway and AWS Lambda #18, Task 4. Integration with DynamoDB #22, Task 5. Integration with S3 #27 and commit history if you want to learn more about setup and reasoning. Issues, PRs and each commit messages contain lot of details.
• Please provide your evaluation in comments and fill in the form.

Task 6 Artifacts

Task 6.1 (Pull Request #29)

✔️ Create a lambda function called catalogBatchProcess which will be triggered by an SQS event.
✔️ Create an SQS queue called catalogItemsQueue, in the resources section.
✔️ Configure the SQS to trigger lambda catalogBatchProcess with 5 messages at once via batchSize property.
✔️ The lambda function should iterate over all SQS messages and create corresponding products in the products table.

Task 6.2 (Pull Request #31)

✔️ Update the importFileParser lambda function to send each CSV record into SQS.
✔️ It is no longer log entries to CloudWatch.

Middify for non http handlers now use appropriate middlewares to log inputs, outputs and errors.

Task 6.3 (Pull Request #26)

✔️ Create an SNS topic and email subscriptions.
✔️ Update the catalogBatchProcess lambda function to send an event to the SNS topic once it creates products.
➕ catalogBatchProcess lambda is covered by unit tests
➕ There are 2 email subscriptions with different filtering rules

Links to deployment

Deployments links removed since its outdated and there are newer tasks implemented.

Email SNS notifications screenshot: