QuickStart: Deploy a .NET Core on Linux application to Elastic Beanstalk - Amazon Elastic Beanstalk
Your Amazon accountPrerequisitesStep 1: Create a .NET Core on Linux applicationStep 2: Run your application locallyStep 3: Deploy your .NET Core on Linux application with the EB CLIStep 4: Run your application on Elastic BeanstalkStep 5: Clean upAmazon resources for your applicationNext stepsDeploy with the console
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

QuickStart: Deploy a .NET Core on Linux application to Elastic Beanstalk

This QuickStart tutorial walks you through the process of creating a .NET Core on Linux application and deploying it to an Amazon Elastic Beanstalk environment.

Note

This QuickStart tutorial is intended for demonstration purposes. Do not use the application created in this tutorial for production traffic.

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.

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/ and choose Sign Up.

  2. 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/ 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) 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:

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.

~/eb-project$ this is a command
this is output

On Linux and macOS, you can use your preferred shell and package manager. On Windows you can install the Windows Subsystem for Linux to get a Windows-integrated version of Ubuntu and Bash.

EB CLI

This tutorial uses the Elastic Beanstalk Command Line Interface (EB CLI). For details on installing and configuring the EB CLI, see Install the EB CLI and Configure the EB CLI.

.NET Core on Linux

If you don't have the .NET SDK installed on your local machine, you can install it by following the Download .NET link on the .NET documentation website.

Verify your .NET SDK installation by running the following command.

~$ dotnet --info

Step 1: Create a .NET Core on Linux application

Create a project directory.

~$ mkdir eb-dotnetcore
~$ cd eb-dotnetcore

Next, create a sample Hello World application by running the following commands.

~/eb-dotnetcore$ dotnet new web --name HelloElasticBeanstalk
~/eb-dotnetcore$ cd HelloElasticBeanstalk

Step 2: Run your application locally

Run the following command to run your application locally.

~/eb-dotnetcore/HelloElasticBeasntalk$ dotnet run

The output should look something like the following text.

Building...
info: Microsoft.Hosting.Lifetime[14]
      Now listening on: https://localhost:7294
info: Microsoft.Hosting.Lifetime[14]
      Now listening on: http://localhost:5052
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]
Note

The dotnet command selects a port at random when running the application locally. In this example the port is 5052. 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:5052. The web browser should display “Hello World!”.

Step 3: Deploy your .NET Core on Linux 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 Linux application

  1. Compile and publish your application to a folder for deployment to the Elastic Beanstalk environment you're about to create.

    ~$ cd eb-dotnetcore/HelloElasticBeanstalk
~/eb-dotnetcore/HelloElasticBeanstalk$ dotnet publish -o site

  2. Navigate to the site directory where you just published your app.

    ~/eb-dotnetcore/HelloElasticBeanstalk$ cd site

  3. Initialize your EB CLI repository with the eb init command.

    Be aware of the following details regarding the platform branch version that you specify in the command:

    • Replace x.y.z in the following command with the latest version of the platform branch .NET 6 on AL2023.

    • To locate the latest platform branch version see .NET Core on Linux Supported platforms in the Amazon Elastic Beanstalk Platforms guide.

    • An example of a solution stack name that includes the version number is 64bit-amazon-linux-2023-v3.1.1-running-.net-6. In this example the branch version is 3.1.1.

    ~eb-dotnetcore/HelloElasticBeanstalk/site$ eb init -p 64bit-amazon-linux-2023-vx.y.z-running-.net-6 dotnetcore-tutorial --region us-west-2
Application dotnetcore-tutorial has been created.

    This command creates an application named dotnetcore-tutorial and configures your local repository to create environments with the .NET Core on Linux platform version specified in the command.

  4. (Optional) Run eb init again to configure a default key pair so that you can use SSH to connect to the EC2 instance running your application.

    ~eb-dotnetcore/HelloElasticBeanstalk/site$ eb init
Do you want to set up SSH for your instances?
(y/n): y
Select a keypair.
1) my-keypair
2) [ Create new KeyPair ]

    Select a key pair if you have one already, or follow the prompts to create one. If you don't see the prompt or need to change your settings later, run eb init -i.

  5. 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.

    to 

    ~eb-dotnetcore/HelloElasticBeanstalk/site$ eb create dotnet-tutorial

    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.

~eb-dotnetcore/HelloElasticBeanstalk/site$ eb open

Congratulations! You've deployed a .NET Core on Linux application with Elastic Beanstalk! 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.

~eb-dotnetcore/HelloElasticBeanstalk/site$ 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.

  • 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 in the Getting started chapter of this guide.

After you deploy a sample application or two and are ready to start developing and running .NET Core on Linux applications locally, see Setting up your .NET Core on Linux development environment.

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 in the Getting started chapter of this guide.