cdk-valheim VS CDK-SPA-Deploy

The best part of CDK is that it enables the creation high-level, reusable constructs that can be published to software registries like npm and PyPI. Developers can import and use these constructs in their own CDK code. A quick google search for "cdk valheim" turned up a few results. cdk-valheim seems like the best option for what I was looking for. This project uses ECS, a container orchestration tool from AWS that I have experience using with web applications and EFS for persistent file storage. Although it is written in Typescript, I can still use the construct in my preferred programming language (Python) without any extra effort or configuration. This is thanks to the jsii. From https://github.com/aws/jsii:

That's correct, I am using Fargate to run the container, but I am using it by way of another CDK construct that I have imported in my CDK code: https://github.com/gotodeploy/cdk-valheim. CDK allows you to import reusable applications, so you don't have to write everything from scratch. I was going to try to write something similar, but this construct has everything I need and is tested. Even though it is written in Typescript, I can import it from PyPI were it is also published (thanks to jsii)

This is the cdk-valheim construct that I use in this project.

One way to do this is implement an S3 deployer with a nice interface like CDK-SPA-Deploy and then add an npm script like npm run build && cdk deploy, but doing that wouldn't achieve my dream of an integrated UI build to match my Lambda function build. To do that, we'll need to dig into a couple of modules.