Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
Almacena las dependencias de tus aplicaciones de App Engine en Artifact Registry.
Declara dependencias en Artifact Registry en tus aplicaciones de Node.js y
Python.
Implementa tu aplicación en App Engine con Cloud Build.
Permisos necesarios
Entorno flexible de App Engine
Si el entorno flexible de App Engine y Artifact Registry están en el mismo proyecto, la cuenta de servicio predeterminada de App Engine tiene permisos para extraer contenedores de los repositorios.
Si también usas Cloud Build para alojar en contenedores tus aplicaciones y almacenarlas
en Artifact Registry, otorga el rol de escritor de Artifact Registry
a la cuenta de servicio de Cloud Build.
Entorno estándar de App Engine:
El entorno estándar de App Engine usa la cuenta de servicio de Cloud Build para compilar y, luego, implementar tus aplicaciones, incluida la integración de dependencias almacenadas en Artifact Registry.
Si App Engine y Artifact Registry están en el mismo
proyectoGoogle Cloud , la cuenta de servicio tiene los permisos
necesarios para descargar desde los repositorios.
Si App Engine y Artifact Registry están en proyectos diferentes, debes otorgarle acceso al repositorio a la cuenta de servicio.
Para proporcionar acceso de solo lectura para descargar dependencias, otorga el rol de lector de Artifact Registry a la cuenta de servicio de Cloud Build.
Si también usas Cloud Build para subir artefactos a repositorios,
otorga el rol de escritor de Artifact Registry a la cuenta de servicio
de Cloud Build.
Configura el acceso a las dependencias
En el caso de las aplicaciones del entorno estándar, consulta la documentación del entorno estándar de App Engine para obtener instrucciones de configuración de npm y Python.
Para incluir dependencias en las compilaciones que ejecutas con Cloud Build, consulta Integración con Cloud Build.
[[["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\u003eArtifact Registry allows you to store dependencies for your App Engine applications.\u003c/p\u003e\n"],["\u003cp\u003eYou can declare dependencies within Artifact Registry for both Node.js and Python applications, and then leverage Cloud Build to deploy your application to App Engine.\u003c/p\u003e\n"],["\u003cp\u003eFor App Engine flexible environment, the default service account has permissions to pull containers from Artifact Registry when they're in the same project, and if using Cloud Build to containerize apps, you need to grant the Cloud Build service account the Artifact Registry Writer role.\u003c/p\u003e\n"],["\u003cp\u003eIn the App Engine standard environment, the Cloud Build service account handles building and deploying applications, including dependencies from Artifact Registry, and if they're in different projects, you'll need to grant the service account repository access, with options for read-only or writer roles.\u003c/p\u003e\n"],["\u003cp\u003eTo configure dependency access, you can refer to the App Engine standard environment documentation for npm and Python, and to include dependencies in Cloud Build runs, you can integrate with Cloud Build.\u003c/p\u003e\n"]]],[],null,["# Deploying to App Engine\n\nStore dependencies for your App Engine applications in Artifact Registry.\n\n- Declare dependencies in Artifact Registry in your Node.js and Python applications.\n- Deploy your application to App Engine leveraging Cloud Build.\n\n| **Note:** App Engine and Cloud Build create [Pub/Sub](/pubsub/docs) topics and subscriptions in your project for use in Google's internal analysis and maintenance of your container images. These Pub/Sub push subscriptions have `rpc://` URL targets.\n\nRequired permissions\n--------------------\n\nApp Engine flexible environment\n: If App Engine flexible environment and Artifact Registry are in the same project, the\n App Engine [default service account](/appengine/docs/standard/python/service-account) has permissions to\n pull containers from repositories.\n: If you also use Cloud Build to containerize your applications and store\n them in Artifact Registry, [grant](/artifact-registry/docs/access-control#grant) the Artifact Registry Writer role\n to the Cloud Build service account.\n\nApp Engine standard environment:\n: App Engine standard environment uses the [Cloud Build service account](/build/docs/cloud-build-service-account) to\n build and deploy your applications, including integration of\n dependencies stored in Artifact Registry.\n\n - If App Engine and Artifact Registry are in the same Google Cloud project, the service account has the necessary permissions to download from repositories.\n - If App Engine and Artifact Registry are in different projects, you must grant repository access to the service account.\n - To provide read-only access for downloading dependencies, [grant](/artifact-registry/docs/access-control#grant) the Artifact Registry Reader role to the Cloud Build service account.\n - If you also use Cloud Build to upload artifacts to repositories, [grant](/artifact-registry/docs/access-control#grant) the Artifact Registry Writer role to the Cloud Build service account.\n\nConfigure access to dependencies\n--------------------------------\n\nFor standard environment applications, see the App Engine standard environment documentation for\n[npm](/appengine/docs/standard/nodejs/specifying-dependencies#private_dependencies_with_artifact_registry) and [Python](/appengine/docs/standard/python3/specifying-dependencies#private_dependencies_with_artifact_registry) configuration instructions.\n\nTo include dependencies in builds you run with Cloud Build, see\n[Integrating with Cloud Build](/artifact-registry/docs/configure-cloud-build)."]]
