I soon have to spin up an ec2 with a nitro enclave...
# general
d
I soon have to spin up an ec2 with a nitro enclave. I'm considering using just aws-cdk, but is there any advantages to using sst for this? I do like the abstracted components sst offers (queues, buckets, etc). I expect most of the application code will be some app wrapped in docker. I've used SST heavily already for lambda based work. Question: Does sst offer significant benefits if we're not using lambdas?
t
we're starting to provide better patterns for things like stack definition that are way more typescript friendly than CDK
It's going to be pretty minor to start but we're continuing down this path. Starting to recommend using SST even if you're just using cdk constructs
there's a lot of tiny things we do that cdk doesn't do natively like parallel stack deployment and fixing that annoying export issue automatically
d
Oh, I will never forget the export var. that alone may be enough reason itself. Thank you
s
Sometimes I need to run lambda to do post-deployment updates not supported by aws-cdk. It is especially true for ECS/EC2/VPC IaC code. I prefer to have SST on my side in such case :)