[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["没有我需要的信息","missingTheInformationINeed","thumb-down"],["太复杂/步骤太多","tooComplicatedTooManySteps","thumb-down"],["内容需要更新","outOfDate","thumb-down"],["翻译问题","translationIssue","thumb-down"],["示例/代码问题","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-12。"],[],[],null,["# Choose your locations\n\n| **Note:** This page includes instructions about Alibaba products. Google doesn't guarantee that this guidance is up to date or that the sample configuration choices are ideal for your use case. For the most current information, refer to the [Alibaba Cloud documentation](https://www.alibabacloud.com/help/) .\n\nWhen you use Cross-Cloud Interconnect, Google provisions physical connections on your\nbehalf between the Google Cloud network and the Alibaba Cloud network.\n\nBefore Google can establish these connections, you must order ports from both Google and\nAlibaba. In preparation for that process, identify the Google Cloud locations\nand the corresponding Alibaba locations that you want to use for your connections.\n\nBest practices for selecting a location\n---------------------------------------\n\nWhen deciding where to place your connections, consider questions such as the following:\n\n- Where are most of your Google Cloud resources?\n- Where are most of your Alibaba resources?\n\nIf your resources from both clouds are in the same place, then the choice is simple.\nHowever, if they are not, consider whether you want your connections to be closer to your\nGoogle Cloud resources or closer to your Alibaba resources. If the connections\nare closer to your Alibaba resources, then your traffic spends more time\ntraveling on the Google network, which in general is desirable. However, you should also consider\nthe outbound data transfer costs that you're likely to incur from both clouds.\n\nFactors affected by location\n----------------------------\n\nThis section describes factors that are affected by your location choice.\n\n### VLAN attachments\n\n\nAfter your Cross-Cloud Interconnect connection is established, you must configure\nVLAN attachments in Google Cloud. A VLAN attachment is a\nlogical connection between your remote cloud network and a single region in your\nVirtual Private Cloud (VPC) network.\n\nWhen you choose a location for your ports, you limit the number of regions where you can place\nboth VLAN attachments and Express Connect virtual circuits. For this reason, the supported locations\ntable includes a column for the Google Cloud and Alibaba Cloud regions that are served by each port\nlocation.\n\n\u003cbr /\u003e\n\n| **Note:** In Google Cloud, the location of the VLAN attachment\n| doesn't have to limit which Google Cloud regions receive your Alibaba routes.\n| To advertise Alibaba routes to all of your Google Cloud regions, configure\n| [global\n| dynamic routing](/network-connectivity/docs/interconnect/how-to/cci/alibaba/network-connectivity/docs/router/concepts/learned-routes#dynamic-routing-mode-effects-on-learned-routes).\n\n### Edge availability domains\n\nEach metropolitan area has two Google Cloud edge availability domains. Two domains in the\nsame metropolitan area are not scheduled to be down for maintenance at the same time. For this\nreason, when you select a location for a primary and redundant port,\neach port must use a different edge availability domain within the same metropolitan area. This is\ntrue regardless of how you order your ports. However, when you use the Google Cloud CLI, you\nmust specify each edge availability domain explicitly. When you use the Google Cloud console, you\nsimply select a location, and Google Cloud reserves a port for you in each domain.\n\nIn the gcloud CLI version of the location name, the edge availability domain is the\nsecond piece of information. For example, if the location name is `iad-zone1-1`,\nthe edge availability domain is `zone1`. If the location name is\n`iad-zone2-1`, the edge availability zone is `zone2`.\n\n### Colocation facilities\n\n\nGoogle typically provisions each connection within a single colocation facility. However, sometimes\nconnections are created between adjoining facilities that are operated by the same provider. In\neither case, generally you don't need to know the facility name. For this reason, the supported\nlocations table does not identify specific facilities.\n\nList of supported locations\n---------------------------\n\nThe following table lists the supported Alibaba locations and the corresponding\nGoogle Cloud locations.\n\nYou must specify the Google Cloud location of your Cross-Cloud Interconnect\nport, and additionally specify where in your other cloud provider to connect it. This latter\nAlibaba location is referred to as the *remote location* in this documentation\nset and within Google Cloud. Make sure to use the remote location name\nwhen you order the Cross-Cloud Interconnect. Your remote cloud provider has a different,\nalthough similar, name for the location, which you use when you order the port with that\ncloud provider.\n\nFor each location name, some syntax variations exist. For example:\n\n- The remote location name varies depending on whether you are interacting with Alibaba or Google Cloud.\n- When interacting with Google Cloud, the Google Cloud console displays the remote location *description* next to the location name to help you choose the correct location.\n- In Google Cloud, the Google Cloud console Cloud Interconnect location (not the remote location) shows facility information rather than the actual Cloud Interconnect location name.\n\n| **Note:** You can also use the gcloud CLI to list locations.\n| For more information, see the reference page for the\n| [`gcloud compute interconnects remote-locations list` command](/sdk/gcloud/reference/compute/interconnects/remote-locations/list).\n| **Note:** For the most up-to-date information about Alibaba Cloud locations, see [Alibaba Cloud Regions](https://www.alibabacloud.com/global-locations) in the Alibaba Cloud documentation.\n\nVerify availability\n-------------------\n\nAfter you've identified a location that you want to use, double-check that it has an available\n10-Gbps or 100-Gbps Express Connect port. This step is helpful because the availability\nof ports can change without notice.\n\nNote locations and regions\n--------------------------\n\nAfter you've reviewed the previous sections, make a note of the following values:\n\n- The remote location, as it's known in Google Cloud, and the Google Cloud location. You need these values when you [order your Cross-Cloud Interconnect connections](/network-connectivity/docs/interconnect/how-to/cci/alibaba/order-google-connections).\n- The remote location, as it's known in Alibaba Cloud, and the region where you want to place the connection resources. You need these values when you [order your Alibaba Cloud ports](/network-connectivity/docs/interconnect/how-to/cci/alibaba/order-alibaba-ports) and [configure your Alibaba Cloud resources.](/network-connectivity/docs/interconnect/how-to/cci/alibaba/configure-alibaba)\n- The Google Cloud region where you want to place your VLAN attachments. You need this value when you create the attachment, as described in [Configure your Google Cloud resources](/network-connectivity/docs/interconnect/how-to/cci/alibaba/configure-google-resources)."]]
