On the Launch Status page, click the View Instances button at the bottom. If using a Windows terminal, follow the AWS instructions to download the PuTTYgen utility and convert the. For the tutorial we’re placing it in the /Desktop/NGINX directory. pem file (in the tutorial, NGINX_key.pem) to a secure location. In your file manager utility, move the downloaded. Click it to indicate that you can access the private key. Type a name in the Key pair name field, such as NGINX_key.Īs shown in the animated screenshot below, a check box replaces the Download Key Pair button. Select Create a new key pair from the upper drop‑down menu. In the box that pops up, create a new key pair: On the Step 7 page, click the Launch button at the bottom. For production environments, we recommend you follow the warning on the page which mandates use of security groups to control access.Ĭlick the Review and Launch button at the bottom of the page. For the purposes of this tutorial, we are allowing access from any IP address (the value in the Source column is Anywhere 0.0.0.0/0, ::/0). On the Step 6 page, perform the following steps to allow incoming HTTP and HTTPS traffic (by default EC2 instances accept only SSH traffic):Ĭlick the Add Rule button below the table, then select HTTP from the drop‑down menu in the Type column. Configure Security Group at the top of the page. Leave the rest of the settings at their defaults.Ĭlick 6. On the Step 3 page, make sure the VPC you want to use is selected in the Network field, and that the Auto-assign Public IP field is set either to the default Use Subnet setting (Enable) or to Enable. Click the Next: Configure Instance Details button. On the Step 2 page, select the t2.micro instance type, which as of this writing is marked Free tier eligible and selected by default. On the Step 1 page, click the Select button in the Ubuntu Server 20.04 LTS (HVM), SSD Volume Type row, and keep the default 64-bit (x86) architecture selection. On the AWS home page, sign in to the (AWS Management) Console, or first create a new account if necessary.Ĭlick Services in the Console title bar, then EC2 in the Compute section.Ĭlick the Launch Instance button on the EC2 Dashboard page that opens. Note: The following procedure and screenshots for creating an EC2 instance were verified at the time of writing, but are subject to change by AWS. In this section, you set up your AWS deployment by creating an EC2 instance and connecting to it. In this tutorial we assume that you have an Amazon Virtual Private Cloud (VPC) and can simply use the default VPC configuration that is created with most accounts. You can’t access the actual terminal until you finish the steps in the Setting up AWS, however. Along with AWS, we recommend PuTTY, an ssh client used throughout the world.ĭownload and install the file in a location of your choice, then open it. Windows doesn’t come with a built‑in terminal, so you need to download one from the Internet. Type terminal in the pop‑up box and press Enter. On Macs, you can use the built‑in terminal tool to do everything in this tutorial.Ĭlick the magnifying glass icon at the right end of the top bar on the screen. If you prefer to use your own local terminal to set up NGINX or NGINX Plus and serve web content, feel free to skip to Setting up AWS. Macs have a built‑in terminal, but Windows users need to download PuTTY or an equivalent tool. The tutorial includes instructions for these tasks:įor this tutorial, you need a terminal to connect to your Amazon Elastic Compute Cloud (EC2) instance. The course also readies you for our other instructor‑led and self‑paced courses on advanced topics. Once you complete the steps given here, you may want to continue with NGINX Core training ( instructor‑led or on‑demand), a full‑day course where you’ll learn how to configure, administer, and manage NGINX. It covers both NGINX and NGINX Plus, the commercially supported version with additional enterprise‑grade features. This blog post guides you in getting NGINX up and running on Ubuntu 20.04 on Amazon Web Services (AWS) in an easy-to-use setup that doesn’t affect the settings on your personal computer. In this case we think it’s smart to follow the crowd and use NGINX for all your web‑serving needs, and additionally to take advantage of its capabilities as a reverse proxy, content cache, load balancer, API gateway, and more. Since its introduction more than 15 years ago, NGINX has gained steadily in popularity and is now the most popular web server in the world, powering more than 350 million websites.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |