Prerequisites for a Multi-AZ deployment with RDS Custom for Oracle - Amazon Relational Database Service
Migration for CEVs before 06.30.2025
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).

Prerequisites for a Multi-AZ deployment with RDS Custom for Oracle

Note

If you created your RDS Custom for Oracle instance before June 30, 2025, you cannot modify it from a Single-AZ to Multi-AZ deployment. Your underlying Custom Engine Version (CEV) was built with an older service-provided AMI that lacks Multi-AZ deployment support.

You must migrate your database to a new instance using a CEV that you create with a service-provided AMI after June 30, 2025.

See Migration steps for DB instances using CEVs created before June 30, 2025.

RDS Custom for Oracle requires specific prerequisites when converting from Single-AZ to Multi-AZ deployment. Incomplete prerequisites will cause Multi-AZ setup failure. Use either manual setup or the latest Amazon CloudFormation template file provided in the network setup instructions. For more information, see Step 3: Extract the CloudFormation templates for RDS Custom for Oracle.

To complete the prerequisites manually, follow the steps in Modifying an RDS Custom for Oracle Single-AZ deployment to a Multi-AZ deployment and note the following:

  • Ensure your RDS Custom for Oracle DB instance must use a CEV created after June 30, 2025 with the latest service-provided AMI.

  • Update the Amazon RDS security group inbound and outbound rules to allow port 1120.

  • Create new Amazon SQS VPC endpoints that allow the Amazon RDS RDS Custom for Oracle DB instance to communicate with Amazon SQS.

  • Update the Amazon SQS permissions in the instance profile role.

Important

Do not reboot your Multi-AZ primary DB instance manually by logging into the instance without pausing RDS Custom for Oracle automation.

Migration steps for DB instances using CEVs created before June 30, 2025

If you created your RDS Custom for Oracle DB instance before June 30, 2025, you cannot directly modify it to Multi-AZ deployment because the underlying CEV was built with an older service-provided AMI that lacks Multi-AZ support. You must migrate your database to a new instance using a CEV you create after June 30, 2025. Do the following for the migration.

  1. Create CEV from source with the latest service-provided AMI (after June 30, 2025)

  2. Launch a new DB instance with the new CEV

  3. Migrate your database from the existing DB instance that doesn’t support multi-AZ deployment to the newly created instance using one of following methods below: