As of November 30, 2019, you can only deploy new versions of your App Engine apps if your account provides a payment instrument, such as a credit card. This applies to apps in all App Engine runtimes, including Java 8, Python 2.7, PHP 5, and Go 1.9 apps in the standard environment.
After April 30, 2020, all running applications without a payment instrument will be shut down.
While we are asking you to add a payment instrument to your accounts, the App Engine free tier has not changed and is not going away.
Why we made this change
Requiring a payment instrument for all runtimes prevents fraud and abuse, and brings App Engine in line with the rest of Google Cloud. This allows us to spend more time on delivering new features and supporting you as you grow on App Engine.
In addition, all App Engine runtimes now use Cloud Build to build apps into a container during the deployment process. Cloud Build requires a payment instrument, and therefore if a payment instrument is not present, deploys to App Engine will fail. After April 30, 2020, all running applications without a payment instrument will be shut down. You can reinstate your application by simply adding a payment instrument.
Other than providing a payment instrument, you don't need to make any other changes to your project. The change to Cloud Build is entirely in the background and has no effect on deployment commands or administration APIs.
What is remaining the same
The free tier on App Engine is unchanged.
The App Engine standard environment Python 3, Java 11, PHP 7, Go 1.11/1.12, Ruby, and NodeJS runtimes and the App Engine flexible environment remain unchanged. These runtimes have always used Cloud Build and required a payment instrument.
What you need to do
You will need to add a payment instrument to your project if you have App Engine apps using the Java 8, Python 2.7, PHP 5, and Go 1.9 runtimes in the standard App Engine environment.
To add a payment instrument to your project:
Create a billing account if you do not already have one.
Add your credit card or other payment instrument as a payment method.
Link your project to the billing account.
Learn more about adding, removing or updating a payment method.
Why we are making this change
This change is driven by the following goals:
Reducing fraud on App Engine
Increasing the integration of App Engine with other Google Cloud services
Reducing fraud on App Engine
Fraud hurts all legitimate users of App Engine and Google. Our engineering and support teams invest significant amounts of time in preventing, monitoring, and diagnosing fraudulent usage. This limits the resources we have available to legitimate customers. In addition, fraud costs Google money, which raises costs for everyone as it must be accounted for in our pricing of App Engine.
We have direct evidence from our experience with the newer runtimes that requiring a payment instrument reduces fraud.
Integration of App Engine with other Google Cloud services
App Engine launched in 2008, predating Google Cloud, and was built in a completely custom and proprietary architecture, since there was no broader platform to integrate with. Now that Google Cloud is a large and sophisticated platform, our customers are asking for App Engine to integrate seamlessly with the services available in Google Cloud.
Integration with other Google Cloud services is possible through Serverless VPC Access, which allows App Engine to sit within the same VPC as Compute Engine VMs and Google Kubernetes Engine clusters. As part of the integration, we are moving App Engine builds to Cloud Build, which has the following benefits:
Detailed build output including verbose warnings and errors
The ability to view build history in the Cloud Build section of the Cloud Console
(Coming soon) The ability to include any library in your code in addition to the predefined set that is available in the App Engine runtimes
Almost all Google Cloud services require a payment instrument, so this additional integration means that App Engine must also require a payment instrument.
Costs of using Cloud Build
Cloud Build has a free tier that includes 120 build minutes per billing account, per day. For example, if your build took 5 minutes to complete, you would be able to deploy 24 times a day without incurring any charges. For more information on pricing beyond the free tier, see Cloud Build pricing.
Limiting your costs
You can use the following mechanisms to limit your App Engine costs: