1) The first 2 links in the readme are 404s

2) I feel like the very first question this project needs to answer is: "Why should i use this over the official AWS CDK?" (assuming you want other people to use this). Besides maybe some nicer syntax I don't really see a reason to use this and lose all the (sometimes lacking) documentation, examples + community support that exists for CDK.

2.1) The listed benefits include "Use your favorite [...] type checker", but the example uses strings for specifying field types (vs. AWS CDK which would use enums, and is also "pure python") which immediately throws that out of the window

▲

michal-stlv 7 hours ago | parent [-]

Thanks for having a look.

1. Links are fixed now.

2. We try to answer that hopefully better at our website https://stelvio.dev but you're right we should do it better in readme too! - Can you please be more specific regarding syntax? What you don't like or what you'd like to see? We try to have - Whole point of Stelvio is that you need to write much less code to define your infra, e.g. almost none IAM code due to our linking system. We also have "dev mode" which let's you to test/debug your lambdas locally without re-deployment - We try to have comprehensive documentation and guide covering each component. If you see something missing please can you be more specific? - Regarding community support we can't do much here other than grow community which we're trying to do. Having said that we're happy to support our users personally and answer any question or help you onboard. Just shoot email to team@stelvio.dev

2.1 many parameters/fields/properties in Stelvio have option to use either enum or string. If it's string with specific supported values it's defined as e.g. ` Literal["keys-only", "new-image", "old-image", "new-and-old-images"]` so you'll get help of IDE for auto complete as well as type-checker/linter if you use wrong value.

Thank you again for your valuable feedback. Happy to talk anytime. If you want to try Stelvio just shoot us an email and we'll help you along the way.

▲

raw_anon_1111 7 hours ago | parent | next [-]

We also have "dev mode" which let's you to test/debug your lambdas locally without re-deployment

As does both SAM and the CDK.

https://docs.aws.amazon.com/cdk/v2/guide/testing-locally-get...

But this is 2026. You should be deploying Docker containers to Lambda and those are really easy to test locally

▲

SamuelAdams an hour ago | parent [-]

Docker has a large cold start time usually, sometimes it can take up to 10 seconds for a dockerized Python lambda to invoke. Are there solutions for that, that include docker?

	▲	raw_anon_1111 an hour ago \| parent [-]
		Fair point, I’m working on a project now that doesn’t require responsiveness - it’s not user facing. We were burned so bad by Lambda cold starts for user facing lambdas that were backing websites we said forget it and just used ECS/fargate. This is my go to template - I didn’t write it. I found it 7 years ago. https://github.com/1Strategy/fargate-cloudformation-example/... You just update the parameter for your container image and redeploy. Of course you have provisioned concurrency that can help. But the easiest way to test Python lambdas locally is just to run it like any other Python script and call your event handler with the event you want to test

▲

yunwal 6 hours ago | parent | prev [-]

The manifesto link in the README still points to https://stelvio.dev/manifesto/, which should be about/manifesto/

▲

michal-stlv 6 hours ago | parent [-]

thanks for taking time to let us know. not sure what's going on I checked on multiple devices and it links correctly.

▲

yunwal 6 hours ago | parent [-]

Are you sure you checked both links? There's one at the top of the README that's linked correctly for me and one towards the bottom that is not

	▲	michal-stlv 5 hours ago \| parent [-]
		You're right, second link was broken. Fixed now. Thank you so much for taking time to check this again. If you need any help with stelvio have any more feedback to share please hit us at team@stelvio.dev Thank you again!