HOLY CRAP, PEOPLE. Lambda’s /tmp folder’s max size...
# random
s
HOLY CRAP, PEOPLE. Lambda’s /tmp folder’s max size is increasing from 512MB to 10GB!
a
Announced in re-invent?
s
yessir, just Julian Wood from AWS announce it
that’ll be great for processing large files
a
Nice.
Agreed!
Is always 10 or depends on memory size?
s
sounds like you set the limit. not totally sure though
CloudWatch RUM and Evidently are also really exciting additions
a
RUM?
Tell me more 🙂
I had to pause my re-invent videos, hahaa.
s
it’s not booze, sadly 😆 Real-time User Monitoring.
a
Production issues can not wait haha.
😮
s
so, all kinds of real-time stats on your web app. performance, users’ browser/OS, etc
a
Nice, so you can use it as Sentry?
Or it’s a different thing?
s
it’s different. Sentry is still great for error logging.
this is CloudWatch RUM
a
Niceeee.
Loving it, we have 2 or 3 react apps.
s
and then there’s CloudWatch Evidently, which is feature flagging. very cool! so you can slowly roll out a new feature in your app to 10% of your users, or 50%.. or other determing factors too, I think.. maybe by tag or user ID
a
Wouu!
I was looking to do feature flag!
s
yeah! now we can do it like the big companies do it 😄
a
Haaha.
Thanks for sharing.
s
sure thing 🙂
a
I’ve just shared with my CTO, this is exiting.
We were about to build a feature flag in-house thing 😂 .
s
yeah, I’ve done it before just in the code itself.. for any user who opted into beta features. but this is much better, since you can tweak it from the AWS console
a
Exactly.
The management side it’s what I want to avoid doing.
t
Wow
a
@thdxr new stuff to add to SST 😂 .
t
Haha
Also is Evidently the worst named AWS service
s
it makes no sense
a
It’s… evident.
t
Would you move seed to lambda 👀