Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[doc] Improved procedure to create and configure a virtual server on AWS. #243

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
43 changes: 31 additions & 12 deletions getting-started/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,29 +18,48 @@ Before moving forward, it's important to familiarize yourself with two key eleme
:::{tab-item} AWS
:sync: AWS

1. Navigate to [AWS console](https://console.aws.amazon.com/console/home) – Search EC2 in the search bar and select it. Click the "Launch Instance" button highlighted in orange.
**Step 1: Create Your Virtual Server**

2. Provide a name to the VM.
1. Open the [AWS console](https://console.aws.amazon.com/console/home) and search for **EC2** in the search bar.

3. In Quick Start, select the base OS as Ubuntu (`ami-id : ami-04dd23e62ed049936`).
2. Select **Launch instance** to start creating a virtual server.

4. Select an Instance type that is based on Intel hardware.
3. Under **Name and tags**, name your virtual server in the **Name** field.

4. Under **Quick Start**, choose Ubuntu (`ami-id : ami-04dd23e62ed049936`) as the base OS.

5. In **Instance type**, select an instance for your Intel processor.

>**Note**: We recommend `m7i.4xlarge` or larger instance for an Intel® 4th Gen Xeon© Scalable Processor. For more information on virtual servers on AWS, visit the [AWS and Intel page](https://aws.amazon.com/intel/).

6. Create a new key pair for SSH access by naming it, or select an existing key pair from the dropdown list.

7. Under **Network Settings**:

- Choose an existing security group, or
- Select **Create security group** and enable **Allow SSH traffic** and **Allow HTTP traffic**.

8. In **Storage**, set the size to 100 GiB.

9. Select **Launch instance** to launch your virtual server. A **Success** banner confirms the launch.

>**Note**: We recommend selecting a `m7i.4xlarge` or larger instance with an Intel(R) 4th Gen Xeon(C) Scalable Processor. For more information on virtual servers on AWS visit [here](https://aws.amazon.com/intel/).
**Step 2: Connect and Configure Your Virtual Server**

5. Next, create a new key pair, give it a name or select one from the existing key pairs.
1. Select **Connect**, and connect using your preferred connection method.

6. Under Network settings select an existing security group. If there is none, create a new one by selecting the Create security group radio button and select the Allow SSH traffic and Allow HTTP traffic check box.
2. Search for **Security Groups** in the search bar and select the security group used when creating the instance.

7. Configure the storage to 100 GiB and click "Launch Instance".
3. Select **Edit inbound rules** on the right side of the window.

8. Click on the "connect" button on the top right and connect using your preferred method.
4. To add a rule, select **Add rule** and enter the following:

9. Look up Security Groups in the search bar and select the security group used when creating the instance.
- Type: Custom TCP
- Port Range: 80
- Source: 0.0.0.0/0

10. Click on the Edit inbound rules on the right side of the window.
>**Note**: To learn more, see [editing inbound or outbound rules](https://docs.aws.amazon.com/finspace/latest/userguide/step5-config-inbound-rule.html) from AWS documentation.

11. Select Add rule at the bottom, and create a rule with type as Custom TCP , port range as 80 and source as 0.0.0.0/0 . Learn more about [editing inbound/outbound rules](https://docs.aws.amazon.com/finspace/latest/userguide/step5-config-inbound-rule.html)
5. Select **Save rules** to commit your changes.

:::
:::{tab-item} Azure
Expand Down