Asegúrate de que haya una red de VPC disponible en el proyecto de Google Cloud que usarás para aprovisionar Apigee. Para ver las redes de VPC disponibles en tu proyecto, ve a la página Redes de VPC:
Redes predeterminadas: Este recurso usa la red y la subred autorizadas predeterminadas en tu proyecto de Google Cloud y asigna automáticamente rangos de IP para el intercambio de tráfico entre redes y las IP del entorno de ejecución.
Un dominio administrado por Google: Esto incluye el servicio de DNS comodín nip.io y un certificado SSL administrado por Google para proteger tu dominio.
Crea el siguiente recurso permanente:
Claves de Google y claves administradas por Google: Este recurso incluye claves de encriptación para la base de datos del entorno de ejecución y la encriptación del disco del entorno de ejecución.
La página Provisioning Apigee se muestra cuando comienza el aprovisionamiento. Puedes supervisar el progreso y ver el tiempo aproximado que queda para completar la tarea desde esta página. El aprovisionamiento puede tomar hasta una hora.
Una vez que se habiliten las APIs necesarias, como se indica en check_circleHabilitado, puedes salir de la página. Aparecerá una notificación en la consola de Google Cloud cuando se complete la operación de aprovisionamiento.
Cuando se complete el aprovisionamiento, se mostrará la página Panel de Apigee. ¡Felicitaciones! Puedes comenzar a explorar Apigee.
Soluciona problemas de aprovisionamiento con un clic
Si los recursos necesarios para aprovisionar Apigee no están disponibles en tu proyecto de Google Cloud, es posible que veas un mensaje de error después de hacer clic en Configurar con valores predeterminados en la página Te damos la bienvenida a la administración de API de Apigee, como se muestra a continuación:
Es posible que veas este mensaje en los siguientes casos:
No hay una red de VPC disponible en el proyecto de Google Cloud que usas para aprovisionar Apigee.
Tu organización de Google Cloud tiene una política que restringe la creación de recursos en la región que se usa para el aprovisionamiento de Apigee. Para obtener más información, consulta Introducción al Servicio de políticas de la organización.
Si encuentras este error, te recomendamos que hagas clic en Personalizar tu configuración para personalizar los recursos necesarios creados para Apigee en tu proyecto.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-04 (UTC)"],[[["\u003cp\u003eThis guide focuses on provisioning a new Apigee Subscription organization, and it does not apply to Apigee hybrid.\u003c/p\u003e\n"],["\u003cp\u003eOne-click provisioning is available for creating a new Apigee Subscription organization with smart default configuration settings, though this option may be disabled by an organization policy constraint.\u003c/p\u003e\n"],["\u003cp\u003eBefore starting, you need to ensure that there is an available VPC network in the chosen Google Cloud project.\u003c/p\u003e\n"],["\u003cp\u003eOne-click provisioning automatically enables required APIs and creates default networking, a Google-managed domain, and a Google-managed encryption key.\u003c/p\u003e\n"],["\u003cp\u003eIf resources are unavailable, or you run into an error during one-click provisioning, you can choose to customize the setup instead of using defaults.\u003c/p\u003e\n"]]],[],null,["# Provision Apigee with one click\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\nYou can provision a new Apigee Subscription organization with just one click, using smart\ndefault configuration settings.\n| **Note:** This option could be disabled if your project has a CMEK [organization policy constraint](/apigee/docs/api-platform/get-started/using-org-policies).\n\nBefore you begin\n----------------\n\nBefore you provision your Apigee Subscription organization:\n\n1. Review and complete the steps described in these topics:\n - [Prerequisites](/apigee/docs/api-platform/get-started/prerequisites)\n - [Get started in the Google Cloud console](/apigee/docs/api-platform/get-started/wizard-select-project)\n2. Ensure there is an available VPC network in the Google Cloud project you will use to provision Apigee. To view available VPC networks in your project, go to the **VPC Networks** page:\n\n [Go to VPC networks](https://cloud.google.com/console/networking/networks/list)\n\n If there is no available network in your project, you may encounter an error during provisioning.\n For more details, see [Troubleshoot one-click provisioning](#troubleshoot).\n\nProvision Apigee with one click\n-------------------------------\n\nTo start one-click provisioning for a new Apigee Subscription organization:\n\n1. Go to the **Welcome to Apigee API management** page in the Google Cloud console.\n\n [Go to Apigee API Management](https://cloud.google.com/console/apigee/welcome)\n2. Click **Set up with defaults** .\n\n When you select this one-click option, Apigee does the following:\n - Enables the required APIs\n - [API hub API](https://console.cloud.google.com/apis/library/apihub.googleapis.com)\n - [Apigee API](https://console.cloud.google.com/apis/library/apigee.googleapis.com)\n - [Compute Engine API](https://console.cloud.google.com/apis/library/compute.googleapis.com)\n - [Cloud Key Management Service (KMS) API](https://console.cloud.google.com/apis/library/cloudkms.googleapis.com)\n - [Service Networking API](https://console.cloud.google.com/apis/library/servicenetworking.googleapis.com)\n - Creates the following configurable resources:\n - **Default networking**: This resource uses the default authorized network and subnetwork in your Google Cloud project and automatically allocates IP ranges for network peering and runtime IPs.\n - **A Google-managed domain** : This includes the `nip.io` wildcard DNS service and a Google-managed SSL certificate to secure your domain.\n - Creates the following permanent resources:\n - **Google-managed encryption key** : This resource includes encryption keys for runtime database and runtime disk encryption. **Note:** If you create this permanent resource using **Set up with defaults** for one-click provisioning, you cannot go back and change the encryption key selections. Apigee does not support updating the encryption key selections after provisioning is complete. For example, if Google-owned and Google-managed encryption keys are created using this option, you cannot change to Customer-managed encryption later.\n - **API hub** instance: A new [API hub instance](/apigee/docs/apihub/what-is-api-hub) is created in the same project and region as your Apigee organization. If you need API hub with customer-managed encryption keys, you must delete the auto-provisioned API hub instance and create a new API hub instance in the same project and region as your Apigee organization.\n\n \u003cbr /\u003e\n\n3. The **Provisioning Apigee** page displays when provisioning begins. You can monitor progress and view the approximate time remaining to complete from this page. Provisioning may take up to **one hour** .\n\n Once the required APIs are enabled, as indicated by check_circle **Enabled**, you can leave the page. A notification will\n appear in the Google Cloud console when the provisioning operation completes.\n4. When provisioning completes, the **Apigee Dashboard** page displays. Congratulations! You can begin exploring Apigee!\n\nTroubleshoot one-click provisioning\n-----------------------------------\n\nIf the resources required to provision Apigee are not available in your Google Cloud project,\nyou may encounter an error message after clicking **Set up with defaults** on the **Welcome to Apigee API management** page, as shown below:\n\nYou may encounter this message if:\n\n- There is no available VPC network in the Google Cloud project you are using to provision Apigee.\n- Your Google Cloud organization has a policy restricting the creation of resources in the region used for Apigee provisioning. For more information, see [Introduction to the Organization Policy Service](/resource-manager/docs/organization-policy/overview).\n\nIf you encounter this error, we recommend clicking **Customize your setup** to customize the\nrequired resources created for Apigee in your project."]]