PHP 5 已終止支援，並將於 2026 年 1 月 31 日
淘汰。淘汰後，您將無法部署 PHP 5 應用程式，即使貴機構先前曾使用機構政策重新啟用舊版執行階段的部署作業，也無法部署。現有的 PHP 5 應用程式在
淘汰日期後仍會繼續執行並接收流量。建議您
改用系統支援的最新 PHP 版本。
所有 App Engine 執行階段都必須提供付款方式
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
自 2019 年 11 月 30 日起，您必須在帳戶中提供付款方式 (例如信用卡)，才能部署新版 App Engine 應用程式。自 2021 年 8 月 9 日起，所有 App Engine 應用程式都必須提供付款方式，才能繼續運作。這項規定適用於所有 App Engine 執行階段的應用程式，包括 App Engine 標準環境中的 Java 8、Python 2.7、PHP 5 和 Go 1.11 應用程式。
自 2021 年 8 月 9 日起，如果執行中的應用程式沒有付款方式，就會遭到關閉。
雖然您必須為帳戶提供付款方式，但App Engine 免費方案並未異動，也不會移除。
異動原因
要求所有執行階段都提供付款方式，可防止詐欺和濫用行為，並讓 App Engine 與其他 Google Cloud保持一致。這麼做可讓我們有更多時間提供新功能，並在您使用 App Engine 時提供支援。
此外，所有 App Engine 執行階段現在都會在部署程序期間使用 Cloud Build 將應用程式建構至容器。Cloud Build 需要付款方式，因此如果沒有付款方式，部署至 App Engine 的作業就會失敗。自 2021 年 8 月 9 日起，如果執行中的應用程式沒有付款方式，就會關閉。您可以新增付款方式，讓應用程式恢復正常運作。
除了提供付款方式之外，您不需要對專案進行任何其他變更。對 Cloud Build 的變更完全在背景進行，不會影響部署指令或管理 API。
維持不變的部分
App Engine 的免費方案不變。
您會看到的內容
如果專案中沒有有效的付款方式，您會看到以下畫面：
需要採取的行動
如果您在 App Engine 標準環境中，有使用 Java 8、Python 2.7、PHP 5 和 Go 1.11 執行階段的 App Engine 應用程式，就必須在專案中新增付款方式。
如要為專案新增付款方式，請按照下列步驟操作：
如果您還沒有帳單帳戶，請建立帳單帳戶。
新增信用卡或其他付款方式做為付款方式。
將專案連結至帳單帳戶。
進一步瞭解如何新增、移除或更新付款方式。
異動原因
這項變更的目標如下：
減少 App Engine 上的詐欺行為
詐欺行為會對 App Engine 和 Google 的所有合法使用者造成傷害。我們的工程團隊和支援團隊投入大量時間，防止、監控及診斷不當使用行為。這會限制我們提供給合法客戶的資源。此外，詐欺行為會讓 Google 損失金錢，而我們必須將這筆費用列入 App Engine 的價格，因此會提高所有人的成本。
我們在使用較新的執行階段時發現，要求使用者提供付款方式確實有助於減少詐欺行為，這也是我們直接觀察到的證據。
將 App Engine 與其他 Google Cloud 服務整合
App Engine 於 2008 年推出，比 Google Cloud更早，且採用完全自訂的專屬架構建構，因為當時沒有更廣泛的平台可供整合。由於 Google Cloud 是一個龐大且複雜的平台，我們的客戶希望 App Engine 能與 Google Cloud中提供的服務無縫整合。
您可以透過 Serverless VPC Access 與其他 Google Cloud 服務整合，讓 App Engine 位於與 Compute Engine VM 和 Google Kubernetes Engine 叢集相同的 VPC 中。在整合過程中，我們會將 App Engine 建構作業移至 Cloud Build，這樣做有以下優點：
幾乎所有 Google Cloud 服務都需要付款方式，因此這項額外整合功能代表 App Engine 也必須提供付款方式。
使用 Cloud Build 的費用
Cloud Build 提供免費方案，每個帳單帳戶每天可使用 120 分鐘的建構時間。舉例來說，如果建構作業需要 5 分鐘才能完成，您每天可以部署 24 次，而不會產生任何費用。如要進一步瞭解免費方案以外的定價，請參閱 Cloud Build 定價。
限制費用
您可以使用下列機制限制 App Engine 費用：
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-09-04 (世界標準時間)。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[[["\u003cp\u003eAs of August 9, 2021, all App Engine applications require a payment method to remain active, and those without will be shut down.\u003c/p\u003e\n"],["\u003cp\u003eDeployments to App Engine will fail if no payment method is present due to the use of Cloud Build for app containerization.\u003c/p\u003e\n"],["\u003cp\u003eThe App Engine free tier is still available and has not been changed.\u003c/p\u003e\n"],["\u003cp\u003eAdding a payment method is the only required action; no other changes to existing project code or configurations are needed.\u003c/p\u003e\n"],["\u003cp\u003eRequiring a payment method helps reduce fraud and increases integration with other Google Cloud services.\u003c/p\u003e\n"]]],[],null,["# Payment method required for all App Engine runtimes\n\nAs of November 30, 2019, you can only deploy new versions of your\nApp Engine apps if your account provides a\n[payment method](/billing/docs/how-to/payment-methods#available_payment_methods),\nsuch as a credit card. As of August 9, 2021, all App Engine apps require\na payment method to continue running. This requirement applies to apps\nin all App Engine runtimes, including Java 8, Python 2.7, PHP 5, and Go 1.11 apps\nin the App Engine standard environment.\n\n**As of August 9, 2021, if a running application does not have a payment method,\nit will be shut down.**\n\nWhile you must provide a payment method for your accounts,\nthe **App Engine free tier has not changed and is not going away**.\n\nWhy we made this change\n-----------------------\n\nRequiring a payment method for all runtimes prevents fraud and abuse, and\nbrings App Engine in line with the rest of Google Cloud. This allows\nus to spend more time on delivering new features and supporting you as you grow\non App Engine.\n\nIn addition, all App Engine runtimes now use Cloud Build to build\napps into a container during the deployment process. Cloud Build\nrequires a payment method, and therefore if a payment method is not\npresent, **deployments to App Engine will fail** . As of August 9, 2021,\nif a running application does not have a payment method, it **will be shut down**.\nYou can reinstate your application by adding a payment method.\n\nOther than providing a payment method, you don't need to make any other\nchanges to your project. The change to Cloud Build is entirely in the\nbackground and has no effect on deployment commands or administration APIs.\n\nWhat remains the same\n---------------------\n\n**The [free tier](/appengine/quotas) on App Engine is unchanged.**\n\nWhat you will see\n-----------------\n\nIf you do not have a valid payment method on the project, you will see:\n\n- `HTTP 500` errors returned when requests are sent to your app\n\n- App log entries in your App Engine logs that read\n \"Billing disabled. Shutting down instance.\"\n\nWhat you need to do\n-------------------\n\nYou will need to add a payment method to your project if you have\nApp Engine apps using the Java 8, Python 2.7, PHP 5, and Go 1.11 runtimes\nin the App Engine standard environment.\n\nTo add a payment method to your project:\n\n1. [Create a billing account](https://console.cloud.google.com/billing/)\n if you do not already have one.\n\n2. Add your credit card or other payment method as a payment method.\n\n3. Link your project to the billing account.\n\nLearn more about [adding, removing or updating a payment method](/billing/docs/how-to/payment-methods).\n\nWhy we are making this change\n-----------------------------\n\nThis change is driven by the following goals:\n\n- Reducing fraud on App Engine\n\n- Increasing the integration of App Engine with other Google Cloud\n services\n\n### Reduce fraud on App Engine\n\nFraud hurts all legitimate users of App Engine and Google. Our\nengineering and support teams invest significant amounts of time in preventing,\nmonitoring, and diagnosing fraudulent usage. This limits the resources we have\navailable to legitimate customers. In addition, fraud costs Google money, which\nraises costs for everyone as it must be accounted for in our pricing of\nApp Engine.\n\nWe have direct evidence from our experience with the newer runtimes that\nrequiring a payment method reduces fraud.\n\n### Integrate App Engine with other Google Cloud services\n\nApp Engine launched in 2008, predating Google Cloud, and was built in a\ncompletely custom and proprietary architecture, since there was no broader platform\nto integrate with. Now that Google Cloud is a large and sophisticated\nplatform, our customers are asking for App Engine to integrate\nseamlessly with the services available in Google Cloud.\n\nIntegration with other Google Cloud services is possible through\nServerless VPC Access, which allows App Engine to sit within\nthe same VPC as Compute Engine VMs and Google Kubernetes Engine clusters. As part of the\nintegration, we are moving App Engine builds to Cloud Build, which\nhas the following benefits:\n\n- Detailed build output including verbose warnings and errors\n\n- The ability to view build history in the Cloud Build section of\n the Cloud console\n\n- (Coming soon) The ability to include any library in your code in addition to\n the predefined set that is available in the App Engine runtimes\n\nAlmost all Google Cloud services require a payment method, so this\nadditional integration means that App Engine must also require a payment\nmethod.\n\nCosts of using Cloud Build\n--------------------------\n\nCloud Build has a free tier that includes 120 build minutes per\nbilling account, per day. For example, if your build took 5 minutes to complete,\nyou would be able to deploy 24 times a day without incurring any charges.\nFor more information on pricing beyond the free tier, see\n[Cloud Build pricing](/build/pricing).\n\nLimit your costs\n----------------\n\nYou can use the following mechanisms to limit your App Engine costs:\n\n- Set the [`max_instances`](/appengine/docs/standard/reference/app-yaml#scaling_elements)\n setting in your `app.yaml` configuration file to `1` to restrict your instance\n usage to the free tier.\n\n- [Set a budget and alerts](/billing/docs/how-to/budgets) to monitor your\n resource consumption across all Google Cloud services.\n\n- [Manually disable your app](/appengine/docs/standard/managing-projects-apps-billing#disabling_an_application)\n once it goes above a preset usage level."]]
