# QuickStart: Deploy a .NET Core on Windows application to Elastic Beanstalk
This QuickStart tutorial walks you through the process of creating a .NET Core on Windows application and deploying it to an Amazon Elastic Beanstalk environment.
**Not for production use**
Examples are intended for demonstration only. Do not use example applications in production.
**Topics**
+ [Your Amazon account](#dotnet-quickstart-aws-account)
+ [Prerequisites](#dotnet-quickstart-prereq)
+ [Step 1: Create a .NET Core on Windows application](#dotnet-quickstart-create-app)
+ [Step 2: Run your application locally](#dotnet-quickstart-run-local)
+ [Step 3: Deploy your .NET Core on Windows application with the EB CLI](#dotnet-quickstart-deploy)
+ [Step 4: Run your application on Elastic Beanstalk](#dotnet-quickstart-run-eb-ap)
+ [Step 5: Clean up](#go-tutorial-cleanup)
+ [Amazon resources for your application](#dotnet-quickstart-eb-resources)
+ [Next steps](#dotnet-quickstart-next-steps)
+ [Deploy with the Elastic Beanstalk console](#dotnet-quickstart-console)
## Your Amazon account
If you're not already an Amazon customer, you need to create an Amazon account. Signing up enables you to access Elastic Beanstalk and other Amazon services that you need.
If you already have an Amazon account, you can move on to [Prerequisites](#dotnet-quickstart-prereq).
### Create an Amazon account
#### Sign up for an Amazon Web Services account
If you do not have an Amazon Web Services account, use the following procedure to create one.
**To sign up for Amazon Web Services**
1. Open [http://www.amazonaws.cn/](http://www.amazonaws.cn/) and choose **Sign Up**.
1. Follow the on-screen instructions.
Amazon sends you a confirmation email after the sign-up process is complete. At any time, you can view your current account activity and manage your account by going to [http://www.amazonaws.cn/](http://www.amazonaws.cn/) and choosing **My Account**.
#### Secure IAM users
After you sign up for an Amazon Web Services account, safeguard your administrative user by turning on multi-factor authentication (MFA). For instructions, see [Enable a virtual MFA device for an IAM user (console)](https://docs.amazonaws.cn/IAM/latest/UserGuide/id_credentials_mfa_enable_virtual.html#enable-virt-mfa-for-iam-user) in the *IAM User Guide*.
To give other users access to your Amazon Web Services account resources, create IAM users. To secure your IAM users, turn on MFA and only give the IAM users the permissions needed to perform their tasks.
For more information about creating and securing IAM users, see the following topics in the *IAM User Guide*:
+ [Creating an IAM user in your Amazon Web Services account](https://docs.amazonaws.cn//IAM/latest/UserGuide/id_users_create.html)
+ [Access management for Amazon resources](https://docs.amazonaws.cn/IAM/latest/UserGuide/access.html)
+ [Example IAM identity-based policies](https://docs.amazonaws.cn/IAM/latest/UserGuide/access_policies_examples.html)
## Prerequisites
To follow the procedures in this guide, you will need a command line terminal or shell to run commands. Commands are shown in listings preceded by a prompt symbol (>) and the name of the current directory, when appropriate.
```
C:\eb-project> this is a command
this is output
```
### EB CLI
This tutorial uses the Elastic Beanstalk Command Line Interface (EB CLI). For details on installing and configuring the EB CLI, see [Install EB CLI with setup script (recommended)](eb-cli3.md#eb-cli3-install) and [Configure the EB CLI](eb-cli3-configuration.md).
### .NET Core on Windows
If you don't have the .NET SDK installed on your local machine, you can install it by following the [Download .NET](https://dotnet.microsoft.com/en-us/download) link on the [.NET documentation](https://learn.microsoft.com/en-us/dotnet/) website.
Verify your .NET SDK installation by running the following command.
```
C:\> dotnet --info
```
## Step 1: Create a .NET Core on Windows application
Create a project directory.
```
C:\> mkdir eb-dotnetcore
C:\> cd eb-dotnetcore
```
Next, create a sample Hello World RESTful web service application by running the following commands.
```
C:\eb-dotnetcore> dotnet new web --name HelloElasticBeanstalk
C:\eb-dotnetcore> cd HelloElasticBeanstalk
```
## Step 2: Run your application locally
Run the following command to run your application locally.
```
C:\eb-dotnetcore\HelloElasticBeasntalk> dotnet run
```
The output should look something like the following text.
```
info: Microsoft.Hosting.Lifetime[14]
Now listening on: https://localhost:7222
info: Microsoft.Hosting.Lifetime[14]
Now listening on: http://localhost:5228
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Development
info: Microsoft.Hosting.Lifetime[0]
Content root path: C:\Users\Administrator\eb-dotnetcore\HelloElasticBeanstalk
```
**Note**
The `dotnet` command selects a port at random when running the application locally. In this example the port is 5228. When you deploy the application to your Elastic Beanstalk environment, the application will run on port 5000.
Enter the URL address `http://localhost:port` in your web browser. For this specific example, the command is `http://localhost:5228`. The web browser should display “Hello World\$1”.
## Step 3: Deploy your .NET Core on Windows application with the EB CLI
Run the following commands to create an Elastic Beanstalk environment for this application.
**To create an environment and deploy your .NET Core on Windows application**
1. Run the following commands in the `HelloElasticBeanstalk` directory to publish and zip your application.
```
C:\eb-dotnetcore\HelloElasticBeasntalk> dotnet publish -o site
C:\eb-dotnetcore\HelloElasticBeasntalk> cd site
C:\eb-dotnetcore\HelloElasticBeasntalk\site> Compress-Archive -Path * -DestinationPath ../site.zip
C:\eb-dotnetcore\HelloElasticBeasntalk\site> cd ..
```
1. Create a new file in the `HelloElasticBeanstalk` called `aws-windows-deployment-manifest.json` with the following contents:
```
{
"manifestVersion": 1,
"deployments": {
"aspNetCoreWeb": [
{
"name": "test-dotnet-core",
"parameters": {
"appBundle": "site.zip",
"iisPath": "/",
"iisWebSite": "Default Web Site"
}
}
]
}
}
```
1. Initialize your EB CLI repository with the **eb init** command.
```
C:\eb-dotnetcore\HelloElasticBeasntalk> eb init -p iis dotnet-windows-server-tutorial --region us-west-2
```
This command creates an application named `dotnet-windows-server-tutorial` and configures your local repository to create environments with the latest Windows server platform version.
1. Create an environment and deploy your application to it with **eb create**. Elastic Beanstalk automatically builds a zip file for your application and starts it on port 5000.
```
C:\eb-dotnetcore\HelloElasticBeasntalk> eb create dotnet-windows-server-env
```
It takes about five minutes for Elastic Beanstalk to create your environment.
## Step 4: Run your application on Elastic Beanstalk
When the process to create your environment completes, open your website with **eb open**.
```
C:\eb-dotnetcore\HelloElasticBeasntalk> eb open
```
Congratulations\$1 You've deployed a .NET Core on Windows application with Elastic Beanstalk\$1 This opens a browser window using the domain name created for your application.
## Step 5: Clean up
You can terminate your environment when you finish working with your application. Elastic Beanstalk terminates all Amazon resources associated with your environment.
To terminate your Elastic Beanstalk environment with the EB CLI run the following command.
```
C:\eb-dotnetcore\HelloElasticBeasntalk> eb terminate
```
## Amazon resources for your application
You just created a single instance application. It serves as a straightforward sample application with a single EC2 instance, so it doesn't require load balancing or auto scaling. For single instance applications Elastic Beanstalk creates the following Amazon resources:
+ **EC2 instance** – An Amazon EC2 virtual machine configured to run web apps on the platform you choose.
Each platform runs a different set of software, configuration files, and scripts to support a specific language version, framework, web container, or combination thereof. Most platforms use either Apache or nginx as a reverse proxy that processes web traffic in front of your web app, forwards requests to it, serves static assets, and generates access and error logs.
+ **Instance security group** – An Amazon EC2 security group configured to allow incoming traffic on port 80. This resource lets HTTP traffic from the load balancer reach the EC2 instance running your web app. By default, traffic is not allowed on other ports.
+ **Amazon S3 bucket** – A storage location for your source code, logs, and other artifacts that are created when you use Elastic Beanstalk.
+ **Amazon CloudWatch alarms** – Two CloudWatch alarms that monitor the load on the instances in your environment and are triggered if the load is too high or too low. When an alarm is triggered, your Auto Scaling group scales up or down in response.
+ **Amazon CloudFormation stack** – Elastic Beanstalk uses Amazon CloudFormation to launch the resources in your environment and propagate configuration changes. The resources are defined in a template that you can view in the [Amazon CloudFormation console](https://console.amazonaws.cn/cloudformation).
+ **Domain name** – A domain name that routes to your web app in the form **subdomain*.*region*.eb.amazonaws.com.cn*.
Elastic Beanstalk manages all of these resources. When you terminate your environment, Elastic Beanstalk terminates all the resources that it contains.
## Next steps
After you have an environment running an application, you can deploy a new version of the application or a different application at any time. Deploying a new application version is very quick because it doesn't require provisioning or restarting EC2 instances. You can also explore your new environment using the Elastic Beanstalk console. For detailed steps, see [Explore your environment](GettingStarted.md#GettingStarted.Explore) in the *Getting started* chapter of this guide.
**Try more tutorials**
If you'd like to try other tutorials with different example applications, see [QuickStart for ASP.NET](aspnet-quickstart.md).
After you deploy a sample application or two and are ready to start developing and running .NET Core on Windows applications locally, see [Setting up your .NET development environment](dotnet-devenv.md)
## Deploy with the Elastic Beanstalk console
You can also use the Elastic Beanstalk console to launch the sample application. For detailed steps, see [Create an example application](GettingStarted.md#GettingStarted.CreateApp) in the *Getting started* chapter of this guide.