- Product Introduction
- Supported Resource Types
- Purchase Guide
- Getting Started
- Operation Guide
- Resources
- Rule
- Managed Rules
- List of Managed Rule
- MFA on Sensitive Operations Required for CAM Users
- MFA on Login Required for CAM Users
- No Idle User Groups on CAM
- Association with User Group Required for CAM User
- No Authorization Policies Directly Added to CAM Sub-account
- No Administrator Access Permissions Granted to CAM Users, User Groups, or Roles
- Granting of Specific High-Risk Permissions by CAM Not Allowed
- No Idle Permission Policies on CAM
- CAM Login Permission Check
- Key of CAM User Rotated at Specified Interval
- Login by CAM User within Specified Time Range
- CVM Instance Associated with Specified Security Group
- CVM Instance Not Moved to Recycle Bin
- Association of CVM Instance with Specified Role
- CVM Instance Enabled Automatic Renewal
- Notification About Expiration for CVM Instance in Monthly Subscription or Pay-As-You-Go Mode
- No Idle Security Groups
- CVM Instance in VPC
- No CVM Instances Not Assigned to Project
- Inactive Duration of CVM Instance After Shutdown Not Exceeding Specified Number of Days
- Lease Duration of CVM Instance Meeting Requirement of Specified Number of Days
- CVM Instance Bound to IPv4 Public Address
- Specified Tag Existed for Resource
- Access to Remote Risky Ports by Security Group Not Allowed
- Access to All Ports by Security Group Not Allowed
- CBS Disk Enabled Arrear Protection
- CBS Disk Enabled Encryption
- Detachable CBS Disk Not Moved to Recycle Bin
- Number of Available IP Addresses in VPC Subnet Greater than Specified Value
- Expiration Protection for CVM Instance in Pay-As-You-Go Mode
- No Idle CBS Disks
- Using Rules
- Managing Rules
- Conformance Pack
- Settings
- API Documentation
- FAQs
- Contact Us
- Glossary
- Product Introduction
- Supported Resource Types
- Purchase Guide
- Getting Started
- Operation Guide
- Resources
- Rule
- Managed Rules
- List of Managed Rule
- MFA on Sensitive Operations Required for CAM Users
- MFA on Login Required for CAM Users
- No Idle User Groups on CAM
- Association with User Group Required for CAM User
- No Authorization Policies Directly Added to CAM Sub-account
- No Administrator Access Permissions Granted to CAM Users, User Groups, or Roles
- Granting of Specific High-Risk Permissions by CAM Not Allowed
- No Idle Permission Policies on CAM
- CAM Login Permission Check
- Key of CAM User Rotated at Specified Interval
- Login by CAM User within Specified Time Range
- CVM Instance Associated with Specified Security Group
- CVM Instance Not Moved to Recycle Bin
- Association of CVM Instance with Specified Role
- CVM Instance Enabled Automatic Renewal
- Notification About Expiration for CVM Instance in Monthly Subscription or Pay-As-You-Go Mode
- No Idle Security Groups
- CVM Instance in VPC
- No CVM Instances Not Assigned to Project
- Inactive Duration of CVM Instance After Shutdown Not Exceeding Specified Number of Days
- Lease Duration of CVM Instance Meeting Requirement of Specified Number of Days
- CVM Instance Bound to IPv4 Public Address
- Specified Tag Existed for Resource
- Access to Remote Risky Ports by Security Group Not Allowed
- Access to All Ports by Security Group Not Allowed
- CBS Disk Enabled Arrear Protection
- CBS Disk Enabled Encryption
- Detachable CBS Disk Not Moved to Recycle Bin
- Number of Available IP Addresses in VPC Subnet Greater than Specified Value
- Expiration Protection for CVM Instance in Pay-As-You-Go Mode
- No Idle CBS Disks
- Using Rules
- Managing Rules
- Conformance Pack
- Settings
- API Documentation
- FAQs
- Contact Us
- Glossary
Which cloud services and resource types does Config support?
Why are some resources not displayed in the resource list?
After you enable Config, set the monitoring scope, and manually update the resource snapshots, Config will update the information on all resources of the specified types. Due to the large data volume, Config will take about 15 minutes to pull the snapshots, generate records, and update resource configurations. Please wait patiently.
Why is the resource configuration information displayed by Config inconsistent with that in the console of the corresponding cloud service?
Information inconsistency may exist in the following situations:
1. Some resource configuration fields in the cloud service console are not included by Config. Therefore, the information of these fields will not be displayed in the Config console.
2. If the resource configuration fields in the cloud service console are included by Config, but the operation event of the configuration change fails to be reported to CloudAudit, then the configuration change cannot be captured by CloudAudit and Config. This results in information inconsistency.
3. If the data volume under the account is large, Config will take about 15 minutes to pull the snapshots, generate records, and update resource configurations before it displays the final information.
Why is the configuration change not included in the resource timeline?
After you modify the resource configuration, Config will monitor the change within 15 minutes. If you recover the original configuration within this period, Config may not generate a change record.
For how long can Config record the configuration data?
By default, Config records the resource information and configuration changes for a year. If you require a longer duration, you can create tracking sets to persistently store the configuration data. For more information, see Delivery Service.
What is the frequency of sending configuration records in the resource timeline from Config to COS?
Configuration records are sent to the COS bucket at 00:30 every day.
What can I do if I expect for more rules?
You can submit a ticket that contains the detailed description of the rule. For the rule format, see Supported Managed Rules. Tencent Cloud will decide whether to implement the rule as a managed rule by considering both Config and the corresponding cloud service.
Why evaluation based on the rule I set is not performed?
If the trigger mechanism is set to periodic execution, evaluation will be performed only at the set time.
If the trigger mechanism is set to trigger by configuration change, evaluation will be performed only when configuration changes are made on the resources bound to the rule.
You can manually perform re-evaluation based on the rule on the rule details page to quickly obtain the latest evaluation result.
Yes
No
Was this page helpful?