Creating a CEV - Amazon Relational Database Service

Creating a CEV

You can create a CEV using the AWS Management Console or the AWS CLI. Typically, creating a CEV takes about two hours.

You can then use the CEV to create an RDS Custom instance. Make sure that the Amazon S3 bucket containing your installation files is in the same AWS Region as your CEV. Otherwise, the process to create a CEV fails.

For more information, see Creating an RDS Custom for Oracle DB instance.

To create a CEV

  1. Sign in to the AWS Management Console and open the Amazon RDS console at

  2. In the navigation pane, choose Custom engine versions.

    The Custom engine versions page shows all CEVs that currently exist. If you haven't created any CEVs, the page is empty.

  3. Choose Create custom engine version.

  4. For Engine type, choose Oracle.

  5. For Edition, choose Oracle Enterprise Edition. Oracle Enterprise Edition (Oracle RAC option) isn't supported.

  6. For Architecture settings, choose Multitenant architecture to create a Multitenant CEV, which uses the engine custom-oracle-ee-cdb. You can create an RDS Custom for Oracle CDB with a Multitenant CEV only. If you don't choose this option, your CEV is a non-CDB, which uses the engine custom-oracle-ee.

  7. For Major version, choose the major engine version.

  8. In Version details, enter a valid name in Custom engine version name.

    The name format is major-engine-version.customized_string. You can use 1–50 alphanumeric characters, underscores, dashes, and periods. For example, you might enter the name 19.cdb_cev1.

    Optionally, enter a description for your CEV.

  9. For S3 location of manifest files, enter the location of the Amazon S3 bucket that you specified in Uploading your installation files to Amazon S3. For example, enter s3://my-custom-installation-files/806242271698/cev1/.

  10. In the RDS Custom encryption section, select Enter a key ARN to list the available AWS KMS keys.

    Then select your KMS key from the list. An AWS KMS key is required for RDS Custom. For more information, see Make sure that you have a symmetric encryption AWS KMS key.

  11. Choose Create custom engine version.

    If the CEV manifest has an invalid form, the console displays Error validating the CEV manifest. Fix the problems, and try again.

The Custom engine versions page appears. Your CEV is shown with the status Creating. The process to create the CEV takes approximately two hours.

To create a CEV by using the AWS CLI, run the create-custom-db-engine-version command.

The following options are required:

  • --engine engine-type, where engine-type is either custom-oracle-ee-cdb for a CDB or custom-oracle-ee for a non-CDB. You can create CDBs only from a CEV created with custom-oracle-ee-cdb. You can create non-CDBs only from a CEV created with custom-oracle-ee.

  • --engine-version major-engine-version.customized_string

  • --kms-key-id

  • --manifest manifest_string or --manifest file:file_name

    Newline characters aren't permitted in manifest_string. Make sure to escape double quotes (") in the JSON code by prefixing them with a backslash (\).

    The following example shows the manifest_string for 19c from Preparing the CEV manifest. The example sets new values for the Oracle base, Oracle home, and the ID and name of the UNIX/Linux user and group. If you copy this string, remove all newline characters before pasting it into your command.

    "{\"mediaImportTemplateVersion\": \"2020-08-14\",\"databaseInstallationFileNames\": [\"\"],\"opatchFileNames\": [\"\"],\"psuRuPatchFileNames\": [\"\"],\"otherPatchFileNames\": [\"\",\"\",\"\",\"\",\"\",\"\",\"\",\"\"]\"installationParameters\":{ \"unixGroupName\":\"dba\", \ \"unixUname\":\"oracle\", \ \"oracleHome\":\"/home/oracle/\", \ \"oracleBase\":\"/home/oracle/\"}}"

  • --database-installation-files-s3-bucket-name s3-bucket-name, where s3-bucket-name is the bucket name that you specified in Uploading your installation files to Amazon S3. The AWS Region in which you run create-custom-db-engine-version must be the same Region as your Amazon S3 bucket.

You can also specify the following options:

The following example creates a Multitenant CEV named 19.cdb_cev1. Make sure that the name of your CEV starts with the major engine version number.

For Linux, macOS, or Unix:

aws rds create-custom-db-engine-version \ --engine custom-oracle-ee-cdb \ --engine-version 19.cdb_cev1 \ --database-installation-files-s3-bucket-name my-custom-installation-files \ --database-installation-files-s3-prefix 123456789012/cev1 \ --kms-key-id my-kms-key \ --description "some text" \ --manifest manifest_string

For Windows:

aws rds create-custom-db-engine-version ^ --engine custom-oracle-ee-cdb ^ --engine-version 19.cdb_cev1 ^ --database-installation-files-s3-bucket-name s3://my-custom-installation-files ^ --database-installation-files-s3-prefix 123456789012/cev1 ^ --kms-key-id my-kms-key ^ --description "some text" ^ --manifest manifest_string

Get details about your CEV by using the describe-db-engine-versions command.

aws rds describe-db-engine-versions \ --engine custom-oracle-ee-cdb \ --include-all

The following partial sample output shows the engine, parameter groups, manifest, and other information.

"DBEngineVersions": [ { "Engine": "custom-oracle-ee", "MajorEngineVersion": "19", "EngineVersion": "19.cev.2021-01.08", "DatabaseInstallationFilesS3BucketName": "us-east-1-123456789012-cev-customer-installation-files", "DatabaseInstallationFilesS3Prefix": "123456789012/cev1", "CustomDBEngineVersionManifest": "{\n\"mediaImportTemplateVersion\": \"2020-08-14\",\n\"databaseInstallationFileNames\": [\n\"\"\n],\n\"installationParameters\": {\n\"oracleBase\":\"/tmp\",\n\"oracleHome\":\"/tmp/Oracle\"\n},\n\"opatchFileNames\": [\n\"\"\n],\n\"psuRuPatchFileNames\": [\n\"\"\n],\n\"otherPatchFileNames\": [\n\"\",\n\"\",\n\"\",\n\"\",\n\"\",\n\"\",\n\"\",\n\"\"\n]\n}\n", "DBParameterGroupFamily": "custom-oracle-ee-19", "DBEngineDescription": "Oracle Database server EE for RDS Custom", "DBEngineVersionArn": "arn:aws:rds:us-west-2:123456789012:cev:custom-oracle-ee/19.my_cev1/0a123b45-6c78-901d-23e4-5678f901fg23", "DBEngineVersionDescription": "test", "KMSKeyId": "arn:aws:kms:us-east-1:123456789012:key/ab1c2de3-f4g5-6789-h012-h3ijk4567l89", "CreateTime": "2022-11-18T09:17:07.693000+00:00", "ValidUpgradeTarget": [ { "Engine": "custom-oracle-ee", "EngineVersion": "19.cev.2021-01.09", "Description": "test", "AutoUpgrade": false, "IsMajorVersionUpgrade": false } ]

Failure to create a CEV

If the process to create a CEV fails, RDS Custom issues RDS-EVENT-0198 with the message Creation failed for custom engine version major-engine-version.cev_name, and includes details about the failure. For example, the event prints missing files.

You can't modify a failed CEV. You can only delete it, then try again to create a CEV after fixing the causes of the failure. For information about troubleshooting the reasons for CEV creation failure, see Troubleshooting custom engine version creation for RDS Custom for Oracle.