Enables a flow log. After the flow log is enabled, traffic information about a resource is captured.
Operation description
-
The ActiveFlowLog operation is asynchronous. After you send the request, the system returns a request ID. However, the operation is still being performed in the system background. You can call the DescribeFlowLogs operation to query the status of a flow log:
- If the flow log is in the Activating state, the flow log is being started.
- If the flow log is in the Active state, the flow log is started.
-
You cannot repeatedly call the ActiveFlowLog operation to start a flow log within the specified period of time.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action
policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resources
is used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
Operation | Access level | Resource type | Condition key | Associated operation |
---|---|---|---|---|
vpc:ActiveFlowLog | update | *FlowLog acs:vpc:{#regionId}:{#accountId}:flowlog/{#FlowLogId} |
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
RegionId | string | Yes | The ID of the region where you want to create the flow log. You can call the DescribeRegions operation to query the most recent region list. | cn-qingdao |
FlowLogId | string | Yes | The ID of the flow log. | fl-m5e8vhz2t21sel1nq**** |
Response parameters
Examples
Sample success responses
JSON
format
{
"Success": "true",
"RequestId": "F7DDDC17-FA06-4AC2-8F35-59D2470FCFC1"
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | IncorrectBusinessStatus.FlowLog | The business status of flowLog is incorrect. | - |
400 | InvalidInstanceId | Instance does not exist. | The error message returned because the specified instance does not exist. |
400 | InvalidStatus | Current instance status is not valid for this action. | - |
400 | InvalidRegionId.NotFound | The RegionId provided does not exist in our records. | The RegionId parameter is set to an invalid value. Specify a valid value and try again. |
400 | InvalidInstanceId.NotFound | The specfied instance is not existed. | - |
400 | IncorrectStatus.flowlog | Invalid flowlog status. | The flow log cannot be disabled because it is in an invalid state. |
400 | Forbidden.OperateManagedFlowLog | Authentication is failed for operate managed flowlog. | Authentication failed when operating the managed flow log. |
400 | OperationDenied.FlowLogDeliverFailed | The operation is not allowed due to an invalid delivery address. | The flow log cannot be started because the delivery address is invalid. |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2023-08-30 | API Description Update. The API operation is not deprecated.. The Error code has changed | View Change Details |
2023-07-06 | The Error code has changed | View Change Details |