- Service Overview
- Getting Started
-
User Guide
- COC Enablement and Permissions Granting
- Overview
-
Resources
- Resource Management
-
Application Management
- Overview
- Creating an Application
- Modifying an Application
- Deleting an Application
- Application Topology
- Creating a Component
- Modifying a Component
- Deleted a Component
- Creating a Group
- Modifying a Group
- Deleting a Group
- Manually Associating with Resources
- Automatically Associating with Resources
- Transferring Resources
- Disassociating Resources from an Application Group
- Viewing Resource Details
- Viewing Capacity Details
- Resource O&M
- Automated O&M
-
Faults
- Diagnosis Tools
- Alarms
-
Incident Management
- Incidents
- Creating an Incident
- Rejecting an Incident
- Resubmitting an Incident After Rejection
- Forwarding Incidents
- Handling Incidents
- Upgrading/Downgrading an Incident
- Adding Remarks
- Starting a War Room
- Handling an Incident
- Verifying Incident
- Creating an Improvement Ticket For An Incident
- Incident History
- WarRoom
- Improvement Management
- Issue Management
- Forwarding Rules
- Data Source Integration Management
- Change Management
- Resilience Center
- Task Management
- Basic Configurations
- Viewing Logs
- Best Practices
- API Reference
-
FAQs
- Product Consulting
- Resource Management FAQs
-
FAQs About Resource O&M
-
Patch Management FAQs
- What Can I Do If the Patch Baselines Do Not Take Effect?
- What Are the Differences Between the Installation Rule Baselines And User-defined Baselines?
- What Can I Do If Exception all mirrors were tried Is Recorded in the Patch Service Ticket Log?
- Why Can't I Select a Node?
- What Can I Do If the Compliance Report Still Reports Non-compliance for a Patch After the Patch Has Been Repaired?
- What Can I Do If the lsb_release not found Error Occurs During Patch Operations?
- Automation FAQs
- Batch Operation FAQs
- FAQs About Parameter Management
- Resource O&M Permissions and Supported Actions
-
Patch Management FAQs
- FAQs About Fault Management
- FAQs About Change Ticket Management
- Resilience Center FAQs
- Change History
Synchronizing Resources
Scenarios
If resource data is not refreshed in time, you can manually synchronize resource data to ensure real-time and reliable data.
A resource is an entity that you can use on the cloud platform. A resource can be an Elastic Cloud Server (ECS), an Elastic Volume Service (EVS) disk, or a Virtual Private Cloud (VPC).
To synchronize resources, you must have the rms:resources:list permission. This permission is used to call RMS APIs to obtain resources in all regions to which the current user belongs.
Precautions
The duration of the resource synchronization tasks depends on the total amount of resource data being synchronized. The maximum synchronization time is approximately 5 minutes.
Synchronizing Resources
- Log in to COC.
- In the navigation pane, choose Resources > Application and Resource Management.
- Select the cloud vendor whose resources are to be synchronized.
Huawei Cloud is selected by default.
NOTE:
- To synchronize resources of other cloud vendors, add accounts of other cloud vendors in the multi-cloud configuration. For details, see Accessing to Other Cloud Vendors.
- Prerequisites for synchronizing Alibaba Cloud resources:
- Prerequisites for synchronizing AWS resources:
- The master account must enable the Config service.
Access the Config service, select the Region where resources are to be synchronized, and enable the Config service in one click.
- Add actions to the account corresponding to the AK/SK.
Create a policy: Access the IAM service, create a policy on the policy page. Select the EC2 service, filter operations and select DescribeRegions, add the Config service, filter operations and select SelectResourceConfig and BatchGetResourceConfig, click Next and create the policy.
Add a policy to a user: On the IAM console, click user and add permission, select the policy created in the previous step, and click Next to complete permissions adding.
- The master account must enable the Config service.
- Select the account to which the resources to be synchronized belong.
By default, My Resources is selected.
- Select the resource type to be synchronized.
By default, Elastic Cloud Server (ECS) is selected.
- Click
on the right of the filter box.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.