diff --git a/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/_index.md b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/_index.md new file mode 100644 index 0000000000..c66dd30e0b --- /dev/null +++ b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/_index.md @@ -0,0 +1,61 @@ +--- +title: Deploy NGINX on the Microsoft Azure Cobalt 100 processors + +draft: true +cascade: + draft: true + +minutes_to_complete: 30 + +who_is_this_for: This Learning Path introduces NGINX deployment on Microsoft Azure Cobalt 100 (Arm-based) virtual machine. It is intended for system administrators and developers looking to deploy and benchmark NGINX on Arm architecture with minimal adjustments from traditional x86_64 environments. + +learning_objectives: + - Start an Azure Arm64 virtual machine using the Azure console and Ubuntu Pro 24.04 LTS as the base image. + - Deploy the NGINX web server on the Azure Arm64 virtual machine running Ubuntu Pro 24.04 LTS. + - Configure and test a static website using NGINX on the virtual machine. + - Perform baseline testing and benchmarking of NGINX in the Ubuntu Pro 24.04 LTS Arm64 virtual machine environment. + + +prerequisites: + - A [Microsoft Azure](https://azure.microsoft.com/) account with access to Cobalt 100 based instances (Dpsv6). + - Familiarity with the [NGINX architecture](https://www.nginx.com/) and deployment practices on Arm64 platforms. + - Network settings (firewalls and security groups) should allow inbound communication on ports 22 (SSH) and 80 (HTTP). + +author: Jason Andrews + +### Tags +skilllevels: Advanced +subjects: Web +cloud_service_providers: Microsoft Azure + +armips: + - Neoverse + +tools_software_languages: + - NGINX + - Apache Bench + +operatingsystems: + - Linux + +further_reading: + - resource: + title: NGINX official documentation + link: https://nginx.org/en/docs/ + type: documentation + - resource: + title: Apache Bench official documentation + link: https://httpd.apache.org/docs/2.4/programs/ab.html + type: documentation + - resource: + title: NGINX on Azure + link: https://docs.nginx.com/nginx/deployment-guides/microsoft-azure/virtual-machines-for-nginx/ + type: documentation + + +### FIXED, DO NOT MODIFY +# ================================================================================ +weight: 1 # _index.md always has weight of 1 to order correctly +layout: "learningpathall" # All files under learning paths have this same wrapper +learning_path_main_page: "yes" # This should be surfaced when looking for related content. Only set for _index.md of learning path content. +--- diff --git a/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/_next-steps.md b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/_next-steps.md new file mode 100644 index 0000000000..c3db0de5a2 --- /dev/null +++ b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/_next-steps.md @@ -0,0 +1,8 @@ +--- +# ================================================================================ +# FIXED, DO NOT MODIFY THIS FILE +# ================================================================================ +weight: 21 # Set to always be larger than the content in this path to be at the end of the navigation. +title: "Next Steps" # Always the same, html page title. +layout: "learningpathall" # All files under learning paths have this same wrapper for Hugo processing. +--- diff --git a/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/backgroud.md b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/backgroud.md new file mode 100644 index 0000000000..9363127800 --- /dev/null +++ b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/backgroud.md @@ -0,0 +1,22 @@ +--- +title: "Overview" + +weight: 2 + +layout: "learningpathall" +--- + +## Cobalt 100 Arm-based processor + +Azure’s Cobalt 100 is built on Microsoft's first-generation, in-house Arm-based processor: the Cobalt 100. Designed entirely by Microsoft and based on Arm’s Neoverse N2 architecture, this 64-bit CPU delivers improved performance and energy efficiency across a broad spectrum of cloud-native, scale-out Linux workloads. These include web and application servers, data analytics, open-source databases, caching systems, and more. Running at 3.4 GHz, the Cobalt 100 processor allocates a dedicated physical core for each vCPU, ensuring consistent and predictable performance. + +To learn more about Cobalt 100, refer to the blog [Announcing the preview of new Azure virtual machine based on the Azure Cobalt 100 processor](https://techcommunity.microsoft.com/blog/azurecompute/announcing-the-preview-of-new-azure-vms-based-on-the-azure-cobalt-100-processor/4146353). + +## NGINX + +NGINX is a high-performance, open-source web server, reverse proxy, load balancer, and HTTP cache. Originally developed by Igor Sysoev, NGINX is known for its event-driven, asynchronous architecture, which enables it to handle high concurrency with low resource usage. + +There are three main variants of NGINX: +- **NGINX Open Source**– Free and [open-source version available at nginx.org](https://nginx.org) +- **NGINX Plus**- [Commercial edition of NGINX](https://www.nginx.com/products/nginx/) with features like dynamic reconfig, active health checks, and monitoring. +- **NGINX Unit**- A lightweight, dynamic application server that complements NGINX. [Learn more at unit.nginx.org](https://unit.nginx.org/). diff --git a/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/baseline.md b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/baseline.md new file mode 100644 index 0000000000..60cbf26c3a --- /dev/null +++ b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/baseline.md @@ -0,0 +1,129 @@ +--- +title: NGINX Baseline Testing +weight: 5 + +### FIXED, DO NOT MODIFY +layout: learningpathall +--- + + +### Baseline testing with a static website on NGINX +Perform baseline testing of NGINX on an **Ubuntu Pro 24.04 LTS** virtual machine by deploying a custom static HTML page. This verifies that NGINX is correctly serving content on the Arm64 platform. + +1. Create a Static Website Directory: + +Prepare a folder to host your HTML content. +```console +mkdir -p ~/my-static-site +``` +2. Create an HTML file and Web page: + +Create a HTML file `nano my-static-site/index.html` with the content below to design a visually appealing static landing page. + +```html + + + + + Welcome to NGINX on Azure Ubuntu Pro + + + +
+

Welcome to NGINX on Azure Ubuntu Pro 24.04 LTS!

+

Your static site is running beautifully on ARM64

+
+ + +``` +3. Move the Website to NGINX's Accessible Directory: + +Since NGINX runs under the `www-data` user and may not have access to files inside `/home/ubuntu`, move the site to a directory where NGINX has permissions by default: + +```console +sudo mkdir -p /var/www/my-static-site +sudo cp -r ~/my-static-site/* /var/www/my-static-site/ +sudo chown -R www-data:www-data /var/www/my-static-site +``` + +4. Create NGINX Config File to Serve Static Website: + +Point NGINX to serve your static HTML content. +```console +sudo nano /etc/nginx/conf.d/static-site.conf +``` +Now, add the following configuration: + +```NGINX +server { + listen 80; + server_name localhost; + + location / { + root /var/www/my-static-site; + index index.html; + } + + access_log /var/log/nginx/static-access.log; + error_log /var/log/nginx/static-error.log; +} +``` +Make sure `/home/ubuntu/my-static-site` is the correct path to your **index.html**. + +5. Test the NGINX Configuration: + +```console +sudo nginx -t +``` +You should see an output similar to: +```output +nginx: the configuration file /etc/nginx/nginx.conf syntax is ok +nginx: configuration file /etc/nginx/nginx.conf test is successful +``` + +6. Reload or Restart NGINX: + +Apply configuration changes and restart the web server. +```console +sudo nginx -s reload +sudo systemctl restart nginx +``` + +7. Test the Static Website on browser: + +Access your website at your public IP on port 80. +```console +http:/// +``` +Make sure port 80 is open in your Azure Network Security Group (NSG). + +8. You should see the NGINX welcome page confirming a successful deployment: + +![Static Website Screenshot](images/nginx-web.png) + +This verifies the basic functionality of NGINX installation before proceeding to the benchmarking. diff --git a/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/benchmarking.md b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/benchmarking.md new file mode 100644 index 0000000000..67e2ed327d --- /dev/null +++ b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/benchmarking.md @@ -0,0 +1,178 @@ +--- +title: NGINX Benchmarking +weight: 6 + +### FIXED, DO NOT MODIFY +layout: learningpathall +--- + +## NGINX Benchmarking by ApacheBench + +**ApacheBench (ab)** is a lightweight command-line tool for benchmarking HTTP servers. It measures performance metrics like requests per second, response time, and throughput under concurrent load. + + +1. Install ApacheBench + +On **Ubuntu Pro 24.04 LTS**, ApacheBench is available as part of the `apache2-utils` package: +```console +sudo apt update +sudo apt install apache2-utils -y +``` + +2. Verify Installation + +```console +ab -V +``` +You should see an output similar to: + +```output +This is ApacheBench, Version 2.3 <$Revision: 1923142 $> +Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ +Licensed to The Apache Software Foundation, http://www.apache.org/ +``` + +3. Basic Benchmark Command Syntax + +```console +ab -n -c +``` +Example: + +```console +ab -n 1000 -c 50 http://localhost/ +``` +This sends **1000 total requests** with **50 concurrent connections** to `http://localhost/`. + +You should see an output similar to: +```output +This is ApacheBench, Version 2.3 <$Revision: 1903618 $> +Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ +Licensed to The Apache Software Foundation, http://www.apache.org/ + +Benchmarking localhost (be patient) +Completed 100 requests +Completed 200 requests +Completed 300 requests +Completed 400 requests +Completed 500 requests +Completed 600 requests +Completed 700 requests +Completed 800 requests +Completed 900 requests +Completed 1000 requests +Finished 1000 requests + + +Server Software: nginx/1.24.0 +Server Hostname: localhost +Server Port: 80 + +Document Path: / +Document Length: 890 bytes + +Concurrency Level: 50 +Time taken for tests: 0.032 seconds +Complete requests: 1000 +Failed requests: 0 +Total transferred: 1132000 bytes +HTML transferred: 890000 bytes +Requests per second: 31523.86 [#/sec] (mean) +Time per request: 1.586 [ms] (mean) +Time per request: 0.032 [ms] (mean, across all concurrent requests) +Transfer rate: 34848.65 [Kbytes/sec] received + +Connection Times (ms) + min mean[+/-sd] median max +Connect: 0 1 0.1 1 1 +Processing: 0 1 0.1 1 1 +Waiting: 0 1 0.2 1 1 +Total: 1 2 0.1 2 2 + +Percentage of the requests served within a certain time (ms) + 50% 2 + 66% 2 + 75% 2 + 80% 2 + 90% 2 + 95% 2 + 98% 2 + 99% 2 + 100% 2 (longest request) +``` + +### Benchmark Results Table Explained: + +- **Requests per second** – How many requests were served per second. +- **Time per request** – Average latency per request. +- **Transfer rate** – Data throughput. +- **Connection times** – Breakdown of min/mean/max connect, processing, and total times. +- **Percentage served** – Percentile distribution of response times. + +### Benchmark summary on x86_64: +Here is a summary of the benchmark results collected on x86_64 **D4s_v6 Ubuntu Pro 24.04 LTS virtual machine**. + +| **Category** | **Metric** | **Value** | +|---------------------------|-------------------------------------------------|-------------------------------| +| **General Info** | Server Software | nginx/1.24.0 | +| | Server Hostname | localhost | +| | Server Port | 80 | +| | Document Path | / | +| | Document Length | 615 bytes | +| **Test Setup** | Concurrency Level | 50 | +| | Time Taken for Tests | 0.038 sec | +| | Complete Requests | 1000 | +| | Failed Requests | 0 | +| **Transfer Stats** | Total Transferred | 857,000 bytes | +| | HTML Transferred | 615,000 bytes | +| | Requests per Second | 26,592.21 [#/sec] | +| | Time per Request (mean) | 1.880 ms | +| | Time per Request (across all) | 0.038 ms | +| | Transfer Rate | 22,255.39 KB/sec | +| **Connection Times (ms)** | Connect (min / mean / stdev / median / max) | 0 / 1 / 0.2 / 1 / 1 | +| | Processing (min / mean / stdev / median / max) | 0 / 1 / 0.2 / 1 / 2 | +| | Waiting (min / mean / stdev / median / max) | 0 / 1 / 0.2 / 1 / 1 | +| | Total (min / mean / stdev / median / max) | 1 / 2 / 0.2 / 2 / 2 | +| **Latency Percentiles** | 50% of requests served within | 2 ms | +| | 66% of requests served within | 2 ms | +| | 75% of requests served within | 2 ms | +| | 80% of requests served within | 2 ms | +| | 90% of requests served within | 2 ms | +| | 95% of requests served within | 2 ms | +| | 98% of requests served within | 2 ms + +### Benchmark summary on Arm64: +Here is a summary of benchmark results collected on an Arm64 **D4ps_v6 Ubuntu Pro 24.04 LTS virtual machine**. + +| **Category** | **Metric** | **Value** | +|---------------------------|-------------------------------------------------|-------------------------------| +| **General Info** | Server Software | nginx/1.24.0 | +| | Server Hostname | localhost | +| | Server Port | 80 | +| | Document Path | / | +| | Document Length | 890 bytes | +| **Test Setup** | Concurrency Level | 50 | +| | Time Taken for Tests | 0.032 sec | +| | Complete Requests | 1000 | +| | Failed Requests | 0 | +| **Transfer Stats** | Total Transferred | 1,132,000 bytes | +| | HTML Transferred | 890,000 bytes | +| | Requests per Second | 31,523.86 [#/sec] | +| | Time per Request (mean) | 1.586 ms | +| | Time per Request (across all) | 0.032 ms | +| | Transfer Rate | 34,848.65 KB/sec | +| **Connection Times (ms)** | Connect (min / mean / stdev / median / max) | 0 / 1 / 0.1 / 1 / 1 | +| | Processing (min / mean / stdev / median / max) | 0 / 1 / 0.1 / 1 / 1 | +| | Waiting (min / mean / stdev / median / max) | 0 / 1 / 0.2 / 1 / 1 | +| | Total (min / mean / stdev / median / max) | 1 / 2 / 0.1 / 2 / 2 | + +### Highlights from Ubuntu Pro 24.04 LTS Arm64 Benchmarking + +When comparing the results on Arm64 vs x86_64 virtual machines: + +- Achieved **31,523.86 requests/sec**, demonstrating high throughput under concurrent load. +- Response time per request averaged **1.586 ms**, indicating efficient handling of requests with minimal delay. +- **Zero failed requests**, confirming stability and reliability during testing. +- Consistently low **connection and processing times** (mean ≈ 1 ms), ensuring smooth performance. + +You have now benchmarked NGINX on an Azure Cobalt 100 Arm64 virtual machine and compared results with x86_64. diff --git a/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/deploy.md b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/deploy.md new file mode 100644 index 0000000000..5f356361dc --- /dev/null +++ b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/deploy.md @@ -0,0 +1,127 @@ +--- +title: Install NGINX +weight: 4 + +### FIXED, DO NOT MODIFY +layout: learningpathall +--- + + + +## NGINX Installation on Ubuntu Pro 24.04 LTS + +Install NGINX using `apt` on your Ubuntu Pro 24.04 LTS virtual machine, start the NGINX service, and allow **HTTP** traffic through the firewall. Then access the default welcome page using your virtual machine’s public IP address in a browser. + +### Install NGINX + +```console +sudo apt update +sudo apt install -y nginx +sudo systemctl enable nginx +sudo systemctl start nginx +``` + +### Verify NGINX + +```console +sudo systemctl status nginx +``` +You should see an output similar to: + +```output +● nginx.service - A high performance web server and a reverse proxy server + Loaded: loaded (/usr/lib/systemd/system/nginx.service; enabled; preset: enabled) + Active: active (running) since Mon 2025-09-08 04:26:39 UTC; 20s ago + Docs: man:nginx(8) + Main PID: 1940 (nginx) + Tasks: 5 (limit: 19099) + Memory: 3.6M (peak: 8.1M) + CPU: 23ms + CGroup: /system.slice/nginx.service + ├─1940 "nginx: master process /usr/sbin/nginx -g daemon on; master_process on;" + ├─1942 "nginx: worker process" + ├─1943 "nginx: worker process" + ├─1944 "nginx: worker process" + └─1945 "nginx: worker process" +``` +Also, you can use the below command to see the installed version of NGINX: + +```console +nginx -v +``` +{{% notice Note %}} +There is an [Arm community blog](https://community.arm.com/arm-community-blogs/b/servers-and-cloud-computing-blog/posts/improve-nginx-performance-up-to-32-by-deploying-on-alibaba-cloud-yitian-710-instances) that shows that NGINX version 1.20.1 deployed on Yitian 710 based ECS provides up to 32% more throughput in compared to the equivalent x86 based ECS instances. + +The [Arm Ecosystem Dashboard](https://developer.arm.com/ecosystem-dashboard/) recommends NGINX version 1.20.1 as the minimum recommended on the Arm platforms. +{{% /notice %}} + +### Validation with curl +Validation with `curl` confirms that NGINX is correctly installed, running, and serving **HTTP** responses. + +Run the following command to send a HEAD request to the local NGINX server: +```console +curl -I http://localhost/ +``` +The `curl -I http://localhost/` command sends a HEAD request to NGINX to check its **HTTP** response headers without downloading the page content. + +You should see an output similar to: + +```output +HTTP/1.1 200 OK +Server: nginx/1.24.0 (Ubuntu) +Date: Mon, 08 Sep 2025 04:27:20 GMT +Content-Type: text/html +Content-Length: 615 +Last-Modified: Mon, 08 Sep 2025 04:26:39 GMT +Connection: keep-alive +ETag: "68be5aff-267" +Accept-Ranges: bytes +``` + +Output summery: +- **HTTP/1.1 200 OK**: nginx is responding successfully. +- **Server: nginx/1.24.0**: Confirms it's running nginx. +- Confirms your web server is reachable on **localhost**. + +### Allow HTTP Traffic in Firewall(Optional) + +On **Ubuntu Pro 24.04 LTS** virtual machines, **UFW (Uncomplicated Firewall)** is used to manage firewall rules. By default, it allows only SSH (port 22) and blocks most other traffic. + +So even if Azure allows HTTP on port 80 (added to inbound ports during Virtual Machine creation), your Virtual Machine’s firewall may still block it until you run: + +```console +sudo ufw allow 80/tcp +sudo ufw enable +``` +You can verify that HTTP is now allowed with: + +```console +sudo ufw status +``` +You should see an output similar to: +```output +Status: active + +To Action From +-- ------ ---- +8080/tcp ALLOW Anywhere +80/tcp ALLOW Anywhere +8080/tcp (v6) ALLOW Anywhere (v6) +80/tcp (v6) ALLOW Anywhere (v6) +``` + +### Accessing the NGINX Default Page + +You can access the NGINX default page from your Virtual machine’s public IP. Run the following command to display your public URL: + +Now you can access the NGINX default page in a browser. Run the following command to print your Virtual machine’s public URL, then open it in a browser: +```console +echo "http://$(curl -s ifconfig.me)/" +``` + +Open the printed URL in a browser. You should see the NGINX welcome page confirming a successful installation. + +![NGINX](images/nginx-browser.png) + +NGINX installation is complete. You can now proceed with the baseline testing ahead. + diff --git a/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/images/final-vm.png b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/images/final-vm.png new file mode 100644 index 0000000000..5207abfb41 Binary files /dev/null and b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/images/final-vm.png differ diff --git a/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/images/instance.png b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/images/instance.png new file mode 100644 index 0000000000..285cd764a5 Binary files /dev/null and b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/images/instance.png differ diff --git a/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/images/instance1.png b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/images/instance1.png new file mode 100644 index 0000000000..b9d22c352d Binary files /dev/null and b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/images/instance1.png differ diff --git a/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/images/instance4.png b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/images/instance4.png new file mode 100644 index 0000000000..2a0ff1e3b0 Binary files /dev/null and b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/images/instance4.png differ diff --git a/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/images/nginx-browser.png b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/images/nginx-browser.png new file mode 100644 index 0000000000..6a97f1e10b Binary files /dev/null and b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/images/nginx-browser.png differ diff --git a/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/images/nginx-web.png b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/images/nginx-web.png new file mode 100644 index 0000000000..152bf727a6 Binary files /dev/null and b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/images/nginx-web.png differ diff --git a/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/images/ubuntu-pro.png b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/images/ubuntu-pro.png new file mode 100644 index 0000000000..d54bd75ca6 Binary files /dev/null and b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/images/ubuntu-pro.png differ diff --git a/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/instance.md b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/instance.md new file mode 100644 index 0000000000..42f9b2c5dc --- /dev/null +++ b/content/learning-paths/servers-and-cloud-computing/nginx-on-azure/instance.md @@ -0,0 +1,50 @@ +--- +title: Create an Arm based cloud virtual machine using Microsoft Cobalt 100 CPU +weight: 3 + +### FIXED, DO NOT MODIFY +layout: learningpathall +--- + +## Introduction + +There are several ways to create an Arm-based Cobalt 100 virtual machine : the Microsoft Azure console, the Azure CLI tool, or using your choice of IaC (Infrastructure as Code). This guide will use the Azure console to create a virtual machine with Arm-based Cobalt 100 Processor. + +This learning path focuses on the general-purpose virtual machine of the D series. Please read the guide on [Dpsv6 size series](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/general-purpose/dpsv6-series) offered by Microsoft Azure. + +If you have never used the Microsoft Cloud Platform before, please review the microsoft [guide to Create a Linux virtual machine in the Azure portal](https://learn.microsoft.com/en-us/azure/virtual-machines/linux/quick-create-portal?tabs=ubuntu). + +#### Create an Arm-based Azure Virtual Machine + +Creating a virtual machine based on Azure Cobalt 100 is no different from creating any other virtual machine in Azure. To create an Azure virtual machine, launch the Azure portal and navigate to "Virtual Machines". +1. Select "Create", and click on "Virtual Machine" from the drop-down list. +2. Inside the "Basic" tab, fill in the Instance details such as "Virtual machine name" and "Region". +3. Choose the image for your virtual machine (for example, Ubuntu Pro 24.04 LTS) and select “Arm64” as the VM architecture. +4. In the “Size” field, click on “See all sizes” and select the D-Series v6 family of virtual machines. Select “D4ps_v6” from the list. + +![Azure portal VM creation — Azure Cobalt 100 Arm64 virtual machine (D4ps_v6) alt-text#center](images/instance.png "Figure 1: Select the D-Series v6 family of virtual machines") + +5. Select "SSH public key" as an Authentication type. Azure will automatically generate an SSH key pair for you and allow you to store it for future use. It is a fast, simple, and secure way to connect to your virtual machine. +6. Fill in the Administrator username for your VM. +7. Select "Generate new key pair", and select "RSA SSH Format" as the SSH Key Type. RSA could offer better security with keys longer than 3072 bits. Give a Key pair name to your SSH key. +8. In the "Inbound port rules", select HTTP (80) and SSH (22) as the inbound ports. The default port for NGINX when handling standard web traffic (HTTP) is 80. + +![Azure portal VM creation — Azure Cobalt 100 Arm64 virtual machine (D4ps_v6) alt-text#center](images/instance1.png "Figure 2: Allow inbound port rules") + +9. Click on the "Review + Create" tab and review the configuration for your virtual machine. It should look like the following: + +![Azure portal VM creation — Azure Cobalt 100 Arm64 virtual machine (D4ps_v6) alt-text#center](images/ubuntu-pro.png "Figure 3: Review and Create an Azure Cobalt 100 Arm64 VM") + +10. Finally, when you are confident about your selection, click on the "Create" button, and click on the "Download Private key and Create Resources" button. + +![Azure portal VM creation — Azure Cobalt 100 Arm64 virtual machine (D4ps_v6) alt-text#center](images/instance4.png "Figure 4: Download Private key and Create Resources") + +11. Your virtual machine should be ready and running within no time. You can SSH into the virtual machine using the private key, along with the Public IP details. + +![Azure portal VM creation — Azure Cobalt 100 Arm64 virtual machine (D4ps_v6) alt-text#center](images/final-vm.png "Figure 5: VM deployment confirmation in Azure portal") + +{{% notice Note %}} + +To learn more about Arm-based virtual machine in Azure, refer to “Getting Started with Microsoft Azure” in [Get started with Arm-based cloud instances](/learning-paths/servers-and-cloud-computing/csp/azure). + +{{% /notice %}}