Skip to content
AMTEXConsulting

Oracle Cloud Infrastructure

The cloud layer that makes Oracle SaaS extensible.

OCI architecture for the workloads that live around Fusion: Autonomous Database, Functions, API Gateway, Object Storage, networking, identity and observability, designed for security and high availability.

OCI services around Oracle SaaS
  1. Edge

    • WAF
    • API Gateway
    • Identity
  2. Integration & compute

    OIC

    Functions

    Queue / Events

  3. Data

    • Autonomous DB
    • Object Storage
    • Vault
  4. Operations

    • Logging
    • Monitoring
    • Cloud Guard

Overview

Oracle OCI, done properly.

Fusion applications are closed by design. OCI is where the rest of the solution lives: the staging database for integrations, the API that a mobile app calls, the function that transforms a partner file, the storage that holds seven years of documents. AMTEX designs and runs that layer.

Technologies

  • Oracle Cloud Infrastructure
  • Autonomous Database
  • OCI Functions
  • OCI Object Storage
  • OCI API Gateway
  • OCI Vault & IAM
  • OCI Streaming & Events
  • Terraform
  • Oracle APEX

What we deliver

Capabilities

Everything AMTEX builds, configures and runs across Oracle OCI.

  • OCI architecture

    Compartments, tenancy design, landing zones and Terraform so every environment is reproducible.

  • Autonomous Database

    ATP and ADW for integration staging, application data, APEX and analytics, with private endpoints and Data Safe.

  • Object Storage

    Lifecycle-managed buckets for files, archives and report distribution, with pre-authenticated requests where appropriate.

  • API Gateway

    Authentication, rate limiting, request validation and routing in front of OIC, Functions and backend services.

  • Functions

    Serverless code for transforms and glue that OIC should not do in-line, in Node.js, Python or Java.

  • Notifications, Queue & Events

    Alerting and decoupling patterns: Events to Functions, Queue for buffering, Notifications to people.

  • Networking

    VCNs, private endpoints, FastConnect or VPN to on-prem, and the connectivity agent design for OIC.

  • Identity

    Identity domains, federation with Entra ID or Okta, policies written for least privilege.

  • Monitoring & logging

    Logging, Monitoring, alarms and dashboards that cover OIC, Functions and databases in one place.

  • High availability & DR

    Multi-AD designs, Autonomous Data Guard and tested recovery procedures.

  • Security

    Cloud Guard, Vault, Security Zones, WAF and a posture review against the CIS OCI benchmark.

  • Cloud modernisation

    Moving on-prem Oracle databases and applications to OCI, including EBS on OCI.

The hard parts

Where these projects become difficult

The places programmes slip, and what we do about each one.

  1. 01

    Hand-built tenancies

    The problem

    Nobody can rebuild the environment, and nobody is sure what the policies allow.

    How AMTEX approaches it

    Terraform for everything, a policy review and a landing-zone pattern applied retroactively.

  2. 02

    Integration sprawl

    The problem

    OIC does everything, including things it is slow and expensive at.

    How AMTEX approaches it

    Move heavy transforms to Functions, staging to ATP, files to Object Storage, and let OIC orchestrate.

  3. 03

    Cost visibility

    The problem

    The bill grows and nobody knows which workload caused it.

    How AMTEX approaches it

    Tagging standards, budgets and alarms, and right-sizing reviews.

Pattern

Event-driven, not polled.

The pattern we use when downstream systems need to react to Fusion in near real time without hammering its APIs.

  • Fusion raises the event; OIC subscribes and validates once.
  • A queue or stream decouples producers from consumers, so a slow consumer never blocks Fusion.
  • Consumers are Functions, applications behind API Gateway, or warehouse loads, each scaling independently.
  • Every hop is logged with the business identifier so a single invoice can be traced end to end.
Event-driven pattern around Fusion
  1. Trigger

    • Fusion business evente.g. Invoice approved
  2. Receive

    OIC event subscription

    Validate · enrich · publish

  3. Decouple

    • OCI Queue
    • OCI Streaming
  4. Consume

    • Functions
    • Application via API Gateway
    • Warehouse load
    • Notifications

How we work

From first conversation to steady state

  1. 01

    Assess

    Workloads, security posture, cost, connectivity.

  2. 02

    Design

    Landing zone, network, identity, service selection.

  3. 03

    Build

    Terraform, pipelines, workloads, observability.

  4. 04

    Operate

    Monitoring, patching, cost management, DR tests.

Is your OCI tenancy documented anywhere but in someone's head?

A short assessment tells you how far you are from reproducible.