Guides

The Concepts section explains how Axis thinks; the Guides show you how to do things. Each guide is a focused recipe grounded in the framework’s synth-tested example projects, so the code you see is code that actually builds.

API surfaces

Pick the API style your project scaffolds with, then wire routes and auth:

• REST v1 API — API Gateway REST, the full-breadth default.
• HTTP v2 API — API Gateway HTTP API, the leaner v2 surface.
• GraphQL API — AppSync with VTL/JS resolvers.
• The Auth Matrix — cognito | none | iam | custom plus API keys, per route.

Data, storage, and messaging

• DynamoDB Tables — keys, GSIs, streams, TTL, billing.
• Storage & Encryption — S3, KMS, and Secrets Manager.
• Messaging — SQS with DLQ-by-default, SNS, and EventBridge.
• Workers & Cron — standalone and scheduled Lambdas.

Operate and secure

• Observability & Alerting — alarms, dashboards, Slack/Teams.
• Budgets & Cost — AWS Budgets wired to alerts.
• Security Perimeter — WAF and SES.
• CloudFront Edge — distributions and Lambda@Edge.

Developer workflow

• SDK Generation — typed REST/GraphQL clients from your config.
• Importing Existing Resources — reference or adopt resources by ARN.
• AI-Assisted Workflow — axs context, axs doctor, and the manifest.

A note on the layout matrix

Guides use module layout (lambdas/modules/...) in their paths. Feature layout (lambdas/features/...) is identical in behaviour and differs only in where files live — see Layout: Module vs Feature. The feature layout is supported for the rest-v1, rest-v2, graphql, and worker starters (bare is module-only); where a guide’s example depends on that, it says so.