⚡

Serverless API

API Gateway (REST API) → Lambda → DynamoDB. Zero servers, scales to zero.

What you can build with this

Build a backend for a mobile app or SPA with no servers to manage. The REST API is a full proxy: a root "/" method and a "{proxy+}" catch-all forward EVERY path and HTTP method to your Lambda function — your code handles routing, not API Gateway. There is no authorizer by default (AuthorizationType NONE) — add your own auth in code, or connect a Cognito User Pool to the REST API node on canvas before exporting to get a real COGNITO_USER_POOLS authorizer wired onto every method. The Lambda has read/write access to the DynamoDB table through an explicit IAM policy scoped to that table's ARN — the canvas deliberately does NOT draw a data edge between the Lambda and the table (any such edge makes the engine force-enable DynamoDB Streams and re-invoke your function on every write, which a plain CRUD API does not want).

Deployment timing

After you run the deploy command, resources come online at different times. Check the validation steps in order.

Resource	Ready in
DynamoDB Table	Immediate
Lambda Function + IAM Role	30–60 sec
REST API + Deployment + Stage	1–2 min (stack CREATE_COMPLETE)

CloudFormation parameters

These are the values you will fill in when deploying the exported template. Changing these does not break the template — that is the point.

Parameter	What to provide	Example
Environment	Environment tag applied to resources (does not rename them); also becomes the API stage name	dev