[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-05 (世界標準時間)。"],[[["\u003cp\u003eThis documentation is specifically for Apigee and does not apply to Apigee hybrid.\u003c/p\u003e\n"],["\u003cp\u003eUsers can choose to configure their new Apigee instance for either external or internal access to API proxies.\u003c/p\u003e\n"],["\u003cp\u003eSelecting "Enable internet access" allows external requests to the API proxy and is the recommended approach by Apigee, which deploys a "Hello World" proxy for this method.\u003c/p\u003e\n"],["\u003cp\u003eChoosing "No internet access" restricts access to internal requests only, requiring a VM inside the network to interact with the API proxy.\u003c/p\u003e\n"],["\u003cp\u003eConfiguring external access in the Cloud console involves selecting options for domain type, which can either be an automatically generated domain or a customized domain with custom subnetwork and SSL certificates.\u003c/p\u003e\n"]]],[],null,["# Step 4: Customize access routing\n\n*This page\napplies to **Apigee** , but not to **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\nWhat you're doing in this step\n------------------------------\n\nIn this step, you can choose to expose your new Apigee instance to external requests or keep\nit private (and only allow requests from within the firewall).\n| **Tip:** There are fewer steps required to deploy and test a proxy if you choose **external**. If you are following these steps for testing purposes, choose that path.\n\nHow you access the API proxy depends on whether you allow external\nrequests or restrict access to internal requests only.\n\nEach of these approaches is presented on a tab in the instructions below.\n\nPerform the step\n----------------\n\n1. Select **External Access** or **Internal Access**: \n\n### External Access\n\nThis section describes how to configure routing from the Cloud Console when you want to allow\n*external* access to your API proxy.\n\n#### Permissions required for this task\n\nYou can give the Apigee provisioner a predefined role that includes the permissions needed to complete this task,\nor give more fine-grained permissions to provide the least privilege necessary. See\n[Predefined roles](/apigee/docs/api-platform/get-started/permissions#predefined-roles)\nand [Access routing permissions](/apigee/docs/api-platform/get-started/permissions#access-routing-permissions).\n\n**To configure routing for external access in the Cloud console**:\n\n1. Click create**Edit** to open the **Configure access** panel.\n2. Select **Enable internet access** .\n\n Choose one of the following options in the **Domain Type** section:\n - **Automatically generated domain, subnetwork and SSL certificates**: Choose this option to use the nip.io wildcard DNS service, and a Google managed certificate to secure your domain. Apigee automatically creates an L7 global external load balancer to forward traffic to your runtime.\n - **Customize** : Choose this option if you want to customize your domain name, SSL certificate, or subnetwork. Apigee automatically creates an L7 global external load balancer to forward traffic to your runtime. You can select or deselect any of the following options to enter custom details:\n - **Domain**: Optional. Enter the custom domain name.\n - **Network**: Optional. Select an available network name from the dropdown menu.\n - **Subnetwork**: Optional. Select an available subnetwork name from the dropdown menu. The subnetwork selected should be in the same region as the runtime instance.\n - **SSL Certificate** : Optional. Select an existing self-managed certificate or provide a new self-managed certificate.\n\n To select an existing certificate:\n 1. Browse the file system and select the certificate you wish to use.\n 2. Click **Save SSL**.\n\n To provide a new certificate:\n 1. Click **Add new**.\n 2. In the respective fields, browse your file system and attach the files containing the certificate and private key. Both should be PEM-formatted.\n 3. Click **Save SSL**.\n3. Click **Set access** .\n\n Apigee prepares your instance for external access. This includes creating firewall\n rules, uploading certificates, and creating a load balancer.\n\n This process can take several minutes.\n\n### Internal Access\n\nThis section describes how to configure routing when you're using the\nCloud Console and you *do not* want to allow external access to your API proxy.\nInstead, you want to limit access to *internal* requests only that originate from\nwithin the VPC.\n\n**To configure routing for internal access in the Cloud Console:**\n\n1. Click create**Edit** to open the **Configure access** panel.\n2. Select **No internet access**.\n\n3. Click **Set access**.\n2. Click **Next**.\n3. Click **Submit** to begin the provisioning process.\n\n The provisioning process may take up to 40 minutes to complete. If you\n want to leave the page while provisioning is in progress, a notification\n will appear in notifications\n **Notifications** in the Cloud console when the operation completes.\n\n Once provisioning is complete, the **Apigee Overview** page will\n appear and you can begin exploring Apigee!"]]