Bring Your Own Cloud (BYOC) is a deployment and management model for OceanBase clusters in your own or designated cloud account and network environment. The underlying computing, storage, and network resources typically belong to your cloud subscription. You can use the OceanBase Cloud console to perform tasks such as cluster creation, tenant management, and O&M.
Note
- Currently, when creating a BYOC cluster instance through OceanBase Cloud, only AWS is supported. The available regions, zones, and specifications are subject to what the wizard and console actually display.
- When selecting AWS, you must contact AWS Technical Support in advance to enable the Proxy Protocol v2 attribute for the NLB target group on your account and in the target region (specific parameter:
proxy_protocol_v2.client_to_server.header_placement=on_first_ack). Otherwise, you may not be able to access the database via the connection address after creating the tenant. This attribute is enabled separately for each account and region. Plan the regions you need and enable this attribute in each of them before creating instances. - BYOC cluster instances currently do not support features such as diagnostics and data migration. Refer to the console for the features available in your environment.
Prerequisites
You have an available AWS account for deployment. For details, see AWS Management Console.
You have confirmed that the instance quota in the target region under your cloud service provider account meets the needs for creation and subsequent scaling. For details, see Prepare BYOC instance quotas.
You have completed Authorize a BYOC cloud account.
Procedure
Log in to the OceanBase Cloud console and switch the project to BYOC Project (or your BYOC project) in the top menu bar.
In the left-side navigation pane, click Instances.
In the upper-right corner of the page, click Create Instance to go to the instance creation page.
Select BYOC for Instance Type.
In Cloud Vendor and Region: Select AWS and the target Region; in the Cloud service authorization drop-down list, select the authorized option.
In Instance Configuration, fill in or select the following items as needed (the form item names are subject to the console).
ParameterDescriptionInstance Name The name displayed for the cluster in the console. It must be 2 to 64 characters long and can only contain Chinese characters, numbers, English letters, underscores, and hyphens. Storage Architecture Shared-nothing architecture. Version Select the version of OceanBase Database you need. VPC The VPC where the instance and its components reside. You can choose an existing VPC, or OceanBase Cloud will automatically create a new one upon first creation. Deployment Solution Select the deployment solution you need, such as dual-IDC deployment. Availability Zone/Subnet IP Range The availability zone and subnet IP range configuration that matches the deployment solution, which must be consistent with VPC planning. Compute Specification Compute resource specifications such as node vCPU and memory. Storage Specification Select a data disk capacity within the range available in the wizard. Instance Backup Set Bucket The object storage bucket for storing backup data (an S3 bucket for AWS). It is recommended to use a dedicated bucket to store backup, monitoring logs, and other data for BYOC instances to avoid mixing with other business data. This option becomes available and effective only after Cloud Service Authorization is selected. Security Settings You can choose whether to enable data encryption (encrypt the database using a key; this setting cannot be changed after it is configured). In the Summary section, verify the information, read and agree to the relevant agreements (including the End User Agreement, Cloud Service SLA, and Data Collection Agreement), then click Next: Payment and complete the payment as prompted.
Return to the Instances page to view the cluster status.