AWS .NET deployment tool for the .NET CLI - 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.

AWS .NET deployment tool for the .NET CLI

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

After you've developed your cloud-native .NET Core application on a development machine, you'll most likely want to deploy it to AWS.

Deployment to AWS sometimes involves multiple AWS services and resources, each of which must be configured. To ease this deployment work, you can use the AWS .NET deployment tool for the .NET CLI, or deployment tool for short.


If you develop on Windows with Visual Studio, you might have the AWS Toolkit for Visual Studio installed. The toolkit provides similar deployment functionality in its Publish to AWS feature. For information about toolkit versions and using the feature, see Publish to AWS in the AWS Toolkit for Visual Studio User Guide.

When you run the deployment tool for a .NET Core application, the tool shows you all of the AWS compute-service options that are available to deploy your application. It suggests the most likely choice, as well as the most likely settings to go along with that choice. It then builds and packages your application as required by the chosen compute service. It generates the deployment infrastructure, deploys your application by using the AWS Cloud Development Kit (CDK), and then displays the endpoint.

You can select deployment options interactively or specify them in a JSON configuration file. You can also keep the default values that the tool selects for you.


  • Deploys to AWS Elastic Beanstalk or Amazon ECS (using AWS Fargate).

  • Deploys cloud-native .NET applications that are built with .NET Core 2.1 and later, and that are written with the intent to deploy to Linux. Such an application isn't tied to any Windows-specific technology such as the Windows Registry, IIS, or MSMQ, and can be deployed on virtualized compute.

  • Deploys ASP.NET Core web apps, Blazor WebAssembly apps, long-running service apps, and scheduled tasks. For more information, see the README in the GitHub repo.