Learn the basic concepts for Oracle Database@AWS onboarding.
Oracle Database@AWS is an Oracle database service running on Oracle Cloud Infrastructure (OCI), with hardware located in AWS data centers. This ensures that AWS resources and applications have the lowest possible latency when accessing Oracle Database@AWS.
Oracle Database@AWS runs on infrastructure managed by Oracle's expert Cloud Infrastructure operations team. The operations team performs software patching, infrastructure updates, and other operations through a connection to OCI. While the service requires that customers have an OCI tenancy, most service activities take place in the AWS environment.
Purchase Offer Options
Private offer: To receive a private offer, you first contact Oracle's sales team to negotiate a contract for Oracle Database@AWS. Billing and payment for the service is done through AWS. Payment for Oracle Database@AWS counts toward your AWS Commitments. Existing Oracle Database software customers can use the Bring Your Own License (BYOL) option or Unlimited License Agreements (ULAs). On your regular AWS invoices, you'll see charges for Oracle Database@AWS alongside charges for your other AWS Marketplace services.
Roles and Responsibilities 🔗
Each Onboarding step requires one or more customer teams to be involved. Depending on the size of your AWS investment and your organization, some members of your organization could be on more than one of the teams described in the following section.
The following table summarizes the teams involved in each step of the process. Sometimes, more than one team might need to collaborate on the work of an onboarding step, or a second team might need to review the work of the team primarily responsible for the work of the onboarding step.
Customer team
Onboarding steps performed
Business owner
This is the persona that wants to purchase the service (or receives internal requests for it), and who starts working with the Legal and Purchasing teams on the purchase.
Places a private offer request
Reviews and approves the private offer
Purchasing
Places a private offer request
Reviews and approves the private offer
Legal
Reviews and approves the private offer (if applicable)
Cloud administrator
All onboarding steps (see also "security specialist" and "identity" teams for steps involving role based access control and identity)
Networking specialist
Checks tenancy networking limits
Database administrator
Checks tenancy limits for Oracle Database@AWS database resources
Onboarding Overview 🔗
During onboarding, you configure your AWS environment to use the Oracle Database@AWS service. This topic provides a high-level overview of onboarding. For complete instructions, see the Onboarding with Oracle Database@AWS section of this documentation.
Business Relationship and Offer
OCI offers customers Oracle Database@AWS through private offer purchase in the AWS Marketplace.
To receive a private offer, your organization contacts the Oracle Sales team and negotiates a service price based on parameters such as length of contract, spend commitment, and number of Exadata hardware deployments. After you successfully negotiate and sign a contract with Oracle, OCI creates a private offer for your organization in AWS Marketplace for you to accept. After your organization signs the purchase agreements, OCI creates an order in the AWS Marketplace and sends you an email confirming the offer.
Private Offer: Select the link in the email you received from Oracle, or open the AWS Marketplace Orders page, then select the link for your offer.
At this point, you connect your AWS account with a new or existing OCI cloud account. Here's what happens during this process:
AWS Marketplace prompts you to select an existing OCI cloud account, or create a new OCI cloud account to use with the Oracle Database@AWS. An OCI account is required because, while the databases are deployed in your AWS environment, some resource components like container database (CDB) and pluggable databases (PDBs) are configured using OCI console.
The AWS and OCI accounts are linked. During this process, the service defines a connection between a AWS account (selected by the user) and an Oracle Database Subscription for the service. This defines the mapping between AWS and OCI that's used when provisioning resources in both environments, managing billing, delivering metrics, and more.
At this point, the Oracle Database@AWS service is enabled in your AWS environment, and you can provision Oracle Database resources. Verify your tenancy limits to ensure you can deploy the database resources you need.
OCI Service Limits
OCI uses service limits to control the number of certain resource types that you can deploy in OCI. Your ability to deploy Oracle Database resources in AWS (and OCI) is affected by the service limits set in your OCI cloud account. When creating a new OCI tenancy, or connecting to an existing OCI tenancy, the linking process described in this topic automatically sets limits for Oracle Database products and associated resources in the OCI cloud account used for Oracle Database@AWS.
Before you begin provisioning Oracle Database resources in AWS, assess how many Oracle Database resources (Exadata Infrastructure, Exadata VM clusters, CDBs, and PDBs) you plan to deploy in your AWS environment. Then review the current service limits in your OCI tenancy and determine if your existing limits will let you deploy the number of Oracle Database@AWS resources you need.
You can provision Oracle Database@AWS using the AWS Management Console.
Management of Oracle database system infrastructure and VM cluster resources takes place in the AWS Management Console as well.
For Oracle Container Databases (CDB) and Oracle Pluggable Databases (PDB), some management tasks are completed using the OCI console.
Database and application developers work in the AWS Management Console to interact with Oracle Database@AWS databases.
What's Next? 🔗
Review the following topics to plan your Oracle Database@AWS deployment.