Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
Per eseguire il deployment dell'app su App Engine, devi creare un Google Cloud progetto
e le risorse dell'applicazione App Engine.
Il progetto Google Cloud è un container di primo livello che contiene l'applicazione App Engine e altre risorse Google Cloud .
L'applicazione App Engine è una risorsa che devi creare per
attivare App Engine. La risorsa applicazione App Engine definisce
la regione in cui vuoi eseguire il tuo servizio web e archiviare le relative
impostazioni, credenziali e metadati. È possibile creare una sola risorsa applicazione App Engine per progetto Google Cloud e la regione specificata non può essere modificata dopo la creazione di queste risorse.
Se hai già un progetto Google Cloud con App Engine e l'API Cloud Build abilitata, puoi continuare a scrivere il tuo servizio web.
Crea un progetto Google Cloud
Sign in to your Google Cloud account. If you're new to
Google Cloud,
create an account to evaluate how our products perform in
real-world scenarios. New customers also get $300 in free credits to
run, test, and deploy workloads.
In the Google Cloud console, on the project selector page,
select or create a Google Cloud project.
Per inizializzare gcloud CLI, esegui questo comando:
gcloudinit
Esegui il seguente comando gcloud per abilitare App Engine e
creare le risorse dell'applicazione associate. Tieni presente che la
posizione che
selezioni non può essere modificata in un secondo momento.
App Engine è regionale, il che significa che l'infrastruttura che esegue le tue app si trova in una regione specifica e Google la gestisce in modo che sia disponibile in modo ridondante in tutte le zone all'interno di quella regione.
Soddisfare i requisiti di latenza, disponibilità o durabilità è il fattore principale per la selezione della regione in cui vengono eseguite le tue app. In genere puoi
selezionare la regione più vicina agli utenti della tua app, ma devi considerare le
posizioni in cui è disponibile App Engine
e le posizioni degli altri
Google Cloud prodotti e servizi utilizzati dalla tua app. L'utilizzo di servizi
in più località può influire sulla latenza della tua app e sui relativi
prezzi.
Non puoi modificare la regione di un'app dopo averla impostata.
Se hai già creato un'applicazione App Engine, puoi visualizzarne la
regione eseguendo una delle seguenti operazioni:
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-04 UTC."],[[["\u003cp\u003eGoogle Cloud projects are top-level containers for App Engine applications and other Google Cloud resources.\u003c/p\u003e\n"],["\u003cp\u003eApp Engine applications are regional resources that define where your web service runs, and only one can be created per Google Cloud project.\u003c/p\u003e\n"],["\u003cp\u003eWhen creating an App Engine application, the specified region is permanent and cannot be changed later.\u003c/p\u003e\n"],["\u003cp\u003eIf deploying a new Python web service, consider Cloud Run as an alternative to App Engine.\u003c/p\u003e\n"],["\u003cp\u003eApp Engine applications region can be found by running \u003ccode\u003egcloud app describe\u003c/code\u003e or through the App Engine Dashboard in the Google Cloud Console.\u003c/p\u003e\n"]]],[],null,["\u003cbr /\u003e\n\n| **Note:** If you are deploying a new Python web service to Google Cloud, we recommend getting started with [Cloud Run](/run/docs/quickstarts/build-and-deploy/deploy-python-service).\n\nTo deploy your app to App Engine, you must create a Google Cloud project\nand your App Engine application resources.\n\nThe Google Cloud project is a top-level container that holds your\nApp Engine application and other Google Cloud resources.\n\nThe App Engine application is a resource that you must create to\nenable App Engine. The App Engine application resource defines\nthe region in which you want to run your web service and store its\nrelated settings, credentials, and metadata. Only a single App Engine\napplication resource can be created per Google Cloud project and the specified\nregion cannot be changed after those resources are created.\n\nIf you already have a Google Cloud project with App Engine and the\nCloud Build API enabled, you can continue to\n[Writing Your Web Service](/appengine/docs/standard/python3/building-app/writing-web-service).\n\nCreate a Google Cloud project\n\n- Sign in to your Google Cloud account. If you're new to Google Cloud, [create an account](https://console.cloud.google.com/freetrial) to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.\n- In the Google Cloud console, on the project selector page,\n select or create a Google Cloud project.\n\n | **Note**: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.\n\n [Go to project selector](https://console.cloud.google.com/projectselector2/home/dashboard)\n-\n [Verify that billing is enabled for your Google Cloud project](/billing/docs/how-to/verify-billing-enabled#confirm_billing_is_enabled_on_a_project).\n\n-\n\n\n Enable the Cloud Build API.\n\n\n [Enable the API](https://console.cloud.google.com/flows/enableapi?apiid=cloudbuild.googleapis.com)\n-\n [Install](/sdk/docs/install) the Google Cloud CLI.\n\n- If you're using an external identity provider (IdP), you must first\n [sign in to the gcloud CLI with your federated identity](/iam/docs/workforce-log-in-gcloud).\n\n-\n To [initialize](/sdk/docs/initializing) the gcloud CLI, run the following command:\n\n ```bash\n gcloud init\n ```\n\n- In the Google Cloud console, on the project selector page,\n select or create a Google Cloud project.\n\n | **Note**: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.\n\n [Go to project selector](https://console.cloud.google.com/projectselector2/home/dashboard)\n-\n [Verify that billing is enabled for your Google Cloud project](/billing/docs/how-to/verify-billing-enabled#confirm_billing_is_enabled_on_a_project).\n\n-\n\n\n Enable the Cloud Build API.\n\n\n [Enable the API](https://console.cloud.google.com/flows/enableapi?apiid=cloudbuild.googleapis.com)\n-\n [Install](/sdk/docs/install) the Google Cloud CLI.\n\n- If you're using an external identity provider (IdP), you must first\n [sign in to the gcloud CLI with your federated identity](/iam/docs/workforce-log-in-gcloud).\n\n-\n To [initialize](/sdk/docs/initializing) the gcloud CLI, run the following command:\n\n ```bash\n gcloud init\n ```\n\n1. Run the following `gcloud` command to enable App Engine and create the associated application resources. Note that the [location](#creating_a_gcp_project) you select cannot be changed later. \n\n ```bash\n gcloud app create\n ```\n2. Due to [changes in the default\n behavior for how Cloud Build uses service accounts](/build/docs/cloud-build-service-account-updates) in new projects, and [secure-by-default\n organization policy changes](/resource-manager/docs/secure-by-default-organizations), you might need to grant additional roles to your deploying service account. For more information on granting specific roles, see the [troubleshooting guide](/appengine/docs/standard/troubleshooter/deployment#default-sa-permissions).\n\nApp Engine locations\n\n\u003cbr /\u003e\n\nApp Engine is *regional* , which means the infrastructure that runs your apps is\nlocated in a specific region, and Google manages it so that it is available\nredundantly across\n[all of the zones within that region](/docs/geography-and-regions).\n\nMeeting your latency, availability, or durability requirements are primary\nfactors for selecting the region where your apps are run. You can generally\nselect the region nearest to your app's users, but you should consider [the\nlocations where App Engine is available](/about/locations#region)\nas well as the [locations](/about/locations#region) of the other\nGoogle Cloud products and services that your app uses. Using services\nacross multiple locations can affect your app's latency as well as its\n[pricing](/appengine/pricing).\n\nYou cannot change an app's region after you set it.\n| **Note:** Two locations, which are called `europe-west` and `us-central` in App Engine commands and in the Google Cloud console, are called `europe-west1` and `us-central1`, respectively, elsewhere in Google documentation.\n\nIf you already created an App Engine application, you can view its\nregion by doing one of the following:\n\n- Run the `gcloud app describe` command.\n\n- Open the\n [App Engine Dashboard in the Google Cloud console](https://console.cloud.google.com/appengine).\n The region appears near the top of the page.\n\nOK\n\nNext steps\n\nNow that your Google Cloud project is set up, you're ready to\nwrite a basic web service."]]
