Skip to content
aizkaizk

AWS and CockroachDB Cloud

This public site is part of the AIZK hackathon deployment. The same AWS origin serves the landing page, these docs, the browser app and the MCP endpoint.

Public site
https://xpc3f5mjuv5edgnsfsfbffcoda0ckvij.lambda-url.ap-southeast-1.on.aws/
MCP endpoint
https://xpc3f5mjuv5edgnsfsfbffcoda0ckvij.lambda-url.ap-southeast-1.on.aws/mcp

Use the origin printed above for the website and MCP endpoint. Other AIZK deployments are separate systems with their own users and memory.

The live AIZK deployment uses one public Lambda origin and one private workerverifyinvokebrowser or MCP clientpublic Lambdasite, docs and appMCP and OAuthworker LambdaCockroachDB Cloudprivate S3 bucketLogtohosted model APIs

Why the stack is small

Section titled “Why the stack is small”

The deployment uses two Lambda functions built from one immutable ECR image digest. The public function handles HTTP and serves committed static assets. The worker drains durable work in bounded batches. An EventBridge Scheduler rule wakes recovery work and another keeps the public path warm during the demo.

CockroachDB Cloud is the persistent memory layer. It stores documents, claims, vectors, scopes, temporal history, usage and queue state. Native C-SPANN serves the scoped vector path. A private, encrypted S3 bucket stores original artifact bytes under opaque keys.

SSM Parameter Store holds deployment secrets. CloudWatch retains structured Lambda logs for seven days. An AWS Budget watches demo spend. Logto verifies users and organizations. Hosted model APIs provide extraction, captions and text embeddings.

The demo describes figures as text and embeds those descriptions. It does not call the production image-embedding lane. The source keeps that multimodal capability available for other deployments.

The stack intentionally has no API Gateway, load balancer, VPC, NAT gateway, EC2 instance, ECS cluster or separate static hosting service. A Lambda Function URL is enough for this bounded demo.

Routes on one origin

Section titled “Routes on one origin”
Route Purpose
/ landing page
/docs/ user and developer documentation
/app/ browser UI
/mcp modern MCP endpoint and OAuth discovery

Keeping one origin makes the submission easy to inspect and avoids sending a visitor to another deployment. The build receives its own public URL through AIZK_DOCS_SITE_URL, so canonical metadata and client examples match the deployed image.

Demo limits

Section titled “Demo limits”

The AWS profile is tuned for a public demonstration. Each upload is limited to 4 MiB, and each user may store at most 1 GiB of original files. Monthly operation and write limits bound hosted model and database spend. Expensive retrieval lanes and maintenance passes can be disabled through settings when their measured quality gain does not justify demo latency.

These controls make the deployment cheaper and simpler. They do not change the source, evidence, scope or temporal semantics that define AIZK.

Reproduce the deployment

Section titled “Reproduce the deployment”

Infrastructure lives in infra/aws/ and is declared with AWS CDK. The full operator commands and required SSM parameters are in the repository runbook. The immutable image contains the server, worker, website, docs and web app, so one digest identifies the complete submitted build.

Next

Section titled “Next”