이 주제에서는 VM을 수동으로 업데이트하여 Apigee 인스턴스의 IP를 변경하는 방법을 설명합니다.
개요
Apigee 인스턴스를 삭제한 후 다시 만들면 새로 생성된 인스턴스에 대해 IP 주소가 생성됩니다. 예를 들어 cidrRange 및 네트워킹과 같은 특정 인스턴스 매개변수는 변경할 수 없습니다. 따라서 이러한 매개변수를 변경하려면 인스턴스를 삭제하고 원하는 구성으로 다시 만들어야 합니다.
대부분의 경우 인스턴스를 다시 만들면 동일한 인스턴스 IP가 선택되지만 동일한 IP가 사용된다고 보장할 수는 없습니다. 부하 분산기에서 Apigee의 비공개 IP로 트래픽을 라우팅하는 VM에는 여전히 이전 IP 주소가 있으므로 새 인스턴스 IP가 생성된 경우 VM을 수동으로 새 IP로 업데이트해야 합니다.
[[["이해하기 쉬움","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-08-18(UTC)"],[[["\u003cp\u003eThis content pertains to Apigee, excluding Apigee hybrid, and is specifically for organizations with VPC peering enabled.\u003c/p\u003e\n"],["\u003cp\u003eWhen an Apigee instance is deleted and recreated, a new IP address may be generated, requiring manual updating of the VMs.\u003c/p\u003e\n"],["\u003cp\u003eChanging certain immutable parameters of an Apigee instance, like \u003ccode\u003ecidrRange\u003c/code\u003e and networking, necessitates deleting and recreating the instance.\u003c/p\u003e\n"],["\u003cp\u003eTo update VMs with a new instance IP, create a new instance template, modify the \u003ccode\u003eENDPOINT\u003c/code\u003e metadata to reflect the new IP, and then apply this template to the instance group via a rolling update.\u003c/p\u003e\n"],["\u003cp\u003eAfter a rolling update is initiated, new VMs will take a few minutes to become operational, and old VMs will be shut down, resuming normal API traffic upon completion.\u003c/p\u003e\n"]]],[],null,["# Changing instance IPs\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\n| **Important:** This topic only applies to organizations that were created with VPC peering enabled. See also [Apigee networking options](/apigee/docs/api-platform/get-started/networking-options).\n\n\nThis topic explains how to change the IP of an Apigee instance by manually updating the\nVMs.\n\nOverview\n--------\n\n\nWhen an Apigee instance is\n[deleted](https://cloud.google.com/apigee/docs/reference/apis/apigee/rest/v1/organizations.instances/delete)\nand then [created](https://cloud.google.com/apigee/docs/reference/apis/apigee/rest/v1/organizations.instances/create)\nagain, an IP address is generated for the newly created instance. For example, certain instance\nparameters, such as cidrRange and networking, are immutable. Therefore, if you want to change\nthese parameters, you must delete the instance and recreate it with the desired configuration.\n\n\nIn most cases, when you recreate an instance, the same instance IP is selected, but getting the\nsame IP is not guaranteed. The VMs that are routing traffic from the load balancer to\nApigee's private IP still have the old IP address; therefore, in cases where a new instance\nIP is generated, you have to manually update the VMs with the new IP.\n\nChanging the instance IP\n------------------------\n\n\nTo update the VMs with a new instance IP, follow these steps:\n\n1. In the Google Cloud console, go to the **Virtual Machines** \\\u003e **Instance templates** page.\n\n [Go to Instance templates](https://console.cloud.google.com/compute/instanceTemplates/list)\n2. Click on the Apigee instance template (the template that you want to copy and update).\n3. Click **Create Similar**.\n4. In the **Name** field, provide a new name for the template. For example, you might add a suffix like \"v2\" at the end of the original name.\n5. Under **Advanced options** , click the **Management** tab.\n6. Scroll down to the **Metadata (Optional)** section and look for the key value pair containing the **ENDPOINT** key. Change the value of the endpoint to match the new instance IP. Use your IP, not the one shown in the screenshot:\n\n7. Click **Create** to create the template.\n8. In the Google Cloud console, go to the **Instance groups** page.\n\n [Go to Instance groups](https://console.cloud.google.com/compute/instanceGroups/list)\n9. Under the **Name** column of the list, click the name of the Apigee instance group that you wish to modify.\n10. Click **Edit** to modify this instance group.\n11. Under **Instance template**, select the new instance template (the one you just created).\n12. Click **Save**.\n13. At the top of the page, click **Rolling update**.\n14. Leave all the defaults/presets as-is and click **Update**.\n15. It takes a few minutes for the new VMs to come up, and the old VMs will be shut down and removed. Once the new VMs are up, all API traffic will resume normally."]]
