Bjorn Stange

First we should choose an execution environment, the candidates are: * Github Actions (leaning towards this, as I've had nothing but good experiences with it) * AWS Lambda (the existing...

Add all AWS Resources * SQS * Lambdas * producer * consumer

Self explanatory. Will have to update schema, store md5 in the db, compare etag value to md5, skip file if they are the same, process file if the md5 is...

Code is hacky, needs to be broken into more functions. Also, there are many pylint issues.

Tested a working POC and it seemed to work wonderfully. I've committed to migrating to cockroach as my primary database.

The resolve function for IngestionServiceSnowball is not mapping back to existing table/field names. This is because of the temporary fix implemented to get EC2 pricing back up.

Instead, dockerfile should grab the raw script from the other github repo that has the latest import script. Github repo found here: https://github.com/Bjorn248/aws_pricing_data_ingestor/

See https://docs.docker.com/compose/networking/#specify-custom-networks Wouldn't want to use things that are on the chopping block of deprecation