Setting up your Google Cloud project for App Engine Stay organized with collections Save and categorize content based on your preferences.
A Google Cloud project contains your App Engine application as well as otherGoogle Cloud resources.
You can perform all of your administrative tasks from the Google Cloud CLI and theApp Engine Admin API, including the common tasks covered in this topic.Before you candeploy your appsto the App Engine standard environment, you typically need tocreate or set up the following:
Creating a project and application
You can select or create a new Google Cloud project and App Engineapplication to create and manage a collection of settings, credentials, and yourapp's metadata. App Engine requires allprojects to enable billing, but you will only be charged if a project exceedsitsfree quota.
Only theOwner rolehas privileges to create an App Engine applicationin a Google Cloud project and that application must exist before any otheraccount can perform tasks on that application. For example, theApp Engine application must be created before an account with theApp Engine Deployer role can deploy an app using a service account.
Important: Each Google Cloud project can contain only a singleApp Engine application, and once created you cannot change thelocation of your App Engine application.gcloud
After installingGoogle Cloud CLI,an account with the Google Cloud project Owner role can run the followinggcloud commands to create a Google Cloud project and App Engineapplication:
Run the following command to create a Google Cloud project:
gcloudprojectscreatePROJECT_ID
ReplacePROJECT_ID with the Google Cloud project ID.
Run the following command to select a region and create anApp Engine application:
gcloudappcreate
Enable billing in the Billing page of the Google Cloud console, seeEnabling billing for details.
Tips:- If you deploy your apps with the
gcloud app deploycommand, the gcloud CLI will ensure that yourGoogle Cloud project includes an App Engine application andprompt you to select a region when needed. - To check if an App Engine application exists in yourGoogle Cloud project, you can run the
gcloud app describecommand.
- If you deploy your apps with the
API
To programmatically create a Google Cloud project and App Engineapplication, you use both the Cloud Resource Manager API and App Engine Admin API:
To create a Google Cloud project, seeCreating a NewProject.
To create an App Engine application, seeCreating AppEngine Applications.
Enable billing in the Billing page of the Google Cloud console, seeEnabling billing for details.
Console
Note: This is not applicable to Python.To create a Google Cloud project and App Engineapplication with billing enabled:
Go to the App Engine page:
Select or create a Google Cloud project.
In theCreate App page,select a region, service account, and enable billing:
- Select a region to specify where you want to your App Engineapplication located.More information about App Engine locations
- Select aservice accountfor your app fromIdentity and API access.
- Select or create a billing account to enable billing in your project.
After the App Engine application is created in your project, theDashboard page opens.
App Engine Locations
App Engine isregional, which means the infrastructure that runs your apps islocated in a specific region, and Google manages it so that it is availableredundantly acrossall of the zones within that region.
Meeting your latency, availability, or durability requirements are primaryfactors for selecting the region where your apps are run. You can generallyselect the region nearest to your app's users, but you should considerthelocations where App Engine is availableas well as thelocations of the otherGoogle Cloud products and services that your app uses. Using servicesacross multiple locations can affect your app's latency as well as itspricing.
You cannot change an app's region after you set it.
Note: Two locations, which are calledeurope-west andus-central in App Engine commands and in the Google Cloud console,are calledeurope-west1 andus-central1, respectively,elsewhere in Google documentation.If you already created an App Engine application, you can view itsregion by doing one of the following:
Run the
gcloud app describecommand.Open theApp Engine Dashboard in the Google Cloud console.The region appears near the top of the page.
Enabling billing
To deploy your apps, you must enable billing.Your account will not be charged if you stay within yourfree quota.If your application needs resources that exceed the free quota, you will becharged for the additional usage.
If you have a billing account when you create a Google Cloud project, thenbilling is automatically enabled on that project.
To enable billing on a Google Cloud project:
In the Google Cloud console, go to the Billing page:
Select or create a Google Cloud project.
Depending on if a billing account exists or if the selectedGoogle Cloud project is associated with an account, the Billing pagedisplays one of the following:
If billing is already enabled for the selected Google Cloud project,then the details about the billing account are listed.
If no billing account exists, you are prompted to create a billing accountand associate it with the selected Google Cloud project.
If a billing account exists, you are prompted to enable billing if theselected Google Cloud project is not already associated with a billingaccount. You can also clickCancel and then clickCreate account to create and associate a new billing account.
After you enable billing, there is no limit to the amount that you mightbe charged. To gain more control over your application's costs, you cancreate a budget and set alerts.
Managing billing
Use the Billing page to manage your billing accounts:
Go to the Billing page in the Google Cloud console:
Select the account that you want to manage and then navigate to thecorresponding page to perform the following management tasks:
- See an overview of your billing account, make payments, and add billingaccount administrators from theOverview page.
- Create budgets and alerts on theBudgets & alerts page.
- View your transaction history and download invoices from theTransactions page.
- Export your billing data to a BigQuery Dataset from theBilling export page.
- Configure your payment account and contacts on thePayment settingspage.
- Set the method of payment on thePayment method page.
For more information about billing, see thePricing page.
Creating budgets and setting alerts
You can create a budget for a Google Cloud project to avoid surprises on yourbill and monitor all of your Google Cloud charges from one place. With a budget,you can create alerts that send emails to your billing administrators whencharges exceed a certain amount.
To create a budget and set alerts in a Google Cloud project:
In the Google Cloud console, go to the Billing page:
Click the billing account for which you want to create a budget.
ClickBudgets & alerts and thenCreate budget to begin creating abudget for your Google Cloud project.
Define your budget in theSet budget section and then specify thepercentages for which you want to receive email alerts in the followingSet budget alerts section.
ClickSave to set the budget and enable alerts for yourGoogle Cloud project. If you have multiple Google Cloud projects, youmust individually set budgets and alerts in each project.
Setting project ID for a project
You can specify the project ID in a few different ways:
- By using
gcloud initwhen you install the Google Cloud CLI. To view thedefault project ID of the gcloud CLI, rungcloud config list. - By using the
gcloud config set project [YOUR_PROJECT_ID]command to setthe default project ID of the gcloud CLI. - By using the
--projectflag when you deploy your app, for example:gcloud app deploy --project [YOUR_PROJECT_ID]
If you use the Java runtime, you can specify the project IDduring deployment using theGoogle Cloud plugin for IntelliJ.
Disabling an application
Disable an App Engine application to stop your app from runninginstances and serving requests. No data loss will occur when you disable yourapp, nor will any configuration settings change. Simply re-enable yourApp Engine application to startup instances and continue serving thetraffic to your app.
Your app's resources in both the standard and flexible environment are disabledand therefore, won't incur charges. However, billing charges can still occur forthe other services in your Google Cloud project, for example you can stillincur storage charges for your stored data.
If your app is actively processing a request, it will continue to complete thattask and can take up to an hour before your app is completely disabled.
To disable an App Engine application:
Go to the Application settings page:
ClickDisable application and then follow the prompts.
When you want your app to continue serving requests, enable theApp Engine application by returning to the sameApplication settingspage and then clickingEnable application.
Disabling your application stops all serving requests, but your data and stateare retained. You will still be billed for applicable charges already incurredor charges for other services running in your project, such as Cloud SQL.To release all the resources used within the project, shut down your project.
Shutting down a project
You can disable billing and release all the Google Cloud resources thatare being used in your Google Cloud project by shutting down that project.
gcloud
After installing theGoogle Cloud CLI, you run the followinggcloud command to shut down a Google Cloud project:
gcloudprojectsdeletePROJECT_ID
ReplacePROJECT_ID with the Google Cloud project ID.
API
To programmatically shut down your Google Cloud project, seeShutting Down a Project inthe Cloud Resource Manager API.
Console
To shut down a Google Cloud project using the Google Cloud console:
Go to the Projects page:
Select the Google Cloud project that you want to shut down, thenclickdelete.
For more information about managing your Google Cloud projects, seeCloud Resource Manager: creating, shutting down, and restoringprojects.
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-12-15 UTC.