RDS Custom for Oracle workflow - Amazon Relational Database Service

RDS Custom for Oracle workflow

The following diagram shows the typical workflow for RDS Custom for Oracle.

            RDS Custom for Oracle architecture components

The steps are as follows:

  1. Upload your database software to your Amazon S3 bucket.

    For more information, see Uploading your installation files to Amazon S3.

  2. Create an RDS Custom custom engine version (CEV) from your media.

    For more information, see Creating a CEV.

  3. Create an RDS Custom DB instance from a CEV.

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

  4. Connect your application to the RDS Custom DB instance endpoint.

    For more information, see Connecting to your RDS Custom DB instance using SSH and Connecting to your RDS Custom DB instance using AWS Systems Manager.

  5. (Optional) Access the host to customize your software.

  6. Monitor notifications and messages generated by RDS Custom automation.

Database installation files

Your responsibility for media is a key difference between Amazon RDS and RDS Custom. Amazon RDS, which is a fully managed service, supplies the Amazon Machine Image (AMI) and database software. The Amazon RDS database software is preinstalled, so you need only choose a database engine and version, and create your database.

For RDS Custom, you supply your own media. When you create a custom engine version, RDS Custom installs the media that you provide. RDS Custom media contains your database installation files and patches. This service model is called Bring Your Own Media (BYOM).

Custom engine version

An RDS Custom custom engine version (CEV) is a binary volume snapshot of a database version and AMI. You store your database installation files in Amazon S3. When you create your CEV, you specify the files in a JSON document called a CEV manifest.

Name your CEV using a customer-specified string. The name format is the following, depending on your Oracle Database release:

  • 12.1.customized_string

  • 12.2.customized_string

  • 18.customized_string

  • 19.customized_string

You can use 1–50 alphanumeric characters, underscores, dashes, and periods. For example, you might name your CEV 19.my_cev1. To learn how to create a CEV, see Working with custom engine versions for Amazon RDS Custom for Oracle.

Creating a DB instance for RDS Custom for Oracle

After you create the CEV, it's available for use. You can create multiple CEVs, and you can create multiple RDS Custom for Oracle instances from any CEV. You can also change the status of a CEV to make it available or inactive.

To create your RDS Custom for Oracle DB instance, use the create-db-instance command. In this command, specify which CEV to use. The procedure is similar to creating an Amazon RDS instance. However, some of the parameters are different. For more information, see Creating and connecting to a DB instance for Amazon RDS Custom for Oracle.

Database connection

Like an Amazon RDS DB instance, your RDS Custom DB instance resides in a VPC. Your application connects to the RDS Custom instance using an Oracle Listener, just as with RDS for Oracle.

RDS Custom customization

You can access the RDS Custom host to install or customize software. To avoid conflicts between your changes and the RDS Custom automation, you can pause the automation for a specified period. During this period, RDS Custom doesn't perform monitoring or instance recovery. At the end of the period, RDS Custom resumes full automation. For more information, see Pausing and resuming RDS Custom automation.