Compute Instances
Compute Instances: for operating system control and traditional formats.
A tenancy needs to grow without losing clarity on access, networking, costs and recovery. Add Solution turns workload requirements into a governable, connected OCI architecture prepared for the operational lifecycle.
Tenancy, compartments, IAM, networking, data, protection, costs and operations as one system.

OCI landing zones provide Terraform modules for identity, networking, security, observability and governance. The reference accelerates deployment but must be tailored to the organization, regions and workloads. Compartments organize resources and allow policies, quotas, tags and budgets to be applied within logical scopes. They are not physical boundaries. Protection depends on IAM policies, network design, keys, service configuration and procedures. The landing zone is the start of an operating model, not the completion of the cloud project.
OCI IAM combines identity domains, groups, dynamic groups, compartments and policies. Human users can be federated with the corporate provider. Compatible workloads use dynamic groups and resource principals to reduce static credentials. The architecture separates tenancy, networking, security, database and application administrators. Broad policies in the root compartment are avoided where narrower scopes fulfill the role. Emergency access, rotation, review and auditing are part of the operational lifecycle.
VCNs, subnets, route tables, security lists and NSGs define connectivity. Service Gateway enables private access to supported OCI services; NAT Gateway provides outbound connectivity for private resources; DRG connects VCNs, regions, VPNs and FastConnect according to configuration. FastConnect provides private connectivity through partners or colocation, but end-to-end redundancy requires assessing circuits, locations, CPEs, providers, DRGs and routes. VPN can serve as the primary or contingency path according to capacity and risk. The project validates addressing, DNS, ingress, egress, inspection, asymmetry, limits, latency and transfer costs.
Sizing considers CPU, memory, I/O, networking and burst profiles, shape availability and regional capacity. Benchmark figures are used only with reproducible configurations and conditions.
Compute Instances: for operating system control and traditional formats.
OKE: managed Kubernetes, retaining responsibility for nodes, networking, add-ons, applications and policies.
Functions and Container Instances: for scenarios compatible with their limits and execution model.
Object, Block and File Storage: selected for semantics, performance, lifecycle and recovery.
Load Balancer and Network Load Balancer: selected by protocol, termination and flow requirements.
Base Database Service, Autonomous Database and Exadata Database Service serve distinct scenarios. Compatibility, version, features, licensing, administration, maintenance windows, backup, Data Guard, latency and integration guide the choice. Autonomous Database reduces specific administration tasks, but data models, access, dependencies, performance, costs and recovery remain the project's responsibility. Exadata requires its own sizing and commercial validation; it is not assumed to be a universal destination for Oracle databases.
Cloud Guard identifies relevant configurations and activities through detector recipes and can recommend or execute configured responses. Security Zones apply recipes to compartments and can deny incompatible operations. Vault manages keys and secrets; Bastion offers temporary access to private resources; Vulnerability Scanning covers supported scenarios. These services do not replace data classification, IAM design, application security or incident response. Each finding is assigned a priority, owner, exception and procedure.
Audit records API calls; Logging brings together service and application logs; Monitoring works with metrics and alarms; Events reacts to state changes; Notifications distributes messages; Connector Hub moves data between supported services. Add Solution defines signals by critical service, retention, access, integration and cost. Alarms must reach an owner with context and a runbook. Collecting everything without an operational hypothesis increases volume without improving response.
Availability Domains and Fault Domains can reduce failure exposure according to the region and service. Not all regions have the same topology or offering. The application must operate during the failure under consideration. Backups, clones, replication and Data Guard address different risks. RPO, RTO, consistency, destination region, capacity, credentials and dependencies must be documented. Object Storage can support retention and copies, subject to policies, lifecycle and deletion controls. Restore, switchover, failover and failback must be exercised.
Compartments, tags and budgets support allocation and alerts but do not replace financial owners. Compute, storage, databases, licenses, FastConnect, egress, logs and backups make up total cost. Service limits and quotas can vary by region and tenancy. Specific shapes or capacities may require planning. Commitments, licenses and discounts depend on the current contract and are not assumed on this page.
OCI offers public, dedicated and Cloud@Customer models, as well as multicloud integrations. The choice depends on residency, latency, operations, sovereignty, connectivity and contract. Available services and responsibilities change between models. Integrations with other clouds must address identity, networking, DNS, observability, data transfer and incident ownership. “Multicloud” adds value only when it meets a concrete requirement.
The plan identifies applications, databases, data, integrations, licenses, dependencies and windows. Migration tools are selected after the strategy for each workload. Flow:
discover and classify;
establish a landing zone;
validate connectivity and security;
pilot a representative workload;
migrate in waves with rollback;
stabilize performance, backup, costs and observability;
hand over runbooks and responsibilities.
Regions do not necessarily have the same services, shapes or capacities. Oracle Database, Java, operating systems and third-party software require contractual validation. BYOL, license included and commercial programs depend on the product and current terms. Add Solution support covers the scope contracted with the customer. Oracle Support and cloud plans are contracted separately and follow their own terms. Integration between these workflows must be defined in operations.
Clear answers for OCI architecture, operations and continuity decisions.
No. The reference is modular. The project selects components proportionate to risk, scale and operations while preserving minimum identity, networking, logging, cost and recovery foundations.
No. They are logical scopes for organization and access. Network isolation depends on VCNs, subnets, routes, NSGs, gateways and policies.
Not on its own. Circuits, locations, providers, CPEs, DRGs and routes must form the resilient design.
It reduces platform tasks but does not eliminate modeling, access, integration, performance, cost and recovery work.
No. They apply a recipe's policies to supported resources. Processes, applications, identities and evidence are still necessary.
When workload, compatibility, consolidation, performance and operational requirements justify the investment and are validated through sizing.
No. It depends on failure events, data residency, RPO, RTO, cost and recovery capacity.
tenancy and workload assessment;
landing zone and Terraform;
IAM, compartments and policies;
VCN, DRG, VPN and FastConnect;
compute, OKE, storage and databases;
security and observability;
backup, DR e testes;
costs, quotas and capacity planning;
migration, documentation and ongoing operational support.
Connect tenancy, identity, networking, databases, protection, costs and operations before expanding the environment.