Working with the AWS CDK in C# - AWS Cloud Development Kit (AWS CDK)

Working with the AWS CDK in C#

.NET is a fully-supported client platform for the AWS CDK and is considered stable. Our .NET code examples are in C#. It is possible to write AWS CDK applications in other .NET languages, such as Visual Basic or F#, but we are unable to provide support for these languages.

You can develop AWS CDK applications in C# using familiar tools including Visual Studio, the dotnet command, and the NuGet package manager. The modules comprising the AWS Construct Library are distributed via

We suggest using Visual Studio 2019 (any edition) and the Microsoft .NET Framework on Windows to develop AWS CDK apps in C#. You may use other tools (for example, Mono on Mac OS X or Linux), but our ability to provide instruction and support for these environments may be limited.


To work with the AWS CDK, you must have an AWS account and credentials and have installed Node.js and the AWS CDK Toolkit. See AWS CDK Prerequisites.

C# AWS CDK applications require a .NET Standard 2.1 compatible implementation. Suitable implementations include:

  • .NET Core v3.1 or later

  • .NET Framework v4.6.1 or later

  • Mono v5.4 or later on Mac OS X or Linux; download here

If you have an up-to-date Windows 10 installation, you already have a suitable installation of .NET Framework.

The .NET Standard toolchain includes dotnet, a command-line tool for building and running .NET applications and managing NuGet packages. Even if you are using Visual Studio, this command is useful for batch operations and for installing AWS Construct Library packages.

Creating a project

You create a new AWS CDK project by invoking cdk init in an empty directory.

mkdir my-project cd my-project cdk init app --language csharp

cdk init uses the name of the project folder to name various elements of the project, including classes, subfolders, and files.

The resulting project includes a reference to the Amazon.CDK NuGet package. It and its dependencies are installed automatically by NuGet.

Managing AWS Construct Library modules

The .NET ecosystem uses the NuGet package manager. AWS Construct Library modules are named like Amazon.CDK.AWS.SERVICE-NAME where the service name is a short name without an AWS or Amazon prefix. For example, the NuGet package name for the Amazon S3 module is Amazon.CDK.AWS.S3. If you can't find a package you want, search


The .NET edition of the CDK API Reference also shows the package names.

Some services' AWS Construct Library support is in more than one module. For example, Amazon Route 53 has the three modules in addition to the main Amazon.CDK.AWS.Route53 module, named Route53.Patterns, Route53rResolver, and Route53.Targets.

The AWS CDK's core module, which you'll need in most AWS CDK apps, is imported in C# code as Amazon.CDK. Modules for the various services in the AWS Construct Library live under Amazon.CDK.AWS and are named the same as their NuGet package name. For example, the Amazon S3 module's namespace is Amazon.CDK.AWS.S3.

We recommend writing a single C# using directive for each AWS Construct Library module you use in each of your C# source files. You may find it convenient to use an alias for a namespace or type to help resolve name conflicts. You can always use a type's fully-qualfiied name (including its namespace) without a using statement.


All AWS Construct Library modules used in your project must be the same version.

NuGet has four standard, mostly-equivalent interfaces; you can use the one that suits your needs and working style. You can also use compatible tools, such as Paket or MyGet.

The Visual Studio NuGet GUI

Visual Studio's NuGet tools are accessible from Tools > NuGet Package Manager > Manage NuGet Packages for Solution. Use the Browse tab to find the AWS Construct Library packages you want to install. You can choose the desired version, including pre-release versions (mark the Include prerelease checkbox) and add them to any of the open projects.


All AWS Construct Library modules deemed "experimental" (see Versioning) are flagged as pre-release in NuGet.

Look on the Updates page to install new versions of your packages.

The NuGet console

The NuGet console is a PowerShell-based interface to NuGet that works in the context of a Visual Studio project. You can open it in Visual Studio by choosing Tools > NuGet Package Manager > Package Manager Console. For more information about using this tool, see Install and Manage Packages with the Package Manager Console in Visual Studio.

The dotnet command

The dotnet command is the primary command-line tool for working with Visual Studio C# projects. You can invoke it from any Windows command prompt. Among its many capabilities, dotnet can add NuGet dependencies to a Visual Studio project.

Assuming you're in the same directory as the Visual Studio project (.csproj) file, issue a command like the following to install a package.

dotnet add package Amazon.CDK.AWS.S3

You may issue the command from another directory by including the path to the project file, or to the directory that contains it, after the add keyword. The following example assumes that you are in your AWS CDK project's main directory.

dotnet add src/PROJECT-DIR package Amazon.CDK.AWS.S3

To install a specific version of a package, include the -v flag and the desired version. AWS Construct Library modules that are deemed "experimental" (see Versioning) are flagged as pre-release in NuGet, and must be installed using an explicit version number.

