tag: Serverless · 4 items
- Platform/SRE — Learn: This default-on guardrail stops runaway Lambda recursion via S3/SQS/SNS and sends Health Dashboard alerts; worth knowing if you operate Lambda at scale, and note that intentional recursive patterns now require explicit opt-out via PutFunctionRecursionConfig.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Learn: Lambda MicroVMs is now GA in Frankfurt, Stockholm, Mumbai, Singapore, and Sydney, giving platform teams a managed VM-isolation primitive for multi-tenant or AI workload sandboxing without managing hypervisors. No action required — worth evaluating if latency or data-residency in these regions is a current pain point.
- CI/CD — Skip
- Leader — Learn: The regional expansion signals AWS maturing Lambda MicroVMs as a serious compute tier for AI coding assistants and sandboxed execution — worth tracking as a potential building block for internal developer platform strategy, though no decision is needed today.
- Platform/SRE — Learn: Public preview of serverless JavaScript execution at the Azure Front Door edge layer — worth evaluating if you run AFD as your ingress/CDN layer, but pre-GA so no action yet.
- CI/CD — Skip
- Leader — Skip
- Signals: pre-GA (alpha/beta/RC/preview)
- Platform/SRE — Plan: This GA capability removes the per-Region Lambda-managed storage quota for teams running large function/layer footprints; evaluate adopting
S3ObjectStorageMode=REFERENCEthis quarter for deployments approaching the old 75GB ceiling, and note the default limit has already been raised to 300GB for all accounts. - CI/CD — Skip
- Leader — Learn: Cost impact is neutral-to-positive (standard S3 rates replace implicit Lambda storage overhead) with no forced migration, but worth flagging to platform teams running high function counts so they can evaluate whether S3-backed storage fits their existing artifact management posture.