Function Compute:CLI-based instance management

Usage notes

• You can run commands only on active instances, which include long-running provisioned instances and active on-demand instances. If an on-demand instance is released or in an unhealthy state and is about to be destroyed, you may not be able to log on to the instance to perform operations.

• CLI-based management requests do not occupy the concurrency quota of an instance. Even if the instance concurrency of a function is set to 1, you can invoke the function and perform CLI-based operations on instances of the function at the same time.

• Each command that you run on an instance is considered as a function invocation. If you establish a WebSocket connection to an instance for CLI-based management, the instance stays active until you terminate the connection. You are charged based on the metering rules for regular function invocations. If you connect to an instance from the Function Compute console for CLI-based management, the instance is automatically disconnected 10 minutes after the last piece of data is transferred from the Function Compute console.

• If you use a custom image in a Custom Container runtime, make sure that the container contains the /bin/bash or /bin/sh directory. Otherwise, the instance client cannot be started.

Before you start

• Creates a function

• Activate Simple Log Service

Procedure

1. Log on to the Function Compute console. In the left-side navigation pane, click Functions.

2. In the top navigation bar, select a region. On the Functions page, click the function that you want to manage.

3. On the function details page, click the Instances tab.

4. In the instance list, find the instance that you want to manage and click Connect in the Actions column.

5. In the message that appears, read the message. Then, click I understand the risks.

   You are redirected to the CLI page of the instance. You can run commands based on your business requirements.