Getting Started

Kanject is a .NET CLI plus a suite of libraries that takes a C# AWS Lambda service from dotnet new to kanject aws deploy --env prod — wrapping the dotnet/AWS toolchain so the inner-loop stays vanilla and the AWS plumbing disappears behind one manifest.

You don't manage EC2, Kubernetes, or connection pools. You scaffold with kanject new, declare your AWS targets in a single kanject-cli/manifest.json, then deploy with one command. Identity, persistence, event publishing, observability and rollback are opt-in libraries — pick what you need.

01
Install
Install the kanject CLI as a .NET global tool from your team's feed.
02
Scaffold
`kanject new` lays down a project; `kanject init` wires the manifest.
03
Deploy
`kanject aws deploy --env dev` builds, packages and ships in one command.

Prerequisites

  • .NET 10 SDK or later — the runtime and dotnet CLI everything builds on
  • AWS CLI 2.x — used by deploy, rollback, add param, add secret, preview, and pipeline bootstrap
  • git 2.x — required for cross-repo dependency resolution (add lib, sync, migrate)
  • Amazon.Lambda.Tools — the AWS-supplied tool kanject calls for packaging and deploys
  • An AWS account you control — kanject deploys into your environment, not a managed host
  • Access credentials for the kanject NuGet feed (typically AWS CodeArtifact — request from your admin)