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
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.
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?
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.
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
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!
I’ve used SST, Pulumi, CDK, and Terraform. I decided to stick with SST because it offers a far superior development experience. Sure, I could write IAM policies with plain CDK, but it’s more error-prone and harder to maintain. Features like linking and live lambdas just make development so much easier.
I actually think this project makes a lot of sense. It lets you get started in minutes without dealing with unnecessary details. Furthermore, you can always access the low-level Pulumi component and override whatever you need. Keep doing what you’re doing! Your project makes IaC more accessible to everyone, and that’s a good thing. I’ll be happy to try it.
We have a handful of legacy SST Lambdas at work. We literally just use it to build a ZIP which we publish to an S3 Bucket, not much different than publishing an ECR image. It’s all Terraform from there.
Curious why you’d go from sst (back?) to terraform? Are there services or features missing in sst or is it about terraforms ergonomics that fits your case better?
Terraform in combination with Claude Code is actually quiet managable. Yes it generates much code, but you have great detail of what is actually going on, there is no hidden abstraction layers on top.
Just came across SST the other day and it looks very interesting. It looks like it's based on Pulumi, so it begs the question for me of why does it exist? Structurally it doesn't seem to be that different in capabilities. Perhaps it is more that it is a more opinionated subset that has better ergonomics. Is that correct, or is the reason different for you?
Interesting product! Not sure if I'm getting this right, docs seem pretty sparse so please forgive me. Here are a couple questions:
1. Do you support tagging resources?
2. You mention provisioning Pulumi resources, are you "simply" a wrapper around Pulumi? If so, are you relying on Pulumi for state management or does Stelvio have it's own state manager?
3. Do you support cloudfront? Imo this is a vital service for building even small production apps, esp if you are serving static assets out of S3.
4. I saw references to API Gateway v1, do you also support v2?
5. One of the cool features is that you're able to handle all the IAM stuff, but can that also be easily modified? Like, if I want to create a new lambda that interacts with an existing dynamodb table, how would I describe that with Stelvio?
Sorry for the pile of questions lol but you got my attention :) You have a lot of competition in this space and I'm curious to see how your project will evolve. Best of luck!
2. Essentially yes, Stelvio is wrapper around Pulumi, using it mainly for state management and as an escape hatch in cases you might need something not supported.
3. Yes we do, there's `CloudFrontDistribution` component but it's not documented as idiomatic way is to use `Router` [1] & `S3StatitWebsite`[1] components and `custom_domains` [3].
4. Currently only v1. v2 (http) and websockets on the roadmap
5. Yes when you link resources we provide default permissions but these can be fully modified https://stelvio.dev/concepts/linking/#customizing-links
If you want to link existing dynamo table that is NOT created with stelvio and link it to lambda that's currently not supported, meaning you'll not get automated permissions. Although it would be possible so we might support this use case if there's interest.
Thank you for good questions. If you have any more questions/feedback or need help hit us email at team@stelvio.dev Happy to talk.
Even if he does, how kind will it take him to add new functionality? For instance AWS both announced durable lambda functions and CFT support the same day
I just checked, pulumi does have a good track record of keeping up with AWS. But using a non industry standard framework (Stevio) just doesn’t make any sense from a long term portable career perspective.
While I’m not a fanatic about which one I use out of the major ones. My last three projects were CDK/Typescript, Terraform and CloudFormation with my own collection of utility scripts I’ve used over 5 years to make it act more like TF. But the CFTs are standard.
Why would I ever use this instead of just using the CDK with Python? There is plenty of documentation and my experience is I can one shot my entire IAC with a well defined spec with ChatGPT to generate CDK code.
Yes I know AWS well enough to know whether it is correct
Seems great for really small apps where you want your resource definitions colocated with the code using them. I'd imagine the benefits start to break down as your infrastructure gets more complicated.
The bigger answer is that if you're proficient and happy with CDK or anything else to wire resource up, you're probably not going to see much (if any) benefit.
True, I have written my share of CloudFormation custom resources.
Funny anecdote: it was faster for an SA when i was at AWS to create a Terraform module and have it merged into Terraform than it was for us to wait for AWS to add support for the same resource in CloudFormation. They are getting much better now
Also where is this idea that it takes days to ship Python in CDK coming from?
Edit: great, getting downvoted for daring to ask the author to explain a claim. I’m noticing other people asking questions getting downvoted, too. Brigading isn’t a good look.
Stelvio's main selling point here is that you can use our higher-level components for different services and have them automatically configured.
So, you don't have to configure IAM roles, or Env vars manually, as this is handled for you through a concept called linking. https://stelvio.dev/concepts/linking/
In our experience, that alone adds a lot of productivity gains for teams.
Higher level CDK constructs do the same thing. But honestly, IAC is one of the easiest thing for LLMs to do and there is plenty of documentation to troubleshoot. There is no reason to introduce this into a company instead of using the official CDK.
But coincidentally Stelvio was born out of frustration with CDK which I'm using at my day job for 4 years at this point:
- slow deployment: CDK is layer on top of cloud formation, it first translates to CF which is then moved to AWS and resolved/deployed there. Process is quite slow and if something goes wrong it's hard to debug, rollbacks take ages, sometimes they block due to inter-stack dependencies
- CDK is still quite low level and focused on infra. You just can't create say api gateway with 3 routes each using 3 different lambdas with permission to use dynamo table in 4 lines - you an with stelvio
- whatever code change you need to test you need to deploy it first which is probably slowest with CDK(compared e.g. to pulumi) then even if you run it you can't really debug it or just see prints, you need to just go thru cloudwath or other services - stelvio allows you to run lambdas in "dev mode" so you don't need to redeploy and run your lambdas locally for instant feedback and even debugging support
Having said that CDK is good tool and I'm happy that it exists as I like it much better than CF itself or Terraform. Stelvio just tries to be even better and focused on developers.
Regarding LLMs sure, problem with LLMs is not they can't generate the code but if you're willing to read and understand all of it. Stelvio is less code with higher abstractions so it's easier to comprehend.
And what assurances are there that you will be around for five years? Or that you will support new services features when they come out?
And I always “disable rollbacks” this has been a feature in CloudFormation, CDK and SAM for years.
Running lambdas locally with SAM has been a feature for at least 5 or six years as with the CDK. But these days you really should be packaging lambdas as Docker containers - those are really easy to test locally without any special infrastructure
We still believe to have a more flexible solution that also adds some features, including combining multiple cloud providers which at the moment we use to enable cloudflare DNS in front of AWS infra. Feel free to give it a try!
Just to make it explicit, I (author) did not downvoted you.
Both me and sebst (co-author) tried to answer everybody and did so politely.
We respect other opinions and Stelvio (as any other thing) might and is not for everybody.
Regarding your question. Well, it depends on the size of the project. Small enough you can do anything fast. I'm working on bigger mostly serverless system on AWS and it did take lot of time to to setup everything with CDK, certainly days.
I believe it would be faster with stelvio as it offers higher level abstractions than CDK - Stelvio was born out of my frustraction with CDK, I was doing lot of things again and again, waiting long for deployments etc.
If someone is happy with CDK, then they should use CDK, it's good too, even for me much better than CF or Terraform.
But if you feel things could be even less cumbersome, with less code and faster, maybe you could give Stelvio a try.
We're not claiming we'll do everything for everybody, we have our opinions and Stelvio is opinionated - shamefully focusing on (app) developers rather than on infrastracture focused people. https://stelvio.dev/blog/why-i-am-building-stelvio/
Thank you for your comment and wish you a good day.
Thanks for the response. So Stelvo’s sell is through its opinionated approach regarding architecture and defaults. I realize elevator pitches are tough especially when there are lots of competing solutions, but maybe some sort of short and sweet “us vs them” comparison on the home page would make that sell easier. Like many of my peers I’m sure, I’ll admit I have little time and patience to click through to get to the obligatory question of “why us”.
Anyways, not sure who went on the downvote spree or why (it wasn’t one account), and I admit it didn’t seem likely your team would be doing it since you folks were actively discussing, but I couldn’t think of why someone else would do it either. Anyways, sorry and thanks for your time.
I don't understand why I would use this over aws CDK in python.
cdk is already an abstraction over the javascript cdk,
which is an abstraction over cloudformation,
which is an abstraction over the api..
I just want to navigate some of the claims made by Stelvio and others in this thread and see if maybe I'm missing something after reading the docs:
- Ship Python to AWS in minutes, not days: I can already do this with cdk? It's highly dependent on the project requirements. AWS already provides a sleuth of high level constructs with sensible defaults.
- great for really small apps where you want your resource definitions colocated with the code using them: CDK is just code? You can put it all in one place or split it into files. I don't get how this is new.
- easier to manage IAM permissions this is the bread and butter of cdk. I can simply do Resource.grantRead(lambdaFunction) without touching IAM. Who was complaining about this?
The only advantage I see here over CDK is using Pulumi as the underlying resource engine, which I admit performs better on deployment speed. But then we arrive to the question: Why not just use Pulumi, which already gives me IaC in python?
Our goal with Stelvio is bringing these two together: Using Pulumi (for performance and multi-cloud capatbilities) with the convenience of some parts of CDK.
It's unlikely to cover the AWS API's with 100% certainty, and I don't want to spend time trying to work out the kinks, so honestly, I'd rather just use the AWS CDK and CloudFormation.
It's not unlikely, I guarantee it will never happen. Because that's not the point.
Point is to cover most of the common cases (with escape hatch for fine-tuning in special case) and make those super easy and short to do so devs can focus on code and not infrastructure.
It's standard higher level abstraction play of doing more with less (code and time spent).
Co-Author here. As long as you have trust in the underlying API of the Pulumi resources that Stelvio creates on your behalf, we have a mechanism in place that let's you fine-tune every parameter if you like. See: https://stelvio.dev/concepts/customization/
Otherwise, you can stick with Stelvio's sensible defaults if you wish.
We believe that we're creating a solution for problems that we fought with during a combined 40 years of experience in the team. ymmv, but you are invited to give it a try. Happy to show you a demo ;)
Yet I have never had those problems in 8 years of working with AWS including almost 4 working at AWS ProServe (no longer there). I would never depend on a third party IAC package aside from Terraform knowing the surface area of AWS services and nit knowing if this is still going to be supported a decade from now.
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
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.
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
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?
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
The manifesto link in the README still points to https://stelvio.dev/manifesto/, which should be about/manifesto/
thanks for taking time to let us know. not sure what's going on I checked on multiple devices and it links correctly.
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
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!
How does this compare to https://encore.dev/ or other infrastructure-inside-application-code solutions?
Conceptually similar, maybe other opinions baked in.
encore focusses on TypeScript and Python. Stelvio is a solution for Python.
I’ve used SST, Pulumi, CDK, and Terraform. I decided to stick with SST because it offers a far superior development experience. Sure, I could write IAM policies with plain CDK, but it’s more error-prone and harder to maintain. Features like linking and live lambdas just make development so much easier.
I actually think this project makes a lot of sense. It lets you get started in minutes without dealing with unnecessary details. Furthermore, you can always access the low-level Pulumi component and override whatever you need. Keep doing what you’re doing! Your project makes IaC more accessible to everyone, and that’s a good thing. I’ll be happy to try it.
This made my day. Would love to hear how it goes if you try it - team@stelvio.dev or just open an issue.
Thanks for the encouragement!
We have a handful of legacy SST Lambdas at work. We literally just use it to build a ZIP which we publish to an S3 Bucket, not much different than publishing an ECR image. It’s all Terraform from there.
Curious why you’d go from sst (back?) to terraform? Are there services or features missing in sst or is it about terraforms ergonomics that fits your case better?
Terraform in combination with Claude Code is actually quiet managable. Yes it generates much code, but you have great detail of what is actually going on, there is no hidden abstraction layers on top.
Appreciate it! Let me know if you’d like to chat about your experience at some point in time!
Just came across SST the other day and it looks very interesting. It looks like it's based on Pulumi, so it begs the question for me of why does it exist? Structurally it doesn't seem to be that different in capabilities. Perhaps it is more that it is a more opinionated subset that has better ergonomics. Is that correct, or is the reason different for you?
Interesting product! Not sure if I'm getting this right, docs seem pretty sparse so please forgive me. Here are a couple questions:
1. Do you support tagging resources?
2. You mention provisioning Pulumi resources, are you "simply" a wrapper around Pulumi? If so, are you relying on Pulumi for state management or does Stelvio have it's own state manager?
3. Do you support cloudfront? Imo this is a vital service for building even small production apps, esp if you are serving static assets out of S3.
4. I saw references to API Gateway v1, do you also support v2?
5. One of the cool features is that you're able to handle all the IAM stuff, but can that also be easily modified? Like, if I want to create a new lambda that interacts with an existing dynamodb table, how would I describe that with Stelvio?
Sorry for the pile of questions lol but you got my attention :) You have a lot of competition in this space and I'm curious to see how your project will evolve. Best of luck!
Thank you for valuable feedback.
1. Not yet but coming soon.
2. Essentially yes, Stelvio is wrapper around Pulumi, using it mainly for state management and as an escape hatch in cases you might need something not supported.
3. Yes we do, there's `CloudFrontDistribution` component but it's not documented as idiomatic way is to use `Router` [1] & `S3StatitWebsite`[1] components and `custom_domains` [3].
4. Currently only v1. v2 (http) and websockets on the roadmap
5. Yes when you link resources we provide default permissions but these can be fully modified https://stelvio.dev/concepts/linking/#customizing-links If you want to link existing dynamo table that is NOT created with stelvio and link it to lambda that's currently not supported, meaning you'll not get automated permissions. Although it would be possible so we might support this use case if there's interest.
Thank you for good questions. If you have any more questions/feedback or need help hit us email at team@stelvio.dev Happy to talk.
[1] https://stelvio.dev/components/aws/cloudfront-router/ [2] https://stelvio.dev/components/aws/s3/#static-websites [3] https://stelvio.dev/components/aws/api-gateway/?h=custom#cus...
Even if he does, how kind will it take him to add new functionality? For instance AWS both announced durable lambda functions and CFT support the same day
You could always use the plain vanilla resources that pulumi provides if there is no stelvio provided component for that.
I just checked, pulumi does have a good track record of keeping up with AWS. But using a non industry standard framework (Stevio) just doesn’t make any sense from a long term portable career perspective.
While I’m not a fanatic about which one I use out of the major ones. My last three projects were CDK/Typescript, Terraform and CloudFormation with my own collection of utility scripts I’ve used over 5 years to make it act more like TF. But the CFTs are standard.
Why would I ever use this instead of just using the CDK with Python? There is plenty of documentation and my experience is I can one shot my entire IAC with a well defined spec with ChatGPT to generate CDK code.
Yes I know AWS well enough to know whether it is correct
Seems great for really small apps where you want your resource definitions colocated with the code using them. I'd imagine the benefits start to break down as your infrastructure gets more complicated.
The bigger answer is that if you're proficient and happy with CDK or anything else to wire resource up, you're probably not going to see much (if any) benefit.
Until there is a resource you need out of the 150+ AWS services that they don’t support or a new feature of an existing resource….
To be fair, AWS service teams don't always expose all features/options through cloudformation and you end up having to hit the API to manage them.
True, I have written my share of CloudFormation custom resources.
Funny anecdote: it was faster for an SA when i was at AWS to create a Terraform module and have it merged into Terraform than it was for us to wait for AWS to add support for the same resource in CloudFormation. They are getting much better now
Also where is this idea that it takes days to ship Python in CDK coming from?
Edit: great, getting downvoted for daring to ask the author to explain a claim. I’m noticing other people asking questions getting downvoted, too. Brigading isn’t a good look.
Stelvio's main selling point here is that you can use our higher-level components for different services and have them automatically configured.
So, you don't have to configure IAM roles, or Env vars manually, as this is handled for you through a concept called linking. https://stelvio.dev/concepts/linking/
In our experience, that alone adds a lot of productivity gains for teams.
Why not use CDK L3 constructs (patterns) or the corresponding for Pulumi, since that's what you generate?
Higher level CDK constructs do the same thing. But honestly, IAC is one of the easiest thing for LLMs to do and there is plenty of documentation to troubleshoot. There is no reason to introduce this into a company instead of using the official CDK.
I respect your point of view.
But coincidentally Stelvio was born out of frustration with CDK which I'm using at my day job for 4 years at this point:
- slow deployment: CDK is layer on top of cloud formation, it first translates to CF which is then moved to AWS and resolved/deployed there. Process is quite slow and if something goes wrong it's hard to debug, rollbacks take ages, sometimes they block due to inter-stack dependencies - CDK is still quite low level and focused on infra. You just can't create say api gateway with 3 routes each using 3 different lambdas with permission to use dynamo table in 4 lines - you an with stelvio - whatever code change you need to test you need to deploy it first which is probably slowest with CDK(compared e.g. to pulumi) then even if you run it you can't really debug it or just see prints, you need to just go thru cloudwath or other services - stelvio allows you to run lambdas in "dev mode" so you don't need to redeploy and run your lambdas locally for instant feedback and even debugging support
Having said that CDK is good tool and I'm happy that it exists as I like it much better than CF itself or Terraform. Stelvio just tries to be even better and focused on developers.
Regarding LLMs sure, problem with LLMs is not they can't generate the code but if you're willing to read and understand all of it. Stelvio is less code with higher abstractions so it's easier to comprehend.
And what assurances are there that you will be around for five years? Or that you will support new services features when they come out?
And I always “disable rollbacks” this has been a feature in CloudFormation, CDK and SAM for years.
Running lambdas locally with SAM has been a feature for at least 5 or six years as with the CDK. But these days you really should be packaging lambdas as Docker containers - those are really easy to test locally without any special infrastructure
True, and there's nothing wrong with them.
We still believe to have a more flexible solution that also adds some features, including combining multiple cloud providers which at the moment we use to enable cloudflare DNS in front of AWS infra. Feel free to give it a try!
In that case just use Terraform with an entire community to support it across all types of infra.
Just to make it explicit, I (author) did not downvoted you.
Both me and sebst (co-author) tried to answer everybody and did so politely.
We respect other opinions and Stelvio (as any other thing) might and is not for everybody.
Regarding your question. Well, it depends on the size of the project. Small enough you can do anything fast. I'm working on bigger mostly serverless system on AWS and it did take lot of time to to setup everything with CDK, certainly days.
I believe it would be faster with stelvio as it offers higher level abstractions than CDK - Stelvio was born out of my frustraction with CDK, I was doing lot of things again and again, waiting long for deployments etc.
If someone is happy with CDK, then they should use CDK, it's good too, even for me much better than CF or Terraform.
But if you feel things could be even less cumbersome, with less code and faster, maybe you could give Stelvio a try.
We're not claiming we'll do everything for everybody, we have our opinions and Stelvio is opinionated - shamefully focusing on (app) developers rather than on infrastracture focused people. https://stelvio.dev/blog/why-i-am-building-stelvio/
Thank you for your comment and wish you a good day.
Michal
Thanks for the response. So Stelvo’s sell is through its opinionated approach regarding architecture and defaults. I realize elevator pitches are tough especially when there are lots of competing solutions, but maybe some sort of short and sweet “us vs them” comparison on the home page would make that sell easier. Like many of my peers I’m sure, I’ll admit I have little time and patience to click through to get to the obligatory question of “why us”.
Anyways, not sure who went on the downvote spree or why (it wasn’t one account), and I admit it didn’t seem likely your team would be doing it since you folks were actively discussing, but I couldn’t think of why someone else would do it either. Anyways, sorry and thanks for your time.
I don't understand why I would use this over aws CDK in python.
cdk is already an abstraction over the javascript cdk,
which is an abstraction over cloudformation,
which is an abstraction over the api..
I just want to navigate some of the claims made by Stelvio and others in this thread and see if maybe I'm missing something after reading the docs:
- Ship Python to AWS in minutes, not days: I can already do this with cdk? It's highly dependent on the project requirements. AWS already provides a sleuth of high level constructs with sensible defaults.
- great for really small apps where you want your resource definitions colocated with the code using them: CDK is just code? You can put it all in one place or split it into files. I don't get how this is new.
- easier to manage IAM permissions this is the bread and butter of cdk. I can simply do Resource.grantRead(lambdaFunction) without touching IAM. Who was complaining about this?
The only advantage I see here over CDK is using Pulumi as the underlying resource engine, which I admit performs better on deployment speed. But then we arrive to the question: Why not just use Pulumi, which already gives me IaC in python?
Our goal with Stelvio is bringing these two together: Using Pulumi (for performance and multi-cloud capatbilities) with the convenience of some parts of CDK.
There are way too many apps for converting config into code. I'd much rather see more like this that convert code into unnecessary config.
This is exactly what we had in mind as a first principle
It's unlikely to cover the AWS API's with 100% certainty, and I don't want to spend time trying to work out the kinks, so honestly, I'd rather just use the AWS CDK and CloudFormation.
It's not unlikely, I guarantee it will never happen. Because that's not the point.
Point is to cover most of the common cases (with escape hatch for fine-tuning in special case) and make those super easy and short to do so devs can focus on code and not infrastructure.
It's standard higher level abstraction play of doing more with less (code and time spent).
Thank you for the feedback.
So now I have to use two separate IAC frameworks?
Co-Author here. As long as you have trust in the underlying API of the Pulumi resources that Stelvio creates on your behalf, we have a mechanism in place that let's you fine-tune every parameter if you like. See: https://stelvio.dev/concepts/customization/
Otherwise, you can stick with Stelvio's sensible defaults if you wish.
You know you aren’t making a great case for yourself right? This is a solution looking for a problem.
We believe that we're creating a solution for problems that we fought with during a combined 40 years of experience in the team. ymmv, but you are invited to give it a try. Happy to show you a demo ;)
Yet I have never had those problems in 8 years of working with AWS including almost 4 working at AWS ProServe (no longer there). I would never depend on a third party IAC package aside from Terraform knowing the surface area of AWS services and nit knowing if this is still going to be supported a decade from now.