You can select or create a new Google Cloud Platform project and App Engine
application to create and manage a collection of settings, credentials, and your
has privileges to create an App Engine application
in a GCP 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.
an account with the GCP project Owner role can run the following
gcloud commands to create a GCP project and App Engine
Run the following command to create a GCP project:
App Engine is regional, which means the infrastructure that runs your apps is
located in a specific region and is managed by Google to be redundantly
available across all the zones within that
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
location of the other GCP products and
services that are used by your app. Using
services across multiple locations can affect your app's latency as well as
App Engine is available in the following regions:
us-west2 (Los Angeles)
us-east1 (South Carolina)
us-east4 (Northern Virginia)
southamerica-east1 (São Paulo)
asia-east2 (Hong Kong)
You cannot change an app's region after you set it.
If you already created an App Engine application, you can view the
region by running the gcloud app describe command or opening the
App Engine Dashboard in the GCP Console.
The region of your App Engine application is listed under
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 GCP project, then
billing is automatically enabled on that project.
Depending on if a billing account exists or if the selected
GCP project is associated with an account, the Billing page
displays one of the following:
If billing is already enabled for the selected GCP 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 GCP project.
If a billing account exists, you are prompted to enable billing if the
selected GCP 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
set an approximate daily spending limit.
Spending limits are not supported in the App Engine flexible
View your transaction history and download invoices from the
Export your billing data to a BigQuery Dataset from the
Billing export page.
Configure your payment account and contacts on the Payment settings
Set the method of payment on the Payment method page.
For more information about billing, see the
Creating budgets and setting alerts
You can create a budget for a GCP project to avoid surprises on your
bill and monitor all of your Google Cloud Platform 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 GCP project:
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 GCP 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 GCP resources that
are being used in your GCP project by shutting down that project.