> ## Documentation Index
> Fetch the complete documentation index at: https://link.datarelay.run/llms.txt
> Use this file to discover all available pages before exploring further.
# OCI Network and VM
> Create the OCI network, Ubuntu VM, and Reserved Public IPv4 for a DataRelay Link server.
# Part I — Build the OCI network and VM
## 1. Open Virtual Cloud Networks
From the OCI Home page, enter **Networking → Virtual Cloud Networks**. The image below is the **original Picture 1** from the field-deployment Word guide; it is used without conversion or downscaling.
## 2. Create the VCN, Internet Gateway, route, subnet, and ingress rules
Use these values:
```text theme={null}
VCN name data-relay-vcn
VCN IPv4 CIDR 10.0.0.0/16
Internet Gateway data-relay-internet-gateway
Default route 0.0.0.0/0 -> Internet Gateway
Public subnet data-relay-public-subnet
Public subnet CIDR 10.0.0.0/24
Subnet type Regional / Public
```
### 2-1. Create the VCN
Open **Virtual Cloud Networks → Create VCN**.
Set the VCN name to `data-relay-vcn` and the IPv4 CIDR to `10.0.0.0/16`.
### 2-2. Create the Internet Gateway
In the new `data-relay-vcn`, open the **Gateways** tab and create an Internet Gateway.
Use `data-relay-internet-gateway` as the example gateway name.
### 2-3. Add the Internet route to the default route table
Open the **Routing** tab and select `Default Route Table for data-relay-vcn`.
Choose **Route Rules → Add Route Rules**.
Add the following route:
```text theme={null}
Target Type Internet Gateway
Destination CIDR 0.0.0.0/0
Target data-relay-internet-gateway
```
Confirm that the route rule is present after saving.
### 2-4. Start creating the public subnet
Open the **Subnets** tab and select **Create Subnet**.
### 2-5. Configure the public subnet
Create the public subnet with the following values:
```text theme={null}
Name data-relay-public-subnet
Subnet Type Regional
IPv4 CIDR 10.0.0.0/24
Route Table Default Route Table for data-relay-vcn
Subnet Access Public Subnet
```
### 2-6. Configure the Security List
Open the VCN's **Security Lists** page.
Review the ingress rules on the **Default Security List**.
For DataRelay Link in single-443 mode, add TCP 443 and the Remote Service endpoint pool TCP 6000-6098. Keep SSH 22 for administration, preferably restricted to your administrator public IP `/32`.
Confirm that the ingress rules were applied.
### Recommended single-443 ingress
| Protocol | Destination port | Source | Purpose |
| -------- | ---------------: | ------------------------------------------ | ----------------------------------- |
| TCP | 22 | **your admin public IP/32** | SSH administration |
| TCP | 443 | client networks or `0.0.0.0/0` if required | WSS control + enrollment/management |
| TCP | 6000-6098 | only networks/users that need the services | Remote Services |
In **single-443** mode, do not create public OCI ingress or DNAT for **6099** or **7000**. They are internal loopback backends. Also do not blindly copy a broad `All Protocols` rule from a generic OCI tutorial.
If you do not want the whole `6000-6098` range exposed, allow only the service ports that are actually assigned, and constrain source CIDRs where possible.
## 3. Create the Ubuntu compute instance
Recommended values for this walkthrough:
```text theme={null}
Name data-relay-link-server
Image Canonical Ubuntu 24.04 LTS x86_64
Shape VM.Standard.E2.1.Micro (when Console marks it eligible/free)
VCN data-relay-vcn
Subnet data-relay-public-subnet
Boot volume default
```
Before creating the Compute Instance, confirm that the VCN, Internet Gateway, route, public subnet, and Security List created above are ready, then open **Compute → Instances**.
### 3-1. Enter the basic Compute Instance settings
Start on **Create compute instance** and confirm the instance name and placement.
### 3-2. Select Canonical Ubuntu 24.04
Choose **Change image** and select Canonical Ubuntu 24.04. Treat the image/version currently shown in OCI Console as authoritative.
Unless your environment requires something different, keep the Security settings at their defaults.
### 3-3. Select the VCN and public subnet
Under Primary VNIC, select the `data-relay-vcn` and `data-relay-public-subnet` created earlier.
### 3-4. Disable automatic public IPv4 and configure the SSH key
Because this guide attaches a Reserved Public IP later, turn off **Automatically assign public IPv4 address**. Then upload an existing SSH public key or let OCI generate a new key pair, and store the private key securely.
### 3-5. Review the boot volume
Unless you have a separate storage requirement, keep the boot-volume settings at their defaults.
### 3-6. Review before creating the instance
Confirm that the image is Ubuntu 24.04 and that the shape, VCN/subnet, and SSH key match the intended configuration before creating the instance.
### 3-7. Confirm the created instance and Free/Eligible indicator
Confirm the instance state in the Compute Instances list.
The **Always Free** indicator shown in the original screenshot reflects the OCI Console at the time of the field deployment. Current Free Tier/Eligible status can vary by region and tenancy, so use the current Console's eligibility and cost display as the final authority.
Important points from the original deployment:
* choose the existing `data-relay-vcn`
* choose `data-relay-public-subnet`
* allow OCI to assign the **private IPv4** automatically
* turn off **Automatically assign public IPv4 address** for the final persistent-IP design
* generate/download or upload an SSH public key
* if OCI generated the key pair, store the private key securely; do not assume it can be downloaded again later
* keep the boot volume simple unless you have another storage requirement
`VM.Standard.E2.1.Micro` availability and Free Tier treatment are tenancy/region dependent. If the Console does not show it as eligible at creation time, do not assume this guide makes it free.
## 4. Attach a Reserved Public IPv4
From the instance details page, open **Networking → Primary VNIC**.
In the VNIC, open **IP administration → Primary Private IP**.
If an ephemeral public IP is currently attached, edit the private IP and select **No public IP** first.
Confirm that no public IP is currently assigned.
Edit the private IP again and choose:
```text theme={null}
Public IP type Reserved public IP
Option Create new Reserved IP Address
Name data-relay-reserved-public-ip
```
A Reserved Public IP is the address you should treat as the persistent public entry point for DataRelay Link. OCI performs the public/private mapping outside the Ubuntu guest, so `ip addr` on the VM normally shows the private `10.x.x.x` address rather than the public address.
Confirm that the Reserved Public IP is attached to the Primary Private IP. The public IP value in this screenshot has been masked before publication.
Picture 32 (successful SSH session) from the original Word guide is still not published because it contains field connection details. The SSH procedure below uses the `` placeholder instead.
## 5. Test SSH access
For OCI Ubuntu images the default account is normally `ubuntu`:
```bash theme={null}
chmod 600 ~/Downloads/
ssh -i ~/Downloads/ ubuntu@
```
Then verify the host:
```bash theme={null}
uname -m
cat /etc/os-release
systemctl --version
```
Expected for this guide:
```text theme={null}
Architecture x86_64
OS Ubuntu 24.04 LTS
PID 1 systemd
```