Requirements and limitations for Amazon RDS Custom for Oracle - Amazon Relational Database Service

Requirements and limitations for Amazon RDS Custom for Oracle

Following, you can find a summary of the Amazon RDS Custom for Oracle requirements and limitations for quick reference. Requirements and limitations also appear in the relevant sections.

General requirements for RDS Custom for Oracle

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

DB instance class support for RDS Custom for Oracle

RDS Custom for Oracle supports the following DB instance classes:

  • db.m5.large–db.m5.24xlarge

  • db.r5.large–db.r5.24xlarge

AWS Region support for RDS Custom for Oracle

RDS Custom is supported in the following AWS Regions:

  • Asia Pacific (Tokyo)

  • Asia Pacific (Singapore)

  • Asia Pacific (Sydney)

  • Europe (Frankfurt)

  • Europe (Stockholm)

  • Europe (Ireland)

  • US East (N. Virginia)

  • US East (Ohio)

  • US West (Oregon)

Limitations for RDS Custom for Oracle

The following limitations apply to RDS Custom for Oracle:

  • You can't provide your own AMI.

  • Not all options are supported. For example, when you create 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.

    • Set backup retention to 0.

    • Configure Kerberos authentication.

    • Specify your own DB parameter group, option group, or character set.

    • Turn on Performance Insights.

    • Turn on automatic minor version upgrade.

  • You can't change the DB instance class. For example, you can't change a db.m5.xlarge instance to db.m5.2xlarge. However, you can restore a DB snapshot to a different DB instance class.

  • The maximum DB instance storage is 64 TiB.

  • You can't use the Oracle Multitenant architecture.

  • Only one database is supported on an RDS Custom for Oracle instance.