Ubuntu VPS na kyauta: daga VM zuwa SSH

Tabbatar da cancanta, sannan ƙirƙiri key

Kana buƙatar asusun Oracle mai izinin ƙirƙirar network da instance, da OpenSSH a kwamfutarka. Duba allowance da aka riga aka yi amfani da shi. Trial credit ba shaida ce cewa paid resource zai kasance kyauta bayan trial ba. Idan babu capacity, dakata; kada ka zaɓi paid shape ba da niyya ba.

A kwamfutarka, ƙirƙiri key kafin launching instance. Yi amfani da sabon filename idan wannan yana nan. Private key ya zauna a kwamfutarka; public key ne kaɗai ake sakawa a panel.

mkdir -p ~/.ssh
chmod 700 ~/.ssh
ssh-keygen -t rsa -b 3072 -f ~/.ssh/oci-ubuntu-free
chmod 600 ~/.ssh/oci-ubuntu-free
cat ~/.ssh/oci-ubuntu-free.pub

User key yana tantance kai ga sabar; host key yana tantance sabar gare ka. Sunayen instance na iya maimaituwa, saboda haka yi amfani da OCID don tabbatar da wace instance kake dubawa.

Ƙirƙiri network na wannan gwajin

Yi dedicated VCN mai 10.20.0.0/16 da regional public subnet mai 10.20.1.0/24. Tabbatar ba su yi karo da network da za a haɗa ba. Ƙara Internet Gateway da route 0.0.0.0/0 zuwa gare shi, kuma tanadi public IP don instance.

A dedicated security list, ba stateful ingress TCP izini daga public IP na kwamfutarka na yanzu da /32, source port All, destination port 22. Kada ka yi amfani da private IP na gida a matsayin source na internet. Idan wannan dedicated list yana da tsohuwar dokar SSH daga koʼina, cire wannan dokar bayan tabbatar da takaitacciyar dokar.

Ƙara dokar /32 ba ya soke wata doka mai faɗi a wani list ko NSG. Kiyaye ICMP da egress da ake buƙata. Misalin ba ya buƙatar NSG, NAT ko load balancer; kada ka goge wani network da sauran ayyuka suke amfani da shi.

Zaɓi image da shape masu cancanta

Zaɓi Ubuntu 24.04 x86 da VM.Standard.E2.1.Micro a home region. Duba cewa panel ya nuna cancanta da quota mai samuwa. Boot volume 50 GB a matakin performance mai cancanta yana shiga allowance 200 GB na boot da block volumes a haɗe; lissafa sauran volumes na asusu.

Saka public SSH key. Domin samun public host fingerprints a farkon boot, saka cloud-init na ƙasa. Wannan yana fitar da public host keys, ba private keys ba.

#cloud-config
ssh:
  emit_keys_to_console: true

Bayan state ya zama Running, rubuta instance OCID, boot volume OCID da public IP. Running kaɗai ba tabbacin cewa guest ya kammala cloud-init ko SSH ya isa daga internet ba.

Tabbatar da host fingerprint daga console mai aminci

A panel, zaɓi ainihin instance ta OCID. Je zuwa Console connection, yi Launch Cloud Shell connection, sannan ka samo Console history na farkon boot. Nemi ɓangaren SSH HOST KEY FINGERPRINTS da matching algorithm da SHA256.

Fingerprint na Console connection resource yana tantance console endpoint. Ba shi ne guest SSH host fingerprint ba. Haka kuma kada ka kwatanta da fingerprint na user key da ka tura.

Idan babu guest fingerprint, yi amfani da hanyar recovery da aka amince da ita domin karanta public host key na guest. Kada ka maye gurbin wannan tantancewa da ssh-keyscan daga network ba tare da wata hujja mai zaman kanta ba.

Haɗa daga kwamfutarka

Sauya IP ɗin misali da public IP na instance, sannan fara SSH daga kwamfutarka:

ssh -o StrictHostKeyChecking=ask -i ~/.ssh/oci-ubuntu-free ubuntu@203.0.113.20

A Ubuntu image, default user shi ne ubuntu, ba opc ba. Kwatanta algorithm da fingerprint kafin karɓa. Idan bai yi daidai ba, dakata ka binciki ainihin instance, IP da console history.

Idan haɗi ya kasa, duba route, public IP, source /32, port da yanayin provisioning. Jagorar matsalar SSH tana bambanta timeout, ƙin haɗi da authentication.

Bincika guest da updates

A cikin sabar, duba cloud-init, release, architecture, memory, disk da SSH listener:

cloud-init status --wait
cat /etc/os-release
dpkg --print-architecture
free -h
df -h /
sudo ss -lntp
sudo iptables -S

Waɗannan gwaje-gwajen shiga da tsarin guest ne. Ba sa tabbatar da HTTP, capacity na manhaja ko load. Jira cloud-init ya kammala kuma binciki kuskurensa kafin updates.

sudo apt update
sudo apt upgrade

Buɗe SSH na biyu kafin rufe na farko. A wannan sabar gwaji da za a iya sake ƙirƙira, gwada reboot da dawowar shiga tare da recovery console a samuwa. Kada ka yi hakan ba tsari a sabar da ke da muhimmin aiki ba.

Bi firewall na Oracle kafin wallafa shafi

Kada ka kunna UFW ko flush iptables a Ubuntu image na Oracle. Kiyaye dokokin da suke da alaƙa da iSCSI boot da block volumes. Don HTTP/HTTPS daga baya, bi takardun Oracle na OCI network da guest firewall.

Bayan tabbatar da shiga, jagorar Nginx da HTTPS tana da reshen Oracle da ke tsallake UFW. Buɗe port a security list kaɗai ba ya warware dokar guest da ta hana shi.

Ajiye abin da ake buƙata, sannan goge na gwaji

Ajiye bayanai da matakan sake gina sabar a wajen instance, kuma gwada restore. Kafin terminate, tabbatar da instance OCID na wannan gwajin da final export. Boot volume na iya kasancewa bayan terminate ta default; goge shi kawai idan ka tabbatar ba a buƙata kuma an tanadi bayanai.

Duba sauran volumes, IPs da backups bisa sharuɗɗan billing. Goge network kawai idan na wannan gwajin ne kuma babu sauran dependencies. Kada ka yi account-wide cleanup. Tabbatar da usage daga baya a jerin binciken kuɗi.

Tambayoyi da amsoshi

Takardu da madogarai

• Madogara: Oracle Always Free resources
• Madogara: Oracle platform images and essential firewall rules
• Madogara: Creating an Oracle Compute instance
• Madogara: Oracle SSH key pairs
• Madogara: Oracle public subnet scenario
• Madogara: Oracle internet gateway routing
• Madogara: Oracle security rules
• Madogara: Oracle console connections and Cloud Shell
• Madogara: Capturing Oracle instance console history
• Madogara: Cloud-init Keys to Console module
• Madogara: Connecting to an OCI Linux instance
• Madogara: Ubuntu 24.04 release notes: Oracle firewall compatibility
• Madogara: Terminating an Oracle instance