- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- Permissions Management
- Enterprise Routers
- Attachments
- Route Tables
- Associations
- Propagations
- Routes
-
Routing Control
-
Route Policies
- Route Policy Overview
- Creating a Route Policy
- Associating a Route Policy with an Enterprise Router
- Changing the Route Policy Associated with an Enterprise Router
- Disassociating a Route Policy from an Enterprise Router
- Modifying a Route Policy
- Viewing a Route Policy
- Deleting a Route Policy
- Adding a Policy Node to a Route Policy
- Modifying a Policy Node in a Route Policy
- Exporting Policy Nodes in a Route Policy
- Viewing a Policy Node in a Route Policy
- Deleting a Policy Node from a Route Policy
-
IP Prefix Lists
- IP Prefix List Overview
- Creating an IP Prefix List
- Modifying the Name of an IP Prefix List
- Viewing an IP Prefix List
- Deleting an IP Prefix List
- Adding a Prefix Rule to an IP Address Prefix List
- Modifying an IP Prefix Rule in an IP Prefix List
- Exporting Prefix Rules in an IP Prefix List
- Viewing a Prefix Rule in an IP Prefix List
- Deleting a Prefix Rule from an IP Prefix List
-
AS_Path Lists
- AS_Path List Overview
- Creating an AS_Path List
- Modifying the Name of an AS_Path List
- Viewing an AS_Path List
- Deleting an AS_Path List
- Adding an AS_Path Filter to an AS_Path List
- Exporting AS_Path Filters in an AS_Path List
- Viewing an AS_Path Filter in an AS_Path List
- Deleting an AS_Path Filter from an AS_Path List
-
Route Policies
- Sharing
- Flow Logs
- Monitoring and Auditing
- Tags
- Quotas
-
Best Practices
- Summary on Enterprise Router Best Practices
- Connecting VPCs Across Regions Using Enterprise Router and Central Network
- Using Enterprise Router to Isolate VPCs in the Same Region
- Using a Third-Party Firewall to Protect VPCs Connected by Enterprise Routers
- Enabling an On-Premises Data Center to Access Service VPCs Using an Enterprise Router and Transit VPC
- Setting Up a Hybrid Cloud Network Using Enterprise Router and Direct Connect Global DC Gateway
-
Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Direct Connect Connections (Global DC Gateway)
- Overview
- Network and Resource Planning
- Process of Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Direct Connect Connections (Global DC Gateway)
- Procedure for Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Direct Connect Connections (Global DC Gateway)
-
Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Active/Standby Direct Connect Connections (Global DC Gateway)
- Overview
- Network and Resource Planning
- Process of Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Active/Standby Direct Connect Connections (Global DC Gateway)
- Procedure for Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Active/Standby Direct Connect Connections (Global DC Gateway)
- Setting Up a Hybrid Cloud Network Using Enterprise Router, VPN, and Direct Connect (Global DC Gateway)
- Setting Up a Hybrid Cloud Network Using Enterprise Router and Direct Connect (Virtual Gateway)
- Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Direct Connect Connections (Virtual Gateway)
- Setting Up a Hybrid Cloud Network Using Enterprise Router, VPN, and Direct Connect (Virtual Gateway)
- Allowing VPCs to Share an EIP to Access the Internet Using Enterprise Router and NAT Gateway
- Using Enterprise Router to Migrate the Network Set Up Through VPC Peering
- Using Enterprise Router to Migrate the Network Set Up Through Direct Connect (Global DC Gateway)
- Using Enterprise Router and Central Network to Migrate the Network Set Up Through a Cloud Connection
- API Reference
- FAQs
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Service Overview
- Getting Started
- Enterprise Routers
- Attachments
- Route Tables
- Associations
- Propagations
- Routes
- Sharing
- Flow Logs
- Monitoring
- Interconnecting with CTS
- Permissions Management
- Tags
- Quotas
- FAQ
- Change History
-
User Guide (Ankara Region)
- Service Overview
- Getting Started
- Permissions Management
- Enterprise Routers
- Attachments
- Route Tables
- Associations
- Propagations
- Routes
- Sharing
- Flow Logs
- Monitoring
- Quotas
- FAQ
- Change History
- API Reference (Ankara Region)
-
User Guide (ME-Abu Dhabi Region)
- General Reference
Copied.
Sharing Overview
What Is Sharing?
- You are the owner of the enterprise router.
- Other accounts are the users of the enterprise router.
After you share your enterprise router with other accounts, these other users can attach their network instances to your enterprise router, so that their network instances can access your enterprise router.
You can share an enterprise router in your account with other accounts so that these other accounts can attach their VPCs to your enterprise router.
This example uses account A, account B, and account C to describe how you can build a network using one enterprise router. Table 1 describes the resources of each account.
If account A shares enterprise router (ER-A) with account B and account C, the VPCs of accounts B and C can be attached to ER-A. Figure 1 shows the networking.
Allowed Operations by the Owner and Other Users
Role |
Allowed Operation |
Description |
---|---|---|
Other users (user accounts) |
Other users can view: The name of the shared enterprise router followed by Shared with me. |
|
Adding attachments to an enterprise router |
Other users:
For details about the process for creating an attachment for an enterprise router in another account, see Sharing an Enterprise Router with Other Users. |
|
Other users: |
||
Other users can change the names of their attachments created for the shared enterprise router. |
||
Other users can delete their attachments created for the shared enterprise router without the approval of the owner account. |
Other users cannot view Route Tables, Sharing, and Flow Logs of the enterprise router.
Sharing an Enterprise Router with Other Users
- If Auto Accept Shared Attachments is not enabled on your enterprise router, you must accept the attachment creation requests from other users.
Figure 2 Accepting or rejecting attachment creation requests
Table 3 Process description No.
Step
Role
Description
1
Owner
The owner creates a sharing to share an enterprise router with another user. This user can easily identify the shared enterprise router because its name is followed by Shared with me.
2
User
The user creates an attachment to the shared enterprise router. The attachment will be in the Pending acceptance state because Auto Accept Shared Attachments is disabled on the enterprise router.
3
Owner
- The owner accepts the attachment request. The attachment status changes from Pending acceptance to Creating.
- When the attachment status changes to Normal, the attachment is successfully created.
- When the attachment status changes to Failed, the attachment fails to be created. Contact technical support.
After an attachment is created, you can perform Follow-up Procedure.
- The owner can also reject the attachment request. If the owner rejects the request, the attachment status changes from Pending acceptance to Rejected, and the attachment fails to be created. If this happens, contact the owner.
- The owner accepts the attachment request. The attachment status changes from Pending acceptance to Creating.
- If Auto Accept Shared Attachments is enabled on an enterprise router, the other users' requests to create attachments to this enterprise router will be automatically accepted without the approval from the owner.
Figure 3 Attachment requests automatically accepted
Table 4 Process description No.
Step
Role
Description
1
Owner
The owner creates a sharing to share an enterprise router with another user. This user can easily identify the shared enterprise router because its name is followed by Shared with me.
2
User account
Auto Accept Shared Attachments is enabled on the enterprise router.
The user creates an attachment to the shared enterprise router. The attachment will be in the Creating state.- When the attachment status changes to Normal, the attachment is successfully created.
- When the attachment status changes to Failed, the attachment fails to be created. Contact technical support.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot