Deployment

Every Kanject service ships with CloudFormation templates and aws-lambda-tools configs for staging and production. One command deploys the whole stack.

bash 
# aws-lambda-tools-defaults.json already configured —
# just pick the target environment

# Staging
dotnet-lambda deploy-serverless \
    -cfg aws-lambda-tools.stage.json

# Production
dotnet-lambda deploy-serverless \
    -cfg aws-lambda-tools.prod.json

# Kanject.Core.Adapter wires up:
#   • CloudFormation stack with IAM, API Gateway, Lambda
#   • Parameter Store lookup at cold-start
#   • CORS, exception middleware, warm-up endpoints
#   • Per-environment appsettings overrides

What gets provisioned

  • An API Gateway HTTP API, mapped to your Lambda function
  • IAM role with scoped permissions for DynamoDB, S3, SNS, and Parameter Store
  • CloudWatch log group with structured-log ingestion enabled
  • Per-environment stack names so staging and production stay fully isolated