Notes and Constraints
Precautions
- RDS Supabase AI applications are free of charge during the public beta. Depending on your workload scenarios, you are billed only for using public NAT gateways (or EIPs), instance storage, and OBS object storage.
- Two specifications are currently available: 2 vCPUs | 4 GB and 2 vCPUs | 8 GB. Select a specification as required. If you need a larger specification, submit a service ticket to apply for it.
- RDS Supabase requires an RDS for PostgreSQL instance to be hosted. You can associate the instance with an application in either of the following ways:
- Create an application and provision a new RDS for PostgreSQL instance: Provision a new primary/standby or single-node instance.
The new DB instance can be purchased using either the yearly/monthly or pay-per-use billing mode. It has the same functions and usage as an instance created on the RDS instance creation page. You can still connect to it directly using a database driver.
Only an available RDS for PostgreSQL primary/standby or single-node non-DR instance running PostgreSQL 17 or later can be hosted. The DB instance must be in the same VPC and subnet as the application, and must not be undergoing a high-risk operation or another mutually exclusive operation.
- Create an application and bind an existing RDS for PostgreSQL instance to it: Select an existing primary/standby or single-node instance that is running properly.
Only one available RDS for PostgreSQL primary/standby or single-node non-DR instance running PostgreSQL 17 or later can be hosted. The DB instance must be in the same VPC and subnet as the application, and must not be undergoing a high-risk operation or another mutually exclusive operation.
For production environments, you are advised to select a primary/standby instance whose specifications are at least as large as those of the application. This helps ensure high availability and avoid slow workload responses, insufficient connection pool capacity, and the resulting workload failures caused by resource or performance mismatches.
- Create an application and provision a new RDS for PostgreSQL instance: Provision a new primary/standby or single-node instance.
- In the scenario where a new DB instance is provisioned, after you submit an application creation task, the system first creates an RDS for PostgreSQL instance. After the instance is created, the application is automatically created. Do not perform operations on the hosted DB instance while the Supabase application is being created. Otherwise, application creation may fail or encounter errors. The name of the hosted DB instance is system-generated and cannot be customized. Its default format is rds-supabase-pg-{UUID}, for example, rds-supabase-pg-8c44ba06.
- After the application is created, it is automatically bound to and manages the DB instance, establishing a management relationship between them. This does not change the database's original capabilities or usage. You can connect to and use the database service as usual through a database driver. No other changes are made to the database's functionality.
- Do not perform any operations on the DB instance while the management relationship is being established. During initialization, the application performs configuration operations on the DB instance, including creating predefined databases, tables, and users, installing extensions that provide AI capabilities, inserting relevant metadata, and restarting the database process.
- The following databases are automatically created on the hosted DB instance of a Supabase AI application. Do not delete or directly operate on these databases (for example, by inserting or deleting data) while the application is running, as this may affect the application's normal operation. You can perform operations such as deleting these databases only if you choose to retain the DB instance when deleting the Supabase application.
- supabase_db
An application database used to store created tables, data, and Supabase's built-in schemas. Exercise extreme caution when performing operations on this database, especially high-risk O&M operations like rate limiting or session termination.
The extensions pgjwt, pgcrypto, supabase_vault, vector, pg_net, and pg_graphql are automatically installed in this database by default. Do not delete these necessary extensions.
- _supabase
A database used to store platform-level configurations, project metadata, and migration logs, and other related information.
- supabase_db
- The following default accounts are automatically created on the hosted DB instance of the Supabase AI application. These are predefined accounts and cannot be deleted or modified. You cannot create other accounts with the same names on this DB instance.
Automatically created default accounts include: rds_supabase_authenticator, rds_supabase_auth_admin, rds_supabase_admin, rds_supabase_storage_admin, rds_supabase_postgres, rds_supabase_functions_admin, supabase_realtime_adim, anon, authenticated, and service_role.
- Do not modify the network configuration of the hosted DB instance (including its VPC, subnet, private IP address, and port). You cannot establish a DR relationship for the instance or perform a major version upgrade. These operations may affect application operation.
- Deleting a hosted RDS for PostgreSQL instance will automatically delete its associated Supabase AI application. Exercise caution when performing this operation. When deleting an application, you can choose to retain its DB instance. In this case, the management relationship is automatically removed and all database functions remain available as usual.
- After the application is created, you can modify its name on the application list page or the application details page. You can also add custom remarks.
Constraints
- By default, Supabase AI applications support only the general-purpose instance class and standalone deployment.
- A Supabase AI application can manage only one RDS for PostgreSQL instance. You cannot manually remove the management relationship or associate the application with another DB instance.
- No other operations can be performed on an application while it is being created, and its hosted DB instance cannot be deleted during this process.
- Version requirements for hosted RDS for PostgreSQL instances: Only PostgreSQL 17 and later versions are supported. The minimum supported minor version is 17.10.260601.
- During the public beta, native Edge Functions provided by the open-source version are not supported. Edge Functions are a serverless compute service that allows developers to deploy and execute custom code on edge nodes (typically CDN nodes) across a globally distributed network.
- You are advised to use the cloud functions provided by Huawei Cloud FunctionGraph. FunctionGraph provides capabilities equivalent to Edge Functions, with richer features, broader programming language support, and better overall cost-effectiveness. It further extends the capabilities of Supabase BaaS, allowing you to run complex or security-sensitive custom backend logic, such as scheduled tasks and payment transactions.
- After a Supabase AI application is deleted, the associated DB instance is hosted by a new Supabase AI application, and the original data in the instance remains. You are advised to clean up the original data to avoid affecting your workloads.
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot