Team quota management

Environment variables

Configure the access credentials as described in Alibaba Cloud SDK and API guide. Pass them in through environment variables instead of writing them into code, images, templates, or logs. The examples in this topic read the following environment variables:

Set or update a quota

UpdateQuota both sets a quota and updates an existing configuration. Before you run the example, change the CPU, memory, and live instance values to the target values. If a quota already exists, query the current configuration before you update it.

Set the parameters in a terminal in which the access credentials are configured. The following example uses the China (Beijing) region:

export SANDBOX_REGION_ID="cn-beijing"
export SANDBOX_ENDPOINT="sandbox.cn-beijing.aliyuncs.com"
export SANDBOX_TEAM_ID="<TEAM-ID>"

Save the following code as main.go. This example sets the quota of the specified Team to 32 CPU cores, 64 GB of memory, and 16 live instances:

package main

import (
    "encoding/json"
    "fmt"
    "log"
    "os"
    "strings"

    openapiutil "github.com/alibabacloud-go/darabonba-openapi/v2/utils"
    sandbox "github.com/alibabacloud-go/sandbox-20260820/client"
    "github.com/alibabacloud-go/tea/tea"
)

func requireEnv(name string) string {
    value := strings.TrimSpace(os.Getenv(name))
    if value == "" {
        log.Fatalf("Set %s", name)
    }
    return value
}

func printJSON(value interface{}) {
    data, err := json.MarshalIndent(value, "", "  ")
    if err != nil {
        log.Fatal(err)
    }
    fmt.Println(string(data))
}

func main() {
    client, err := sandbox.NewClient(&openapiutil.Config{
        AccessKeyId:     tea.String(requireEnv("ALIBABA_CLOUD_ACCESS_KEY_ID")),
        AccessKeySecret: tea.String(requireEnv("ALIBABA_CLOUD_ACCESS_KEY_SECRET")),
        SecurityToken:   tea.String(os.Getenv("ALIBABA_CLOUD_SECURITY_TOKEN")),
        RegionId:        tea.String(requireEnv("SANDBOX_REGION_ID")),
        Endpoint:        tea.String(requireEnv("SANDBOX_ENDPOINT")),
    })
    if err != nil {
        log.Fatal(err)
    }

    // Set or update the quota.
    resp, err := client.UpdateQuota(&sandbox.UpdateQuotaRequest{
        Body: &sandbox.Quota{
            TagValue:      tea.String(requireEnv("SANDBOX_TEAM_ID")),
            CpuCores:      tea.Int32(32),
            MemoryGB:      tea.Int32(64),
            InstanceCount: tea.Int32(16),
        },
    })
    if err != nil {
        log.Fatalf("set quota failed: %v", err)
    }
    printJSON(resp.Body)
}

Run the code in a Go project in which the SDK is installed:

go run main.go

The response contains the saved quota and the request ID. To adjust the quota again, change the target values in sandbox.Quota and call the same API operation.

The following query, list, and delete examples reuse the imports, helper functions, and client initialization code above. Replace the operation code after the "Set or update the quota" comment in main with the corresponding example. You do not need to run the update operation before you query or delete a quota.

Query a quota

Call DescribeQuota to query the quota of a specified Team:

resp, err := client.DescribeQuota(&sandbox.DescribeQuotaRequest{
    TagValue: tea.String(requireEnv("SANDBOX_TEAM_ID")),
})
if err != nil {
    log.Fatalf("describe quota failed: %v", err)
}
printJSON(resp.Body)

Query the quota list

Call ListQuota to query the quotas of the account a page at a time:

var nextToken *string
for {
    resp, err := client.ListQuota(&sandbox.ListQuotaRequest{
        MaxResults: tea.Int32(100),
        NextToken:  nextToken,
    })
    if err != nil {
        log.Fatalf("list quota failed: %v", err)
    }
    printJSON(resp.Body)

    nextToken = resp.Body.NextToken
    if tea.StringValue(nextToken) == "" {
        break
    }
}

ListQuota queries the quotas of the current account in the target region, and does not filter by SANDBOX_TEAM_ID. To query the quota of a specified Team, call DescribeQuota.

Delete a quota

After you confirm that the Team no longer needs this quota configuration, run the delete operation separately:

resp, err := client.DeleteQuota(&sandbox.DeleteQuotaRequest{
    TagValue: tea.String(requireEnv("SANDBOX_TEAM_ID")),
})
if err != nil {
    log.Fatalf("delete quota failed: %v", err)
}
printJSON(resp.Body)

After the deletion, call DescribeQuota to check whether the configuration still exists. A response of ResourceQuotaNotFound indicates that the quota configuration is not found.

What do I set tagValue to?

Set it to the ID of the target Team. Do not set it to the Team name, the resource group ID, or an API key. For more information about how to obtain the Team ID, see Create a Team.

Why does the system report an invalid parameter when I set a quota?

If InvalidParameter is returned, check the format of the Team ID, whether both the CPU and memory fields are specified, and whether the two values are non-negative integers. If you pass instanceCount, the value must be an integer that is not less than -1.

Why does the system report that I do not have the permission to call quota operations?

Check the RAM permissions and the resource scope of the calling identity. Querying the quota list of the account requires sandbox:ListQuotas, and setting a quota requires sandbox:UpdateQuota. For the authorization details, see Authorize RAM users to access the console. If the error message indicates that the feature is not activated, contact technical support to confirm the activation conditions of the target region and account.

Why does the system report that the account quota is exceeded when I set a quota?

Check the error message to determine whether the exceeded item is CPU, memory, or another quota item. Next, review the account quota and the quotas already configured for other Teams. If the CPU or memory quota is insufficient, reallocate the quota among Teams or request an increase in the corresponding account quota.

If the quota that you set exceeds the account quota, the request may return errors such as LimitExceededError. Evaluate the result based on the returned HTTP status code, error code, and message. Do not identify a quota overrun only by HTTP status code 429.

Why does the system report that the quota does not exist when I query a quota?

If ResourceQuotaNotFound is returned, verify the account, region, and Team ID, and check whether the Team has a quota configured and whether you deleted the quota. If TeamNotFound is returned, check whether the Team exists in the target region.

How do I troubleshoot a failed request?

Record the error message and the request ID. Check whether the access credentials are valid and whether the region and endpoint are consistent. If you use STS temporary credentials, make sure that the AccessKey ID, AccessKey secret, and security token come from the same set of credentials and have not expired. Fix parameter, permission, or quota issues before you retry the request.