[[["容易理解","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"]],["上次更新時間:2025-08-12 (世界標準時間)。"],[],[],null,["# Order AWS ports\n\n| **Note:** This page provides sample guidance. Google doesn't guarantee that this guidance is up to date or that the sample configuration choices are ideal for your use case. For detailed instructions, see the [AWS documentation](https://docs.aws.amazon.com/) .\n\nAfter you've ordered your Cross-Cloud Interconnect connections, order\nyour AWS ports.\n\nOrder your ports\n----------------\n\nAWS offers two *Direct Connect* ordering options: Link Aggregation Group (LAG)s\nand *connections* . (In the AWS interface, links are known as *connections* .) You\nmust order LAGs, not *connections* . LAGs enable\n[Link Aggregation Control Protocol (LACP)](https://en.wikipedia.org/wiki/Link_aggregation),\nwhich permits multiple links per port. Cross-Cloud Interconnect\nfor AWS requires LACP.\n\nOrder one LAG for each Cross-Cloud Interconnect connection.\n| **Caution:** For a redundant pair of Cross-Cloud Interconnect connections, perform the LAG ordering process below twice.\n\nDo not enter `2` for the number of connections within a single LAG if you\nactually want a redundant pair of LAGs, each having one link.\n\nAlthough LAGs enable bundling a group of connections together for higher\nbandwidth, you can create a LAG with just one connection.\n\nIf you accidentally ordered *connections* instead of LAGs, you can create a LAG\nfrom the existing *connections* by following the instructions on the\n[Create a LAG](https://docs.aws.amazon.com/directconnect/latest/UserGuide/create-lag.html)\npage in the AWS documentation, and then clicking the **Create a LAG with existing\nconnections using the console** tab. \n\n### AWS console\n\n| **Note:** For the most up-to-date information about how to order LAGs, see [Create a LAG](https://docs.aws.amazon.com/directconnect/latest/UserGuide/create-lag.html) in the AWS documentation.\n\n1. Go to the Direct Connect **LAGs** page.\n\n2. Click **Create LAG**.\n\n3. In the **LAG type** section of the page, select\n **Request new connections**.\n\n4. Fill out the **LAG settings** section of the page:\n\n - Enter a **LAG Name** for the resource.\n - In the **Location** field, enter the AWS location. If you need help with choosing a value for this field, see [Supported locations](/network-connectivity/docs/interconnect/how-to/cci/aws/choose-locations#supported-locations). You can find the location name below each listed location description. You can also search for a location name by using the search field in the **LAG settings** section.\n - Select the appropriate **Port speed**.\n - Enter the **Number of new connections** that you want.\n\n | **Note:** Set this field to reflect the number of links in this LAG. *Setting the number of new connections to `2` does not set up redundancy.* To set up redundancy, order two LAGs by following the LAG ordering process *twice*.\n - Clear the field labeled **Connect through an AWS Direct Connect partner**.\n5. Click **Create LAG**.\n\n### AWS CLI\n\nTo order your Direct Connect ports, use the\n[`create-lag` command](https://docs.aws.amazon.com/cli/latest/reference/directconnect/create-lag.html).\nFor example: \n\n```\naws directconnect create-lag \\\n --number-of-connections NUMBER_OF_CONNECTIONS \\\n --connections-bandwidth CAPACITY \\\n --location AWS_LOCATION \\\n --lag-name NAME \\\n --region REGION\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eNUMBER_OF_CONNECTIONS\u003c/var\u003e: the number of links, or connections, that you want for each port\n- \u003cvar translate=\"no\"\u003eCAPACITY\u003c/var\u003e: the bandwidth of each connection in the LAG\n- \u003cvar translate=\"no\"\u003eAWS_LOCATION\u003c/var\u003e: the name of the AWS location---for example, `EqFA5`\n- \u003cvar translate=\"no\"\u003eNAME\u003c/var\u003e: the name of the new LAG\n- \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e: the region where you want to place your new connection and its links\n\nGenerate an LOA\n---------------\n\nFor Google to provision your connection, it must have a letter of authorization\n(LOA) for each connection that you created in each AWS LAG.\n\nFor example, suppose you ordered two LAGs and you created two connections in\neach LAG. In this case, you need four LOA documents.\n\nUse the following instructions twice---once for each LAG. \n\n### AWS console\n\n\u003cbr /\u003e\n\nTo download the LOAs, complete the following steps:\n\n1. Go to the Direct Connect **LAGs** page.\n\n2. Click the name of the appropriate LAG.\n\n3. Go the **Connections** section of the page and do the following\n for each connection in the LAG:\n\n - Click the name of the connection to display the connection page.\n - Click **Download LOA**.\n - In the **Provider name - optional** field, enter **Google-Cloud**.\n - Click **Download**.\n4. Repeat step 3 for your redundant LAG.\n\n### AWS CLI\n\n\u003cbr /\u003e\n\nTo download the LOAs, complete the following steps:\n\n1. Use the\n [`aws directconnect describe-lags` command](https://docs.aws.amazon.com/cli/latest/reference/directconnect/describe-lags.html)\n to retrieve identifiers for the LAGs that you created. For example:\n\n ```\n aws directconnect describe-lags \\\n --region REGION |\n jq -r \\ '.lags[].connections[].connectionId'\n ```\n\n Replace \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e with the region where your connections\n are located.\n\n In response, the system returns an identifier for each connection.\n2. For each connection in the LAG, download the LOA by using the\n [`aws directconnect describe-loa` command](https://docs.aws.amazon.com/cli/latest/reference/directconnect/describe-loa.html).\n For example:\n\n ```\n aws directconnect describe-loa \\\n --connection-id CONNECTION_ID \\\n --provider-name \"Google-Cloud\" \\\n --output text \\\n --query loaContent \\\n --region REGION |\n base64 --decode \u003e FILE_NAME.pdf\n ```\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eCONNECTION_ID\u003c/var\u003e: the identifier of the connection\n - \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e: the region where your connections are located\n - \u003cvar translate=\"no\"\u003eFILE_NAME\u003c/var\u003e: a name for the LOA document\n3. Repeat step 2 for your redundant LAG.\n\nSend the LOAs to Google\n-----------------------\n\nAfter you order your Cross-Cloud Interconnect connections, you\nshould receive confirmation email messages from Google. Each of these\nmessages includes instructions for sending your AWS LOAs to Google. Now that\nyou have the LOAs, do the following:\n\n- Decide which AWS LAG you want to connect to each\n Cross-Cloud Interconnect port. Locate the LOA documents for\n that LAG.\n\n- Respond to each Google email. Each email represents a different\n Cross-Cloud Interconnect port. Attach the LOA documents\n for the AWS LAG that you want connected to that port.\n\n | **Caution:** Make sure to attach the correct LOA documents to the correct email. Errors in this step cause unintended port connections, which can result in configuration errors and connection delays.\n\nMake a note of the instructions that you provide to Google regarding which\nCross-Cloud Interconnect port connects to which AWS LAG. You need this\ninformation later in the process when you configure your AWS resources.\n\nStill later, after Google has provisioned your\nCross-Cloud Interconnect connections, you receive another set of\nemails stating that the connections are ready to use.\n\nAfter you receive this confirmation, you can finish the required\nconfiguration."]]