Replace Chef with ECS Deployment

[FinnIckler]

After testing the docker-compose landscape, we have decided it makes more sense to go straight to ECS, as updating the images by ourselves is much more of a hassle
TODO:

• Create the correct infra files for our ECS setup
• test on staging
• make a PR to this rep which builds images and triggers a deploy
• Create New Load Balancer and reference it for the services
• Create a mixed instance fleet to better support prod on a bigger instance

[FinnIckler]

So a staging server does come up successfully with Sidekiq and PMA. There is still one issue with a webpacker dependency when building assets though:
Error [ERR_REQUIRE_ESM]: require() of ES Module /app/node_modules/find-cache-dir/node_modules/pkg-dir/index.js from /app/node_modules/find-cache-dir/index.js not supported.
That sounds like a dependency update gone wrong.
I will take some time tomorrow evening to investigate so we can get everything done by friday.

[FinnIckler]

Successfully deployed a staging container now. Because we compile assets on the container (due to many blockers) we have quite a bad startup time and I had to increase grace periods on both the load balancer and the ECS Container side. This will make scaling a bit more annoying, but should be manageable because we are planning to make our own scaling metrics anyway

[FinnIckler]

Here is an explanation of my proposed way of building and deploying images that I implemented in this (and #8338) PR:
thewca/web-dev-docs#9
might be easier to review with that information. I can also write up some more technical diagrams showing each container and services if needed.

[gregorbg]

Any reason why you paste the bucket into a variable before accessing it?
All use-cases in your most recent commit can be boiled down to regulations_bucket.object(...) directly

[FinnIckler]

I did it because using @@s3 means we don't need to instantiate the bucket every time. I think I have a neater solution though

[gregorbg]

I did it because using @@s3 means we don't need to instantiate the bucket every time. I think I have a neater solution though

Sorry to say but your most recent commit changes absolutely nothing. Passing the parameter as a default argument simply means Rails will call it for you every time that a parameter hasn't been supplied otherwise.

[gregorbg]

Ah, now things are getting more interesting 😎