dotnet add package Amazon.CDK.AWS.S3 -v VERSION-NUMBER

To update a package, issue the same dotnet add command you used to install it. If you do not specify a version number, the latest version is installed. For experimental modules, again, you must specify an explicit version number.

For more information about managing packages using the dotnet command, see Install and Manage Packages Using the dotnet CLI.

The nuget command

The nuget command line tool can install and update NuGet packages. However, it requires your Visual Studio project to be set up differently from the way cdk init sets up projects. (Technical details: nuget works with Packages.config projects, while cdk init creates a newer-style PackageReference project.)

We do not recommend the use of the nuget tool with AWS CDK projects created by cdk init. If you are using another type of project, and want to use nuget, see the NuGet CLI Reference.

AWS CDK idioms in C#


All AWS Construct Library classes are instantiated using three arguments: the scope in which the construct is being defined (its parent in the construct tree), a name, and props, a bundle of key/value pairs that the construct uses to configure the resources it creates. Other classes and methods also use the "bundle of attributes" pattern for arguments.

In C#, props are expressed using a props type. In idiomatic C# fashion, we can use an object initializer to set the various properties. Here we're creating an Amazon S3 bucket using the Bucket construct; its corresponding props type is BucketProps.

var bucket = new Bucket(this, "MyBucket", new BucketProps { Versioned = true });

Add the package Amazon.JSII.Analyzers to your project to get required-values checking in your props definitions inside Visual Studio.

When extending a class or overriding a method, you may want to accept additional props for your own purposes that are not understood by the parent class. To do this, subclass the appropriate props type and add the new attributes.

// extend BucketProps for use with MimeBucket class MimeBucketProps : BucketProps { public string MimeType { get; set; } } // hypothetical bucket that enforces MIME type of objects inside it class MimeBucket : Bucket { public MimeBucket(final Construct scope, final string id, final MimeBucketProps props=null) : base(scope, id, props) { // ... } } // instantiate our MyBucket class var bucket = new MyBucket(this, "MyBucket", new MimeBucketProps { Versioned = true, MimeType = "image/jpeg" });

When calling the parent class's initializer or overridden method, you can generally pass the props you received. The new type is compatible with its parent, and extra props you added are ignored.

Keep in mind that future releases of the AWS CDK may coincidentally add a new property with a name you used for your own property. This won't cause any technical issues using your construct or method (since your property isn't passed "up the chain," the parent class or overridden method will simply use a default value) but it may cause confusion for your construct's users. You can avoid this potential problem by naming your properties so they clearly belong to your construct. If there are many new properties, bundle them into an appropriately-named class and pass them as a single property.

Generic structures

In some places, the AWS CDK uses JavaScript arrays or untyped objects as input to a method. (See, for example, AWS CodeBuild's BuildSpec.fromObject() method.) In C#, objects are represented as System.Collections.Generic.Dictionary<String, Object>. In cases where the values are all strings, you can use Dictionary<String, String>. JavaScript arrays are represented as object[] or string[] in C#.

Missing values

In C#, missing values in AWS CDK objects such as props are represented by null. The null-conditional member access operator ?. and the null coalescing operator ?? are convenient for working with these values.

// mimeType is null if props is null or if props.MimeType is null string mimeType = props?.MimeType; // mimeType defaults to text/plain. either props or props.MimeType can be null string MimeType = props?.MimeType ?? "text/plain";

Building, synthesizing, and deploying

The AWS CDK automatically compiles your app before running it. However, it can be useful to build your app manually to check for errors and run tests. You can do this by pressing F6 in Visual Studio or by issuing dotnet build src from the command line, where src is the directory in your project directory that contains the Visual Studio Solution (.sln) file.

The stacks defined in your AWS CDK app can be deployed individually or together using the commands below. Generally, you should be in your project's main directory when you issue them.

  • cdk synth: Synthesizes a AWS CloudFormation template from one or more of the stacks in your AWS CDK app.

  • cdk deploy: Deploys the resources defined by one or more of the stacks in your AWS CDK app to AWS.

You can specify the names of multiple stacks to be synthesized or deployed in a single command. If your app defines only one stack, you do not need to specify it.

cdk synth # app defines single stack cdk deploy Happy Grumpy # app defines two or more stacks; two are deployed

You may also use the wildcards * (any number of characters) and ? (any single character) to identify stacks by pattern. When using wildcards, enclose the pattern in quotes. Otherwise, the shell may try to expand it to the names of files in the current directory before they are passed to the AWS CDK Toolkit.

cdk synth "Stack?" # Stack1, StackA, etc. cdk deploy "*Stack" # PipeStack, LambdaStack, etc.

You don't need to explicitly synthesize stacks before deploying them; cdk deploy performs this step for you to make sure your latest code gets deployed.

For full documentation of the cdk command, see AWS CDK Toolkit (cdk command).