EnableAgentRuntime
Enables the sandbox and Edge Routine capabilities for a Supabase instance. Read the operation description before you call this operation.
Operation description
During the public preview, the sandbox and Edge Routine features are free of charge.
Before you begin
Before you use this feature, authorize the service-linked role. The service-linked role used is AliyunServiceRoleForRDSAISupabase.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
rdsai:EnableAgentRuntime |
update |
*All Resource
|
None | None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| RegionId |
string |
No |
The region ID of the instance. |
cn-beijing |
| InstanceName |
string |
Yes |
The instance ID of the AI application. |
ra-supabase-8moov5lxba**** |
| VSwitchId |
string |
No |
The vSwitch ID used to create an endpoint. If this parameter is not specified, the vSwitch of the Supabase instance is used by default. Important The endpoint is created only once. When the first Supabase instance in a VPC enables the sandbox and Edge Routine function capabilities, the system performs automatic creation of the endpoint. When subsequent Supabase instances in the same VPC enable these capabilities, the existing endpoint is reused and no new endpoint is created. |
vsw-9dp2hkpm22gxscfgy**** |
| SecurityGroupId |
string |
No |
The security group ID used to create an endpoint. If not specified: The system performs automatic creation of a security group named sg-aliyun-rds-created-supabase-sandbox in the VPC where the instance resides. No manual operation is required. If specified: Make sure that the specified security group allows the CIDR block of the VPC where the Supabase instance resides in both the inbound and outbound directions. Otherwise, network connectivity issues may occur. Important The endpoint is created only once. When the first Supabase instance in a VPC enables the sandbox and Edge Routine function capabilities, the system performs automatic creation of the endpoint. When subsequent Supabase instances in the same VPC enable these capabilities, the existing endpoint is reused and no new endpoint is created. |
sg-bp179qkbvlj8ym***** |
| ClientToken |
string |
No |
The idempotency parameter. |
0c593ea1-3bea-11e9-b96b-88e9fe637760 |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
Schema of Response |
||
| RequestId |
string |
Id of the request |
FE9C65D7-930F-57A5-A207-8C396329**** |
| InstanceName |
string |
The instance ID of the AI application. |
ra-supabase-8moov5lxba**** |
Examples
Success response
JSON format
{
"RequestId": "FE9C65D7-930F-57A5-A207-8C396329****",
"InstanceName": "ra-supabase-8moov5lxba****"
}
Error codes
|
HTTP status code |
Error code |
Error message |
Description |
|---|---|---|---|
| 400 | IdempotentParameterMismatch | The request uses the same client token as a previous, but non-identical request. Do not reuse a client token with different requests, unless the requests are identical. | |
| 400 | IncorrectInstanceState | Current instance status does not support this operation. | The operation is not supported in the current instance state. |
| 400 | InvalidGroupName | Specified group name is not valid. | Invalid group name |
| 400 | InvalidParameter | The provided parameter is invalid. | Invalid parameter. |
| 400 | MissingServiceLinkedRole | %s. | |
| 404 | UserNotFound | User does not exist. | User does not exist. |
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.