AWS Lambda

Trigger any deployed Lambda function synchronously and get its response — useful for running business logic on demand without managing a server.

Fire a Lambda function and continue without waiting for its response — ideal for kicking off long-running jobs or fan-out pipelines.

Invoke a Lambda function and block until it returns — best for request-response flows where the result is needed before the next step.

Execute an arbitrary code snippet directly inside Lambda without pre-deploying a function — useful for one-off computations and ad-hoc data transforms.

Retrieve the full catalogue of deployed Lambda functions in an AWS account so the agent can audit, compare, or select the right function by name.

Fetch the configuration, runtime, memory, and deployment details of a specific Lambda function for inspection or comparison.

Deploy a new Lambda function with specified runtime, handler, IAM role, and environment variables — the full function provisioning in one step.

Push new deployment package bytes to an existing Lambda function to roll out code changes without recreating the function's configuration.

Modify a Lambda function's memory allocation, timeout, environment variables, or concurrency limits without touching the deployed code.

Permanently remove a Lambda function and all its versions from the account — use to decommission unused functions and stop accruing storage costs.

Grant a specific AWS service or principal the permission to invoke a Lambda function, enabling event-driven integrations without manual IAM edits.

Retrieve the resource-based policy attached to a Lambda function to audit which principals and services are allowed to invoke it.

Enumerate every published version of a Lambda function to support rollback decisions, version pinning, and deployment audits.

Create an immutable numbered version snapshot of the current function code and configuration, locking it in place for alias pinning or rollback.

Define a named pointer to a specific Lambda version or a weighted split between two versions, enabling blue/green and canary deployment patterns.

Shift an existing Lambda alias to point at a different version or adjust the canary traffic split — the primary mechanism for progressive and rollback deployments.

Retrieve account-level Lambda quotas including total code storage used, concurrent executions limit, and unreserved concurrency capacity.

Fires whenever a new Lambda function is created in your account, enabling immediate downstream registration, notification, or policy enforcement.

Fires whenever an existing Lambda function's code or configuration is modified, allowing the agent to log the change, notify stakeholders, and trigger downstream validation steps.

Fires when a Lambda function returns an error response, enabling the agent to triage, escalate, or initiate a rollback before the error rate reaches user-visible thresholds.

Fires whenever a Lambda function is removed from the account, enabling the agent to log the deletion, clean up dependent resources, and alert the team to potential service gaps.

Fires when a Lambda function's reserved concurrency limit is hit and invocations begin throttling, enabling the agent to alert, scale, or shed load before customer-facing errors accumulate.

Fires when a Lambda function execution exceeds its configured timeout and is forcibly terminated, enabling the agent to log the event, investigate the cause, and prevent recurrence.