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.

▲

antonymoose 7 hours ago | parent | next [-]

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.

	▲	sebst 6 hours ago \| parent [-]
		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?

▲

tuhgdetzhh 7 hours ago | parent | prev | next [-]

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.

▲

sebst 8 hours ago | parent | prev | next [-]

Appreciate it! Let me know if you’d like to chat about your experience at some point in time!

▲

yowlingcat 5 hours ago | parent | prev [-]

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?