Oracle Database@AWS Architect Professional key terms

A managed offering that places Oracle Exadata infrastructure inside AWS data centers, letting you run Oracle databases close to AWS workloads while Oracle operates and manages the database platform.

The provisioned hardware and control-plane object that hosts one or more Oracle Exadata VM Clusters; it defines shape, storage, and placement, and is the parent object for databases.

A group of compute nodes and shared storage created inside an Exadata Infrastructure resource that runs Oracle Grid Infrastructure and hosts Oracle databases with RAC or single-instance layouts.

A VM cluster variant provisioned for Oracle Autonomous Database workloads, where Oracle automates patching, tuning, and scaling of the databases running on the underlying Exadata system.

A dedicated, isolated network construct created during provisioning that connects Oracle Database@AWS resources to your AWS VPC and to on-premises networks through standard AWS routing and gateways.

The subnet within an ODB network used for application and client connectivity to the database endpoints; it carries the traffic that applications and database clients actually use.

A subnet reserved for backup and recovery traffic between the database system and backup destinations, kept separate from client traffic to simplify routing and security controls.

An AWS connection between two VPCs that routes traffic privately using private IP addresses, commonly used to reach Oracle Database@AWS endpoints from application VPCs in the same or another account.

A regional hub that connects VPCs, VPNs, and on-premises networks through a single attachment point, often used to centralize and scale routing to Oracle Database@AWS networks.

An endpoint that exposes a service to a VPC using private IP addresses only, so database traffic never traverses the public internet and stays within the AWS network.

A stateful virtual firewall attached to resources that permits or denies inbound and outbound traffic by protocol, port, and source or destination, controlling access to database listeners.

A stateless subnet-level filter that evaluates ordered allow and deny rules for traffic entering or leaving a subnet, providing a coarse layer beneath security groups.

An AWS identity with permission policies that trusted principals such as users or services can assume temporarily, used to delegate access to AWS resources involved in provisioning and operations.

A predefined IAM role that an AWS service assumes to perform actions on your behalf, created automatically during onboarding and required for the service to manage resources.

A JSON policy attached directly to a resource such as a KMS key or secret that specifies which principals may perform which actions, independent of identity-based policies.

The resource policy governing an AWS KMS key; it must grant the required principals access before encrypted volumes, backups, or secrets can be used by the database service.

Protection of stored data, including database files, backups, and redo, using keys managed in AWS KMS or Oracle key management so that underlying storage media never holds plaintext.

An Oracle Database feature that encrypts data files and sensitive columns at rest with keys stored in a wallet or external key store, transparent to applications issuing SQL.

A password-protected container holding credentials such as TDE master keys and database passwords, used by the database to open encrypted data without manual intervention.

The Oracle software stack comprising Clusterware and Automatic Storage Management that enables node clustering, resource failover, and shared storage management for databases on Exadata.

Oracle Real Application Clusters, a configuration in which multiple instances on separate nodes mount one database, providing instance-level high availability and horizontal scalability.

Oracle's replication technology that maintains a standby database synchronized with a primary, enabling role transitions for disaster recovery and, with Active Data Guard, read-only offload.

An Oracle Data Guard observer-driven capability that automatically promotes a standby database when the primary becomes unavailable, reducing recovery time without manual intervention.

A planned, reversible role reversal between primary and standby databases, typically performed for maintenance, in which the standby becomes primary and the old primary becomes standby.

A fully managed Oracle database service that automates provisioning, patching, backup, and scaling, available within Oracle Database@AWS for workloads suited to hands-off administration.

A self-contained database within a multitenant container database that has its own metadata and can be opened, cloned, or moved independently of other pluggable databases.

The multitenant root database that hosts one or more pluggable databases, sharing instance memory and background processes to reduce overhead and simplify consolidation.

The practice of combining multiple databases onto shared infrastructure, often using multitenant architecture, to reduce cost and management effort while preserving isolation between workloads.

A high-speed Oracle utility for exporting and importing logical database objects and data, frequently used for migrations into Oracle Database@AWS when physical transport is impractical.

Oracle's logical replication product that captures changes from a source database and applies them to a target, supporting near-zero-downtime migrations and ongoing data synchronization.

The final phase of a migration when applications stop using the source database and begin using the target, usually after replication has caught up and validation has passed.

A documented procedure for reverting to the original environment if a deployment or migration fails, including data reconciliation steps and decision criteria for triggering the reversal.

The pre-migration analysis of source database versions, features, dependencies, sizing, and performance that determines the target shape and the migration method to use.

The rule set defining how long backups are kept and when they expire, balancing recovery point objectives against storage cost and compliance requirements.

The maximum acceptable amount of data loss measured in time, which drives backup frequency and redo transport settings such as Data Guard synchronization mode.

The maximum acceptable duration to restore service after an outage, which determines whether standby databases, automatic failover, or restore-from-backup strategies are required.

A consistent scheme for assigning key-value metadata to provisioned resources so that cost allocation, ownership, automation, and compliance reporting remain accurate across accounts.

The baseline multi-account AWS environment with identity, logging, networking, and guardrails established before workloads are deployed, providing the foundation for database provisioning.