Config Audit (Config) helps you centrally audit and govern Tencent Cloud resources. It continuously records and evaluates the configuration information and change operations of various cloud resources scattered across each region under your account, thereby helping you implement autonomous resource supervision and standard OPS efficiently.
The Config API interfaces described in this chapter are all API 3.0 interfaces.
You can call the API to perform operations on Config, such as viewing resource details and retrieving rule lists.
For information on all APIs supported by Config, see API overview.
Common terminology for Config API interfaces: see the table below.
| Terminology | Description |
|---|---|
| Resource Type | A group of entity resources with identical features under the same cloud service, with a dedicated resource type name in the six-segment resource format. For example, entity resources such as compute instances and storage instances, and management resources such as roles and policies. |
| Associated resource | An associated resource is a resource that has an association relationship with the current resource. |
| Resource Timeline | Refers to the whole lifecycle data of a resource, including its configuration information, configuration change information, operations on the resource (addition, deletion, and edition), and compliance evaluation result. |
| Configuration item | A collection of various Attribute information of a resource at a certain point in time, consisting of Metadata, resource attributes, associated resources, and detailed Configuration information. |
| Rule | A rule function used to judge whether resource configurations are compliant. Config audit uses functions to carry rule code. |
| Managed rules | Rules predefined by Config Audit. When creating a rule, you can select the target managed rule in the Config Audit console. |
| Compliance evaluation result | The result of evaluating associated resources by a rule pair at a certain point in time. |
| Compliance package | A collection of rules customized based on compliance scenarios. It is divided into system pre-set compliance pack templates and user-defined compliance packages. |
| Restriction item | Description |
|---|---|
| Rule | A single account can evaluate up to 100 times per rule each day. |
| Compliance package | A root account can create a maximum of 5 compliance packages. A compliance package allows up to 20 rules. |
| Bucket | A root account allows up to 1 bucket for shipping. |
| Enable/Disable service | You can enable/disable the service up to 5 times daily. |
| Modify monitoring scope | Up to 5 modifications of the monitored resource type are allowed each day. |
| Manual update of resource snapshot | A maximum of 5 manual updates are allowed per day. |
You can use the API Explorer tool to call APIs online.
This document uses querying whether the resource assessment result is compliant as an example. The steps to make an API call through the API Explorer Tool are as follows:
At this point, you can query whether the resource assessment result is compliant.
Esta página foi útil?
Você também pode entrar em contato com a Equipe de vendas ou Enviar um tíquete em caso de ajuda.
comentários