RDS Custom for Oracle requirements and limitations - Amazon Relational Database Service
Region and version supportEdition and licensing supportDB instance class supportGeneral requirements for RDS Custom for OracleGeneral limitations for RDS Custom for Oracle
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

RDS Custom for Oracle requirements and limitations

In this topic, you can find a summary of the Amazon RDS Custom for Oracle feature availability and requirements for quick reference.

Amazon Web Services Region and database version support for RDS Custom for Oracle

Feature availability and support vary across specific versions of each database engine, and across Amazon Web Services Regions. For more information on version and Region availability of RDS Custom for Oracle, see RDS Custom.

Edition and licensing support for RDS Custom for Oracle

RDS Custom for Oracle supports only Enterprise Edition on the BYOL model.

DB instance class support for RDS Custom for Oracle

RDS Custom for Oracle supports the following DB instance classes.

Type Size
db.r6i db.r6i.large | db.r6i.xlarge | db.r6i.2xlarge | db.r6i.4xlarge | db.r6i.8xlarge | db.r6i.12xlarge | db.r6i.16xlarge | db.r6i.24xlarge | db.r6i.32xlarge
db.r5b db.r5b.large | db.r5b.xlarge | db.r5b.2xlarge | db.r5b.4xlarge | db.r5b.8xlarge | db.r5b.12xlarge | db.r5b.16xlarge | db.r5b.24xlarge
db.r5 db.r5.large | db.r5.xlarge | db.r5.2xlarge | db.r5.4xlarge | db.r5.8xlarge | db.r5.12xlarge | db.r5.16xlarge | db.r5.24xlarge
db.x2iedn db.x2iedn.xlarge | db.x2iedn.2xlarge | db.x2iedn.4xlarge | db.x2iedn.8xlarge | db.x2iedn.16xlarge | db.x2iedn.24xlarge | db.x2iedn.32xlarge
db.m6i db.m6i.large | db.m6i.xlarge | db.m6i.2xlarge | db.m6i.4xlarge | db.m6i.8xlarge | db.m6i.12xlarge | db.m6i.16xlarge | db.m6i.24xlarge | db.m6i.32xlarge
db.m5 db.m5.large | db.m5.xlarge | db.m5.2xlarge | db.m5.4xlarge | db.m5.8xlarge | db.m5.12xlarge | db.m5.16xlarge | db.m5.24xlarge
db.t3 db.t3.medium | db.t3.large | db.t3.xlarge | db.t3.2xlarge

General requirements for RDS Custom for Oracle

Make sure to follow these requirements for Amazon RDS Custom for Oracle:

General limitations for RDS Custom for Oracle

The following limitations apply to RDS Custom for Oracle:

  • You can't provide your own AMI. You can specify only the default AMI or an AMI that has been previously used by a CEV.

  • You can't modify a CEV to use a different AMI.

  • You can't modify the DB instance identifier of an existing RDS Custom for Oracle DB instance.

  • You can't specify the multitenant architecture for a database release other than Oracle Database 19c.

  • You can't create a CDB instance from a CEV that uses the custom-oracle-ee engine. The CEV must use custom-oracle-ee-cdb.

  • Not all Amazon RDS options are supported. For example, when you create or modify an RDS Custom for Oracle DB instance, you can't do the following:

    • Change the number of CPU cores and threads per core on the DB instance class.

    • Turn on storage autoscaling.

    • Create a Multi-AZ deployment.

      Note

      For an alternative HA solution, see the Amazon blog article Build high availability for Amazon RDS Custom for Oracle using read replicas.

    • Set backup retention to 0.

    • Configure Kerberos authentication.

    • Specify your own DB parameter group or option group.

    • Turn on Performance Insights.

    • Turn on automatic minor version upgrade.

  • You can't specify a DB instance storage size greater than the maximum of 64 TiB.

  • You can't create multiple Oracle databases on a single RDS Custom for Oracle DB instance.

  • You can’t stop your RDS Custom for Oracle DB instance or its underlying Amazon EC2 instance. Billing for an RDS Custom for Oracle DB instance can't be stopped.

  • You can't use automatic shared memory management. RDS Custom for Oracle supports only automatic memory management. For more information, see Automatic Memory Management in the Oracle Database Administrator’s Guide.

  • Make sure not to change the DB_UNIQUE_NAME for the primary DB instance. Changing the name causes any restore operation to become stuck.

For limitations specific to modifying an RDS Custom for Oracle DB instance, see Modifying your RDS Custom for Oracle DB instance. For replication limitations, see General limitations for RDS Custom for Oracle replication.