This topic explains how to change the IP of an Apigee instance by manually updating the
VMs.
Overview
When an Apigee instance is
deleted
and then created
again, an IP address is generated for the newly created instance. For example, certain instance
parameters, such as cidrRange and networking, are immutable. Therefore, if you want to change
these parameters, you must delete the instance and recreate it with the desired configuration.
In most cases, when you recreate an instance, the same instance IP is selected, but getting the
same IP is not guaranteed. The VMs that are routing traffic from the load balancer to
Apigee's private IP still have the old IP address; therefore, in cases where a new instance
IP is generated, you have to manually update the VMs with the new IP.
Changing the instance IP
To update the VMs with a new instance IP, follow these steps:
In the Google Cloud console, go to the Virtual Machines>Instance templates page.
Click on the Apigee instance template (the template that you want to copy and update).
Click Create Similar.
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.
Under Advanced options, click the Management tab.
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:
Click Create to create the template.
In the Google Cloud console, go to the Instance groups page.
Under the Name column of the list, click the name of the Apigee instance group that you wish to modify.
Click Edit to modify this instance group.
Under Instance template, select the new instance template (the one you just created).
Click Save.
At the top of the page, click Rolling update.
Leave all the defaults/presets as-is and click Update.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 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."]]
