Aws-Lambda on CuraDevOps

AWS Lambda recursive loop detection now GA in all commercial Regions

Tue, 01 Sep 2026 15:20:27 +0000

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

Wed, 26 Aug 2026 11:21:00 +0000

Platform/SRE — Plan: New GA capability that changes the connectivity architecture for Lambda MicroVMs in regulated environments — if you operate Lambda MicroVMs today or are evaluating them for compliance-sensitive workloads, schedule an evaluation to replace public-internet API paths with PrivateLink VPC Endpoints.
CI/CD — Skip
Leader — Learn: For organizations in financial services, healthcare, or government, this GA capability reduces a compliance blocker for Lambda MicroVM adoption, but no licensing, pricing, or vendor-risk decision is triggered — file as context for regulated-workload platform strategy.

Tue, 25 Aug 2026 11:19:32 +0000

Platform/SRE — Plan: Platform teams managing Lambda in multi-account architectures can now consolidate per-principal permission statements into single policy documents with full IAM condition key support (source IP, principal tags, etc.). Plan a policy consolidation pass for existing Lambda functions to reduce policy sprawl and simplify ongoing management.
CI/CD — Skip
Leader — Learn: This GA capability reduces IAM policy complexity for Lambda-heavy multi-account orgs, but it’s an incremental improvement rather than a strategic or cost-model shift — no leadership decision required.

Thu, 20 Aug 2026 11:19:17 +0000

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.

Thu, 06 Aug 2026 12:51:55 +0000

Platform/SRE — Learn: GA capability that may reduce execution time and cost for high-memory Lambda workloads outside a VPC; no deadline or migration required, but worth noting when sizing memory for data-intensive functions.
CI/CD — Skip
Leader — Skip

Tue, 04 Aug 2026 12:54:10 +0000

Platform/SRE — Plan: If you run high-throughput SQS-to-Lambda pipelines that previously required splitting workloads across multiple ESMs, this GA increase to 10,000 pollers and 100,000 concurrent invocations is worth consolidating architecture this quarter.
CI/CD — Skip
Leader — Skip
Signals: GA announcement

Sat, 25 Jul 2026 11:58:38 +0000

Platform/SRE — Learn: If your org uses Lambda Managed Instances for high-volume EC2-backed workloads, structured JSON lifecycle logs (launches, terminations, health checks) are now auto-enabled in CloudWatch — useful context for diagnosing provisioning issues, but no action required since it ships on by default.
CI/CD — Skip
Leader — Skip

Fri, 24 Jul 2026 12:15:09 +0000

Platform/SRE — Skip
CI/CD — Skip
Leader — Learn: Lambda durable functions now offer a native AWS alternative to external orchestration tools (Step Functions, Temporal) for .NET shops; worth factoring into workflow-tooling decisions for teams standardized on C#.
Signals: GA announcement

Wed, 15 Jul 2026 12:10:55 +0000

Platform/SRE — Plan: This GA capability removes the per-Region Lambda-managed storage quota for teams running large function/layer footprints; evaluate adopting S3ObjectStorageMode=REFERENCE this 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.