abhiek187 / aws-shop Goto Github PK

Create a workflow to lint, detect drift, and do a dry run of a CloudFormation template.

Enable logging: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cloudfront-distribution-distributionconfig.html#cfn-cloudfront-distribution-distributionconfig-logging

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-dynamodb-table.html#cfn-dynamodb-table-deletionprotectionenabled

Enable for Lambda: https://docs.aws.amazon.com/lambda/latest/dg/services-xray.html

#23 should be completed first; choose a serverless lens

Can try an internet monitor for CloudFront: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-internetmonitor-monitor.html

Or a synthetics canary to track API Gateway requests: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-synthetics-canary.html

Will probably add once more routes are added. For now, redirecting to the main page should suffice.

See https://docs.aws.amazon.com/awssupport/latest/user/cloudwatch-ta.html

Refer to https://aws.amazon.com/architecture/icons/

I just learned that CRA is not recommended (not officially deprecated, but hasn't been touched since Sept 2022) and we should use Vite instead to generate an SPA. I haven't touched the CRA app at all, so it's not a problem to toss it out and replace it with Vite.

Next.js is another option if we want to utilize SSR, but that would require some extra configuration to get it working with our serverless architecture (though a guide is available). I want to stick with the building blocks and separate the client and server so I can continue exploring AWS.

Do the simple thing first. By starting with a primitive setup, you will understand and appreciate the problems modern frameworks are trying to solve.