RDS Custom for Oracle requirements and limitations

You have access to My Oracle Support and Oracle Software Delivery Cloud to download the supported list of installation files and patches for RDS Custom for Oracle. If you use an unknown patch, custom engine version (CEV) creation fails. In this case, contact the RDS Custom support team and ask it to add the missing patch. For more information, see Step 2: Download your database installation files and patches from Oracle Software Delivery Cloud.

You have access to Amazon S3. You need this service for the following reasons:

For more information, see Step 3: Upload your installation files to Amazon S3 and Creating a CEV.

You use the DB instance classes listed in DB instance class support for RDS Custom for Oracle to create your RDS Custom for Oracle DB instances.

Your RDS Custom for Oracle DB instances run Oracle Linux 7 Update 9 or higher.

You specify the gp2, gp3, or io1 solid state drives for Amazon EBS storage. The maximum storage size is 64 TiB.

You have an Amazon KMS key to create an RDS Custom for Oracle DB instance. For more information, see Step 1: Create or reuse a symmetric encryption Amazon KMS key.

You have the Amazon Identity and Access Management (IAM) role and instance profile required for creating RDS Custom for Oracle DB instances. For more information, see Step 4: Configure IAM for RDS Custom for Oracle.

The Amazon Identity and Access Management (IAM) user that creates a CEV or RDS Custom DB instance has the required permissions for IAM, CloudTrail, and Amazon S3.

For more information, see Step 5: Grant required permissions to your IAM user or role.

You supply your own virtual private cloud (VPC) and security group configuration. For more information, see Step 6: Configure your VPC for RDS Custom for Oracle.

You supply a networking configuration that RDS Custom for Oracle can use to access other Amazon Web Services. For specific requirements, see Step 4: Configure IAM for RDS Custom for Oracle.

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

You can specify the Oracle multitenant architecture for Oracle Database 19c only.

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 because RDS Custom for Oracle supports automatic memory management only. 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.

You can't provide your own AMI for use in an RDS Custom for Oracle CEV. You can specify either the default AMI or an AMI that has been previously used by an RDS Custom for Oracle CEV.

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

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

RDS Custom for Oracle doesn't currently allow you to upgrade the OS of your RDS Custom for Oracle DB instance with RDS API calls. As a workaround, you can update your OS manually with the following command: sudo yum update --security.

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

Turn on storage autoscaling.

Create a Multi-AZ deployment.

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.