# Quickstart

Bare Metal GPUs servers are dedicated, single-tenant servers with 8 NVIDIA H100/H200 GPUs that can operate standalone or in multi-node clusters.

### Sign Up for an Account <a href="#contentify_0" id="contentify_0"></a>

1. Access <https://id.fptcloud.com/> and choose **Sign up**.
2. Please check your **Junk** email folder if you don't see the confirmation email in your **Inbox**.
3. Sign in to <https://console.fptcloud.com/> to start using the Metal Cloud service.

### Create a Subnet <a href="#contentify_1" id="contentify_1"></a>

A subnet is required to create and deploy your Bare Metal GPU server.

1. Click on **AI Infrastructure** and select **Subnet** in the Sidemenu.
2. Follow the detailed guide [here](https://fptcloud.com/en/documents/metal-cloud/?doc=subnet).

### Create Bare Metal GPU Servers <a href="#contentify_2" id="contentify_2"></a>

1. Click on **AI Infrastructure** and select **Metal Cloud** in the Sidemenu.
2. Choose **Create server** and configure the server deployment.
3. Two (02) FPT images for GPU and AI/ML are available; check the software dependencies [here](https://fptcloud.com/en/documents/metal-cloud/?doc=os-image).
4. You may select a **Floating IP (Public IP)** while creating the server to access it via the internet, or attach it later in the **Network/Floating IP**.
5. Follow the detailed guide [here](https://fptcloud.com/en/documents/metal-cloud/?doc=create-server).

### Access to Servers <a href="#contentify_3" id="contentify_3"></a>

1. **Attach a Floating IP** if you have not chosen it while creating servers with this [guide](/fpt-gpu-cloud/metal-cloud/tutorials/server-action.md)**.**
2. Configure **Network ACL** [here](https://fptcloud.com/en/documents/metal-cloud/?doc=network-acl) to create an inbound rule that allows your Public IPs.
3. SSH into the server with your SSH key or password as configured during creation.
4. You can also set a **Jump host** for additional security settings. Follow the guide [here](https://fptcloud.com/en/documents/metal-cloud/?doc=access-server).

\*The default username is **`clouduser` .**

### Notices <a href="#contentify_4" id="contentify_4"></a>

* Please check the **Tenant & Region** after accessing the FPT Cloud Console. AI Factory is only supported in the **Hanoi 2** (Vietnam) and **Tokyo** (Japan) regions.
* You may change the default **Network ACL**, but ensure to set up other required rules for creating servers.\
  Here is the default outbound rule for a Network ACL, which you can delete.

| Priority | Type | Protocol | Port | Destination | Traffic Action |
| -------- | ---- | -------- | ---- | ----------- | -------------- |
| 100      | ALL  | ALL      | ALL  | 0.0.0.0/0   | ALLOW          |

If you delete the above default rule, you need to add the following outbound rules to create and deploy the server:

| Priority | Type      | Protocol | Port | Source    | Traffic Action |
| -------- | --------- | -------- | ---- | --------- | -------------- |
| 1        | HTTP      | TCP      | 80   | 0.0.0.0/0 | ALLOW          |
| 2        | HTTPS     | TCP      | 443  | 0.0.0.0/0 | ALLOW          |
| 3        | DNS (UDP) | UDP      | 53   | 0.0.0.0/0 | ALLOW          |

* FPT sets the **limitation (quota) for resource** quantity according to your contracts/agreements. If you run out of resources, you cannot create new ones. Please contact your salesman or reach out to [FPT Smart Cloud Support](https://support.fptcloud.com/en/support/tickets/new).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ai-docs.fptcloud.com/fpt-gpu-cloud/metal-cloud/quickstart.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.