Setting up your environment - AWS SDK for .NET

Do you want to deploy your .NET applications to AWS in just a few simple clicks? Try our new .NET CLI tooling for a simplified deployment experience! Read our blog post and submit your feedback on GitHub!

For additional information, see the section for the deployment tool in this guide.

Setting up your environment

This is prerelease documentation for a feature in preview release. It is subject to change.

The following sections show you how to set up your environment to run the deployment tool.


The deployment tool requires the AWS Cloud Development Kit (CDK), and the AWS CDK requires Node.js version 10.13.0 or later (excluding versions 13.0.0 through 13.6.0). To see which version of Node.js you have installed, run the following command at the command prompt or in a terminal:

node --version

If the AWS CDK isn't installed on your machine or if the AWS CDK that's installed is earlier than the required minimum version (1.95.2), the deployment tool will install a temporary and "private" copy of the CDK that will be used only by the tool, leaving the global configuration of your machine untouched.

If instead you want to install the AWS CDK, see Install the AWS CDK in the AWS Cloud Development Kit (CDK) Developer Guide

.NET Core and .NET

Your application must be built from .NET Core 3.1 or later (for example, .NET Core 3.1, .NET 5.0, etc.). To see what version you have, run the following on the command prompt or in a terminal:

dotnet --version

For information about how to install or update .NET, see

(Optional) Docker

If you plan to deploy your application to Amazon Elastic Container Service (Amazon ECS) using AWS Fargate, you must have Docker installed where you run the deployment tool. For more information, see

(Linux and macOS) ZIP CLI

The ZIP CLI is used when creating ZIP packages for deployment bundles. It is used to maintain Linux file permissions.