Learning Hub · Enterprise architecture

Oracle Cloud enterprise architecture

A 14-day educational path for OCI as an enterprise estate: identity, VCN, Bastion, Linux VMs, storage, and restore — not Kubernetes first.

Community learning track · not a commercial training product

This path sits beside Windows Server, Linux, and Networking. Treat Oracle Cloud Infrastructure (OCI) like Linux + networking with an IAM control plane. Cert goal after the labs: Foundations Associate, then Architect Associate.

Use an Always Free tenancy. Plan on 1–2 hours most days for two weeks. Do not practice on a production tenancy — including anything that serves this website.

14 days

Enterprise architecture track (Always Free)

1–2 hrs

Lab time most days

VCN first

Networking before fancy services

Linux VM

Bastion + private Compute is the core drill

Path into the enterprise architecture track

Start with foundations if cloud IAM and VCNs are new. Skip ahead only if you already reach private Linux hosts through a Bastion without guessing.

Foundations — cloud architecture mindset

Before the 14-day labs: treat OCI like Linux + networking with an IAM control plane.

  • Regions, ADs, compartments, and tagging
  • IAM users, groups, policies (least privilege)
  • VCN vs classic “flat LAN” thinking
  • Public vs private path: IGW, NAT, Bastion
  • SSH keys and never leaving root open from 0.0.0.0/0

Create the Always Free tenancy, set compartments, and sketch your first VCN on paper.

Enterprise architecture (this program)

Design and operate OCI layers — identity, network, compute, storage, edge — the way an enterprise cloud estate would, at Always Free scale.

  • Private Linux VM reached only via Bastion
  • Block Volume attach, mount, fstab, snapshot/restore
  • Object Storage for off-host copies
  • Monitoring + alarms + a written runbook
  • Simple Load Balancer in front of two VMs

Finish the 14-day sequence with a diagram, addressing table, and a restore drill you actually ran.

What comes after

After this path: certs and deeper architecture — skip Kubernetes until networking and recoverability feel natural.

  • OCI Foundations Associate (1Z0-1085)
  • OCI Architect Associate (1Z0-1072) — main architecture track
  • Optional later: Operations Associate, OKE, Terraform
  • Pair with Linux and Networking Learning Hub tracks

Sit Foundations after day 14; start Architect Associate labs while repeating Bastion + restore drills.

Reference layers

Enterprise OCI architecture is layered. The lab proves each layer at Always Free scale — it does not pretend one public VM is a full production estate.

LayerWhat production looks likeWhat the lab can prove
IdentityTenancy, compartments, IAM groups and policiesSeparate network / compute / shared compartments; least-privilege policies
NetworkVCN, public/private subnets, IGW, NAT, route tables, NSGsOne VCN; Bastion into private subnet; no public IP on private hosts
ComputeLinux VMs, shapes, cloud-init, SSH keys, secondary VNICsOracle Linux or Ubuntu VM; harden SSH; document access path
StorageBlock Volume, boot volume backups, Object StorageAttach and mount a volume; snapshot; restore drill
Edge / HALoad Balancer, dual backends, health checksTwo small web VMs behind one LB (even Always Free shapes)
OpsMonitoring, alarms, Logging, runbooksCPU/disk alarm + one-page restore and “can’t SSH” runbook

Fourteen days

Path and IAM first, then a lab that matches the diagram. Day 14 ends with a runbook and a restore you actually ran — not a slide recap.

  1. Days 1–3

    Identity and layout

    Tenancy layout, compartments, IAM groups/policies, tags. Separate network / compute / shared.

  2. Days 4–7

    Networking core

    VCN with public + private subnets, IGW, NAT, routes, NSGs. Bastion into a private Linux VM.

  3. Days 8–10

    Compute admin

    SSH keys, cloud-init, firewalld/ufw, Block Volume mount + fstab, snapshots, resize / secondary VNIC.

  4. Days 11–12

    Storage and recovery

    Object Storage + lifecycle. Backup/restore a volume. Disaster drill: replace a VM from backup.

  5. Days 13–14

    Operate and document

    Monitoring + alarms, Logging. Load Balancer in front of two web VMs. Diagram + access/backup/restore runbook.

Minimum honest lab

Compartments, a real VCN, Bastion into private Compute, storage you can restore, and a diagram. Green console tiles without a path draw do not count.

PieceRole
AccountOracle Cloud Always Free tenancy (practice only — not production)
Compartmentsnetwork, compute, shared (or equivalent clear split)
VCNPublic + private subnet, IGW, NAT Gateway, route tables, NSGs
AccessBastion → private Linux VM (no public IP on private hosts)
StorageOne Block Volume + Object Storage bucket for off-host copies
DocsOne diagram + addressing table + restore runbook

Non-negotiable rules

  • Use Always Free / lab tenancy only — do not practice on a production tenancy.
  • Prefer private subnet + Bastion after day 4; avoid public IPs on private hosts.
  • Draw the path (user → Bastion → VM) before changing NSGs or routes.
  • Every open ingress rule needs an owner and a reason; default deny elsewhere.
  • Capture proof of failure and of the fix — a green console status alone is not enough.
  • Skip OKE, Functions, and deep Terraform until Bastion + restore feel routine.

Starter links

Docs also live in Resources. Pair this with Linux and Networking when you harden guests and debug paths. Bring questions to Community.