tag: Aws-Lambda · 19 items
- Platform/SRE — Learn: New GA observability plugin for Lambda durable functions exports execution history to 13 destinations including CloudWatch, S3, and OpenSearch; worth noting when designing telemetry for serverless workflows, but installed at the function-code level so no platform infrastructure change required.
- CI/CD — Skip
- Leader — Learn: New no-cost AWS capability for observability into long-running Lambda workflows; relevant context for teams standardizing on serverless architectures, but no licensing, cost, or vendor-risk decision is triggered.
- Platform/SRE — Learn: GA expansion of Lambda durable functions to GovCloud adds a new serverless orchestration primitive for multi-step workflows; worth noting for architecture decisions if your platform serves government or regulated-industry tenants in those regions, but no operational change required today.
- CI/CD — Skip
- Leader — Learn: If your org serves government or regulated-industry customers in GovCloud, this broadens available serverless orchestration options for compliant AI and workflow use cases — worth factoring into platform strategy conversations but no decision is pending.
- Platform/SRE — Learn: This SDK could inform how platform teams design infrastructure automation workflows in Go on Lambda (checkpointed multi-step jobs, approval gates), but it requires no changes to running infrastructure and there is no deadline.
- CI/CD — Learn: The durable execution model with approval gates and durable invocation is worth evaluating for deployment orchestration pipelines, but there is no existing migration or deadline driving immediate action.
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Plan: If your platform runs multi-step or agentic Lambda workflows, the 30,000 operation limit and 1 MB checkpoint open up architectures previously blocked by quota; evaluate whether existing workflows hitting the old 3,000-op ceiling should be redesigned to take advantage.
- CI/CD — Skip
- Leader — Learn: The expanded limits make Lambda durable functions more viable for long-running agentic AI orchestration, worth tracking if your org is evaluating serverless vs. container-based workflow engines for AI workloads.
- Platform/SRE — Learn: New GA AWS Lambda primitive supporting direct HTTP handling (Express/Hono, no adapters) with a different billing model; worth tracking for future platform architecture patterns, but no existing infrastructure needs changing and existing Lambda Event Functions require no migration.
- CI/CD — Skip
- Leader — Plan: The active-CPU billing model (vs. idle CPU) could meaningfully reduce Lambda costs for I/O-bound workloads; evaluate this as a golden-path serverless option and assess cost-optimization potential against current Lambda spend this planning cycle.
- Platform/SRE — Learn: Regional expansion of a GA serverless orchestration feature; relevant if you operate workloads in the EU Sovereign Cloud region and are evaluating durable workflows as an alternative to Step Functions or similar.
- CI/CD — Skip
- Leader — Learn: If your org has EU data-residency or sovereignty compliance requirements, this expands the serverless orchestration options available within the sovereign boundary — worth noting for future architecture decisions.
- Platform/SRE — Learn: New GA capability lets you tune Lambda S3 file read latency vs. throughput independent of function memory size, useful when designing data-processing or agentic workloads on Lambda; no action required today.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: If your org uses Lambda Managed Instances, evaluate migrating capacity providers to Graviton5 instance types (C9g, M9g) for up to 25% compute performance improvement at EC2 pricing; no deadline, but worth scheduling this quarter.
- CI/CD — Skip
- Leader — Learn: Graviton5 support in Lambda Managed Instances offers a potential cost/performance lever for teams running Lambda at scale on EC2; worth tracking as a FinOps input but no strategic decision required now.
- Platform/SRE — Learn: New AI-assisted diagnostic capability for Lambda and connected services (API Gateway, EventBridge, DynamoDB, etc.) is worth evaluating if your team uses AI coding agents, but it requires no platform-side change today.
- CI/CD — Skip
- Leader — Learn: AWS expanding MCP-based AI agent access to operational data is a directional signal for AI-assisted platform tooling strategy, but no procurement or standards decision is required yet.
- Platform/SRE — Plan: GA capability that reduces container image cold starts to sub-second by snapshotting initialized environments; worth adopting this quarter for latency-sensitive Lambda workloads (ML inference, interactive APIs) running on container images.
- CI/CD — Skip
- Leader — Learn: SnapStart extending to container images changes the cost/performance tradeoff for serverless-based architectures, informing build-vs-buy and platform strategy discussions around cold-start optimization.
- 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 — 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.
- 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.
- 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: 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
- 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
- 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
- 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
- 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.