AWS Lambda

The concept of serverless architecture was first popularized by AWS Lambda in 2014.

Firecracker microVM is the lightweight virtual machine technology underlying AWS Lambda.

Firecracker is the underlying technology of AWS Lambda.

AWS Lambda is a serverless computing service that adopts an event-driven model and charges based on the actual number of invocations.

Firecracker microVM was developed and open-sourced by AWS, is widely used in serverless platforms such as AWS Lambda, and can achieve a startup time as low as 125 milliseconds.

The AWS Lambda deployment package size limit is 250 MB (unzipped), with a maximum memory of 10 GB and a maximum execution time of 15 minutes.

2022年后随着AWS Lambda、Vercel等无服务器基础设施普及以及OpenAI API商业化，出现了大量基于LLM的Micro-SaaS产品

The S3 API has given rise to a large toolchain ecosystem, including the AWS CLI, SDKs for various languages, s3cmd, rclone, and others.

Firecracker 最初由 AWS 为 Lambda 和 Fargate 服务开发

Traditional function computing (such as AWS Lambda) and most code sandboxes follow a stateless design, starting a brand-new instance for each invocation and destroying it once execution finishes, with state not retained across invocations.

Platforms such as Cloudflare Workers, Vercel Edge Functions, and AWS Lambda are all affected by cold starts, in which synchronous evaluation during the module import phase is directly counted toward cold start time.

RepoPilot's tech stack includes: Amazon Nova Pro on Amazon Bedrock for reasoning and narration, AWS Lambda (python3.12) hosting the Agent, Amazon API Gateway in front for the Web UI to call, a local CLI based on the Strands Agents SDK, and seven pure-Python tools that feed inputs to the scoring engine.

Packing requests into the AWS Lambda zip hits a wall: the urllib3 it bundles imports content removed in Python 3.12; after rewriting the GitHub scraper with the standard library, the RepoPilot package shrank from 400KB to 13KB.

The egress IPs of Serverless/CI environments such as Vercel, AWS Lambda and GitHub Actions runners are shared and change frequently, making a fixed proxy hard to configure, and such environments usually limit execution duration and outbound connection counts.

In serverless environments such as AWS Lambda or Vercel Functions, frameworks usually have already parsed the request body, so signature verification can only be performed by relying on the platform's provided raw body access method (such as API Gateway's event.body together with the isBase64Encoded flag).

The Banana service is deployed on AWS Lambda and backed by FalkorDB Cloud.

In serverless architecture, functions have a cold start problem: the first execution after a function has not been called for a long time is slower, and the heavier the initialization logic, the more pronounced it is.

In a CDK event-driven architecture, the event source usually comes from AWS Organizations; when a new account is created within the organization, an account is moved into a certain OU, or an organization-level policy changes, Organizations emits an event, which is routed via Amazon EventBridge to processing logic (such as a Lambda function), which then calls License Manager APIs to complete MPPO activation.

The AWS MCP Server lets coding agents connect to running AWS backends via the Model Context Protocol, allowing them to inspect Lambda functions and their associated services (such as API Gateway and databases), not just local code.

CloudWatch alarms can trigger downstream actions such as emails, Lambda, or PagerDuty via SNS, realizing a closed loop of 'notify when drift exceeds the threshold'.