This mirrors my experience. Infrastructure as code is hard. I’ve tried to rely on VSCode extensions for some help getting configuration values, but at the time

This mirrors my experience. Infrastructure as code is hard. I’ve tried to rely on VSCode extensions for some help getting configuration values, but at the time the best that was available was some snippets. I want the editing experience to have less memorization and alt-tabbing to docs, and more expression and validation. Fargate isn’t less config than a helm chart, but you’re on your own, in that there isn’t much of a public config ecosystem that I’m aware of. I also wrote it off due to 2.3-3X instance pricing vs EC2. One of the biggest factors that intimidates developers in my experience is needing to determine resources. It would seem that such a task could be done with automatic testing, but I haven’t found or developed a technique to do so. In theory I would have my script test different RAM/CPU values against a load tester, have live cost data and compute an optimum. I suppose one can come from the opposite angle and determine the program’s needs based on data structures and libraries. That is beyond my skills. I suppose network interface throughput would be another factor, but unfortunately with Fargate and Lambda that is largely opaque ( and I believe linked to CPU allocation ). This just goes to say that in addition to managing the complexity of configuration code, the underlying abstractions are harder to grok than a VM or even Kubernetes nodes and resource allocations.