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 other
Google Cloud resources.
You can perform all of your administrative tasks from the Google Cloud CLI and the
App Engine Admin API, including the common tasks covered in this topic.
Before you can
deploy your apps
to the App Engine standard environment, you typically need to
create or set up the following:
You can select or create a new Google Cloud project and App Engine
application to create and manage a collection of settings, credentials, and your
app's metadata. App Engine requires all
projects to enable billing, but you will only be charged if a project exceeds
its free quota.
Only the
Owner role
has privileges to create an App Engine application
in a Google Cloud project and that application must exist before any other
account can perform tasks on that application. For example, the
App Engine application must be created before an account with the
App Engine Deployer role can deploy an app using a service account.
App Engine is regional, which means the infrastructure that runs your apps is
located in a specific region, and Google manages it so that it is available
redundantly across
all of the zones within that region.
Meeting your latency, availability, or durability requirements are primary
factors for selecting the region where your apps are run. You can generally
select the region nearest to your app's users, but you should consider the
locations where App Engine is available
as well as the locations of the other
Google Cloud products and services that your app uses. Using services
across multiple locations can affect your app's latency as well as its
pricing.
You cannot change an app's region after you set it.
If you already created an App Engine application, you can view its
region by doing one of the following:
To deploy your apps, you must enable billing.
Your account will not be charged if you stay within your free quota.
If your application needs resources that exceed the free quota, you will be
charged for the additional usage.
If you have a billing account when you create a Google Cloud project, then
billing is automatically enabled on that project.
To enable billing on a Google Cloud project:
In the Google Cloud console, go to the Billing page:
Depending on if a billing account exists or if the selected
Google Cloud project is associated with an account, the Billing page
displays 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 account
and associate it with the selected Google Cloud project.
If a billing account exists, you are prompted to enable billing if the
selected Google Cloud project is not already associated with a billing
account. You can also click Cancel and then click
Create account to create and associate a new billing account.
After you enable billing, there is no limit to the amount that you might
be charged. To gain more control over your application's costs, you can
create 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:
View your transaction history and download invoices from the
Transactions page.
Export your billing data to a BigQuery Dataset from the
Billing export page.
Configure your payment account and contacts on the Payment settings
page.
Set the method of payment on the Payment method page.
For more information about billing, see the
Pricing page.
Creating budgets and setting alerts
You can create a budget for a Google Cloud project to avoid surprises on your
bill 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 when
charges 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.
Click Budgets & alerts and then Create budget to begin creating a
budget for your Google Cloud project.
Define your budget in the Set budget section and then specify the
percentages for which you want to receive email alerts in the following
Set budget alerts section.
Click Save to set the budget and enable alerts for your
Google Cloud project. If you have multiple Google Cloud projects, you
must 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 init when you install the Google Cloud CLI. To view the
default project ID of the gcloud CLI, run gcloud config list.
By using the gcloud config set project [YOUR_PROJECT_ID] command to set
the default project ID of the gcloud CLI.
By using the --project flag when you deploy your app, for example:
gcloud app deploy --project [YOUR_PROJECT_ID]
Disable an App Engine application to stop your app from running
instances and serving requests. No data loss will occur when you disable your
app, nor will any configuration settings change. Simply re-enable your
App Engine application to startup instances and continue serving the
traffic to your app.
Your app's resources in both the standard and flexible environment are disabled
and therefore, won't incur charges. However, billing charges can still occur for
the other services in your Google Cloud project, for example you can still
incur storage charges for your stored data.
If your app is actively processing a request, it will continue to complete that
task and can take up to an hour before your app is completely disabled.
Click Disable application and then follow the prompts.
When you want your app to continue serving requests, enable the
App Engine application by returning to the same Application settings
page and then clicking Enable application.
Disabling your application stops all serving requests, but your data and state
are retained. You will still be billed for applicable charges already incurred
or 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 that
are being used in your Google Cloud project by shutting down that project.
[[["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 2026-07-17 UTC."],[],[]]