When you create Access Keys, you are basically blind how they are used. You can see the effects, like new instances starting or things disappearing, but to see how the key is used you need a separate service. CloudTrail records all calls to the AWS APIs and logs some metadata, such as the caller, the result, and a few others. Using this information you can get an insight into how your keys are used, and whether they have landed in the wrong hands.

A typical SPA deployment consists of two types of assets: dynamic and static. The former, usually the index.html, can change its content upon version change, while the latter, files like 7a5467.js, cannot without renaming. Modern compilers support this use-case with a technique called revving, that renames the file and all references to it to contain the hash of the contents.

When I look at what I do as a developer, most of the things are repeated actions that I don’t automate because “this is the last time I need to do this”. Editing a file, restarting some server, switching to the browser, refreshing and navigating it. Then I make another small change and do the same process again.

I’m sure you know the t3.nano instance type in EC2. It has access to 2 vCPUs, has moderate bandwidth, and is generally an all-purpose virtual machine capable of handling light workloads. You need to pay separately for block storage and network usage, but considering only the CPU it will cost at most $72 a month.