Amazon iconAmazonSep 8, 2026 ~7 min source read

Getting started with Oracle Database@AWS: a practical onboarding guide

Step-by-step path from choosing an Oracle Database@AWS service to a provisioning-ready environment, covering public vs private offers, account prerequisites, OCI tenancy linking, and IAM configuration.

Getting started with Oracle Database@AWS: A complete onboarding guide

Share this story

Send the public story page.

Useful takeaways from this story.

Onboarding breaks into procurement (select and accept an offer) and technical setup (validate prerequisites, link OCI tenancy, configure AWS IAM) to reach provisioning-ready status.

Anchor entitlements to a single AWS buyer account and run Oracle sizing tools (AWR Miner, CPAT, ORAchk) early to feed private-offer sizing and avoid rework.

# Overview

# Procurement and onboarding at a glance The journey has two phases: Procurement (Steps 1–2) and Onboarding (Steps 3–5). The five concrete steps are:

  • Select your service and secure the offer.
  • Accept the offer (AWS Marketplace or private offer flow).
  • Validate account prerequisites.
  • Link your OCI tenancy.
  • Configure AWS Identity and Access Management (groups and roles).

Completing these steps prepares you to create ODB networks, provision Exadata infrastructure, and build VM clusters.

# Service selection and procurement paths Which service you choose determines the procurement path and capabilities:

# Requesting and accepting a private offer To begin a private offer, use the Oracle Database@AWS product page in the AWS Management Console and choose Request private offer. The flow redirects to OCI to capture region, workload requirements, and contact details. Oracle requires the buyer AWS account ID at the start because entitlements anchor to a single AWS account. You can also start this process through your Oracle account team or an AWS channel partner.

Sizing tip: run Oracle sizing utilities early (AWR Miner, Cloud Premigration Advisor Tool (CPAT), or ORAchk) on source databases. Their output helps scope CPU, memory, and Exadata configuration in the private offer and reduces iterations.

# Technical onboarding steps After accepting an offer, complete these onboarding tasks:

  • Validate prerequisites in your AWS account and confirm network, permissions, and cross-account requirements.
  • Link your OCI tenancy so Oracle-managed Exadata services can be associated with your AWS environment.
  • Configure AWS IAM groups and roles as described by the offer—this includes the buyer account role setup so provisioning actions can proceed.

Completing these makes your environment provisioning-ready.

# What's next after onboarding Once provision-ready, you move to network and infrastructure creation: define ODB networks, provision Exadata infrastructure (racks or shared Exascale resources), and create VM clusters or Autonomous Database instances based on the service you selected.

# Practical checklist

  • Decide service (public vs private offer).
  • If private, provide AWS buyer account ID and request private offer via the Console or Oracle/AWS channel.
  • Run AWR Miner/CPAT/ORAchk for sizing input.
  • Accept offer in AWS Marketplace or OCI portal.
  • Validate AWS account prerequisites and link OCI tenancy.
  • Create IAM groups and roles per the onboarding instructions.
  • Proceed to create ODB networks and provision infrastructure.

More context around this story.

Loading more related stories...

Keep reading in the app

Open the app view to save this story, compare related coverage, and continue from the same source.

Open in app