Skip to content

Commit 211a13a

Browse files
Further formatting tweaks.
1 parent 758cb79 commit 211a13a

File tree

2 files changed

+20
-21
lines changed
  • content/learning-paths/servers-and-cloud-computing/net-aspire

2 files changed

+20
-21
lines changed

content/learning-paths/servers-and-cloud-computing/net-aspire/aws.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ layout: learningpathall
77
---
88

99
### Objective
10-
In this section, you will learn how to deploy the .NET Aspire application on to an AWS Elastic Compute Cloud (EC2) Virtual Machine powered by Arm-based processors, such as AWS Graviton. This allows you to leverage the cost and performance benefits of Arm architecture while benefiting from the seamless deployment of cloud-native applications on modern infrastructure.
10+
In this section, you will learn how to deploy the .NET Aspire application you created on to an AWS Elastic Compute Cloud (EC2) Virtual Machine powered by Arm-based processors, such as AWS Graviton. This allows you to leverage the cost and performance benefits of Arm architecture while benefiting from the seamless deployment of cloud-native applications on modern infrastructure.
1111

1212
### Set up your AWS EC2 Instance
1313
To set up an Arm-powered EC2 instance, follow these steps:

content/learning-paths/servers-and-cloud-computing/net-aspire/gcp.md

Lines changed: 19 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -7,30 +7,29 @@ layout: learningpathall
77
---
88

99
### Objective
10-
In this section, you will learn how to deploy a .NET Aspire application onto an Arm-based instance running on Google Cloud Platform (GCP).
11-
You will start by creating an instance of an Arm64 virtual machine on GCP. You will then connect to it, install the required software, and run the application.
10+
In this section, you will learn how to deploy the .NET Aspire application you created onto an Arm-based instance running on Google Cloud Platform (GCP). You will start by creating an instance of an Arm64 virtual machine on GCP. You will then connect to it, install the required software, and run the application.
1211

1312
### Create an Arm64 virtual machine
14-
Follow these steps to create an Arm64 VM:
13+
To create an Arm64 VM, follow these steps:
1514
1. Create a Google Cloud Account. If you don’t already have an account, sign up for Google Cloud.
1615
2. Open the Google Cloud Console [here](https://console.cloud.google.com).
17-
3. Navigate to Compute Engine. In the Google Cloud Console, open the Navigation menu and go to Compute Engine > VM Instances. Enable any relevant APIs if prompted.
18-
4. Click Create Instance.
16+
3. Navigate to Compute Engine. In the Google Cloud Console, open the Navigation menu, and go to Compute Engine > VM Instances. Enable any relevant APIs if prompted.
17+
4. Click **Create Instance**.
1918
5. Configure the VM Instance as follows:
20-
* Name: **arm-server**
21-
* Region/Zone: choose a region and zone where Arm64 processors are available, for example us-central1.
22-
* Machine Family: select **General-purpose**.
23-
* Series: T2A.
24-
* Machine Type: select **t2a-standard-1**.
19+
* Name: **arm-server**
20+
* Region/Zone: choose a region and zone where Arm64 processors are available, for example us-central1.
21+
* Machine Family: select **General-purpose**.
22+
* Series: T2A.
23+
* Machine Type: select **t2a-standard-1**.
2524
The configuration setup should resemble the following:
2625

2726
![fig14](figures/14.png)
2827

2928
6. Configure the Remaining Settings:
30-
* Availability Policies: Standard.
31-
* Boot Disk: Click **Change**, then select **Ubuntu** as the operating system.
32-
* Identity and API Access: Keep the default settings.
33-
* Firewall Settings: Check **Allow HTTP traffic** and **Allow HTTPS traffic**.
29+
* Availability Policies: **Standard**.
30+
* Boot Disk: Click **Change**, then select **Ubuntu** as the operating system.
31+
* Identity and API Access: keep the default settings.
32+
* Firewall Settings: Check **Allow HTTP traffic** and **Allow HTTPS traffic**.
3433

3534
![fig15](figures/15.png)
3635

@@ -100,14 +99,14 @@ You will see output similar to this:
10099
To make your application publicly-accessible, configure the firewall rules:
101100
1. In the Google Cloud Console, navigate to **VPC Network** > **Firewall**.
102101
2. Click **Create Firewall Rule** and configure the following:
103-
* Name: allow-dotnet-ports
104-
* Target Tags: dotnet-app
105-
* Source IP Ranges: 0.0.0.0/0 (for public access).
106-
* Protocols and Ports: allow TCP on ports 7133, 7511, and 17222.
107-
* Click the **Create** button.
102+
* Name: allow-dotnet-ports.
103+
* Target Tags: dotnet-app.
104+
* Source IP Ranges: 0.0.0.0/0 (for public access).
105+
* Protocols and Ports: allow TCP on ports 7133, 7511, and 17222.
106+
* Click the **Create** button.
108107
3. Go back to your VM instance.
109108
4. Click **Edit**, and under Networking find Network Tags, add the tag dotnet-app.
110-
5. Click the Save button.
109+
5. Click the **Save** button.
111110

112111
### Summary
113112
You have successfully deployed the Aspire app onto an Arm-powered GCP Virtual Machine. This deployment demonstrates the compatibility of .NET applications with Arm architecture and GCP, offering high performance and cost-efficiency.

0 commit comments

Comments
 (0)