This week finally migrated all my stuff from SLS to SST… kind of side-project for fun… but also needed to scale the Platform, we are expecting 2x more services coming soon. So far so good, we only have 7 micro-services, and maybe 30 lambdas in total, 4 or 5 dynamo tables, 2 eventBus, 5 queues, etc… Medium project size I would say, but the code is way cleaner than having segregated SLS config files. With SLS was really hard to share resources/dependencies, not clean and hard to understand for developers with no IaC/CF experience. I’ve been using AWS Console to compare my old/new resources, and all looks fine, the only thing I noticed is my Lambdas size are 2x now, from 2MB on SLS to 4MB on SST. I believe might the due the

.map

file is included in the bundle now, and before with SLS might not be there. Is there a real need to include

.map

file? I’m not familiarized how to take advantage of it.

Yeah I think we should have an option to disable

.map

. (@thdxr @Jay what do u guys think)

@Frank well, maybe there is a good usage for it, I just don’t know how to take advantage of it yet. I’m using Epsagon for monitoring, but doesn’t look to do any difference.

Packaging

.map

with ur Lambda code gives sensible line numbers in CloudWatch stacktrace.

Yeah, but is cloudwatch aware of that?

yup

Thank you.