- 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
Accessing to Other Cloud Vendors
Scenarios
Cloud Operations Center allows you to configure accounts of other cloud vendors and synchronize resources from other clouds. Currently, the following clouds are supported: Alibaba Cloud and AWS. If you need to manage cloud resources of other cloud vendors through Cloud Operations Center, perform the following operations:
Precautions
Currently, accounts for Alibaba Cloud and AWS can be created.
After an account is added, synchronize existing resources of the account by referring to Synchronizing Resources.
If the resources of an existing account have changed, you need to synchronize the resources again.
Adding an Account of Another Cloud Vendor
- Log in to COC.
- In the navigation pane, choose Resources > Application and Resource Management.
- Click Multi-cloud Configurations in the upper right corner.
- Click the target cloud vendor.
- Click Add xxx Account.
Table 1 Parameters for adding an account Parameter
Description
Account ID
Account ID of the cloud vendor
Account Name
Account name of the cloud vendor
Access Key ID
Access key ID of the cloud vendor
Unique access key ID associated with the secret access key.
Secret Access Key
Enter the secret access key of the cloud vendor.
Secret access key used in conjunction with an AK to sign requests cryptographically. It identifies a request sender and prevents the request from being modified.
- Click OK.
The account is created.
Modifying an Account of Another Cloud Vendor
- Log in to COC.
- In the navigation pane, choose Resources > Application and Resource Management.
- Click Multi-cloud Configurations in the upper right corner.
- Select the target account and click Modify in the Operation column.
- Set parameters for modifying the account
Table 2 Parameters for modifying an account Parameter
Description
Account Name
Account name of the cloud vendor
Access Key ID
Access key ID of the cloud vendor
Unique access key ID associated with the secret access key.
Reuse Access Key Secret
Whether to reuse the secret access key.
If you select Yes, the latest secret access key is reused.
If you select No, enter a new secret access key.
Secret Access Key
Set this parameter only when Reuse Access Key Secret is set to Yes.
Enter the secret access key of the cloud vendor.
Secret access key used together with an AK to sign requests cryptographically. It identifies a request sender and prevents the request from being modified.
- Click OK.
The account is modified.
Deleting an Account of Another Cloud Vendor
- Log in to COC.
- In the navigation pane, choose Resources > Application and Resource Management.
- Click Multi-cloud Configurations in the upper right corner.
- Locate the target account and click Delete in the Operation column.
- Click OK.
Account deletion is complete.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.