Support for enabling only needed legacy bundled services using the
app_engine_bundled_services
field is in General Availability.
App Engine supports Direct VPC egress in Preview. Direct VPC egress lets your workloads access VPC network resources as a simpler, more cost-effective alternative to Serverless VPC Access connectors.
]]>Enable only needed legacy bundled services using the app_engine_bundled_services field for improved security and maintainability of your applications (Preview).
The App Engine Migration hub lets you migrate services in the App Engine standard environment to Cloud Run, and also provides cost-saving recommendations. For more information, see Deploy an App Engine app in the standard environment to Cloud Run (Preview).
]]>Support for the PHP 8.5 runtime is in General Availability.
]]>Support for deploying your existing apps in the standard environment to Cloud Run using
the gcloud beta app migrate-to-run command is in Preview. For more information, see Deploy an App Engine app in the standard environment to Cloud Run.
Support for the PHP 8.5 runtime is in Preview.
]]>PHP 5 is deprecated. You won't be able to deploy PHP 5 applications, even if your organization previously used an organization policy to re-enable deployments of legacy runtimes. Your existing PHP 5 applications will continue to run and receive traffic. We recommend that you migrate to the latest supported version of PHP.
]]>Support for TLS version 1.2 and later, along with a corresponding secure set of cipher suites, is in General Availability (GA).
]]>Support for the PHP 8.4 runtime is in General Availability (GA).
]]>Support for PHP 8.4 runtime is in Preview.
]]>Custom organization policies for Serverless VPC Access connectors are now generally available, and can be applied to projects, folders, or organizations.
]]>The runtime support schedule for some PHP runtimes has been extended to match PHP's public support schedule.
]]>In the App Engine page in the Google Cloud console, you can now filter your existing App Engine versions by runtime lifecycle stages. After you apply this filter, the console displays a warning icon for App Engine versions that are approaching end of support, have reached end of support, are deprecated, and are decomissioned.
]]>Deployments for new projects might be impacted from the following changes to org policies:
Starting in May 2024, Google Cloud enforces secure-by-default organization policies for all organization resources. This policy
prevents App Engine from granting the Editor role to the App Engine default
services accounts by default.
Starting in June 2024, Cloud Build has changed the default behavior for how Cloud Build uses service accounts in new projects. This change is detailed in Cloud Build Service Account Change. As a result of this change, new projects deploying versions for the first time may be using the default App Engine service account with insufficient permissions for deploying versions.
If you are impacted by this change you can do one of the following:
Grant the Editor role to the App Engine default service account.
Review the Cloud Build guidance on changes to the default service account and opt out of these changes.
Accessing a service that's prohibited by the Internal or Internal and Cloud Load Balancing ingress setting now results in a 404 rather than 403 error code.
The PHP 8.2 runtime for App Engine standard environment is now generally available.
]]>Memory limits for second-generation runtimes have been increased to better support the growing memory utilization of many newer runtimes.
]]>If you use the local development server to simulate an App Engine app in production, you must now run dev_appserver.py with Python 3 and set the CLOUDSDK_DEVAPPSERVER_PYTHON environment variable in your shell to the path of your Python 2 interpreter. Learn more about the required setup steps.
The PHP 8.2 runtime for App Engine standard environment is now available in preview.
]]>Specifying a user-managed service account for each App Engine version during deployment is now generally available.
]]>The PHP 8.1 runtime for App Engine standard environment is now available at the Preview release level.
]]>The App Engine legacy bundled services for PHP 7+ are now available at the Preview release level. These APIs can be accessed through language-idiomatic libraries. Calls to these API are billed according to the standard rates.
]]>Support for Serverless VPC Access connectors in Shared VPC host projects is now at general availability (GA). Learn about the advantages of this method and how to configure connectors in host projects.
]]>Builds are now handled by regional Cloud Build pools within the selected App Engine region. To view build logs, go to Cloud Build in the Cloud Console, select the History page, and select the region you would like to filter by.
]]>Egress settings for Serverless VPC Access are now generally available. Egress settings allow you to specify whether or not to send traffic with external destinations through your Serverless VPC Access connector, which is necessary if you want to set up a static outbound IP address for your App Engine service.
]]>Egress settings are now available for Serverless VPC Access. Egress settings allow you to specify whether or not to send traffic with external destinations through your Serverless VPC Access connector, which is necessary if you want to set up a static outbound IP address for your App Engine service.
]]>Specifying a user-managed service account for each App Engine version during deployment is now available in preview. This feature lets you grant different privileges to each version, based on the specific tasks it performs, and avoid granting more privileges than necessary.
Requests from newly created or updated App Engine Cron jobs sent to the App Engine standard environment now come from 0.1.0.2. For Cron jobs created with older gcloud versions (earlier than 326.0.0), Cron requests will come from 0.1.0.1. Previously, these requests only came from 0.1.0.1. See Understanding the App Engine firewall for more information.
App Engine is now available in the us-west1 (Oregon), asia-southeast1 (Singapore), and asia-east1 (Taiwan) regions.
Automatic scaling elements min_instances and min_idle_instances will now only apply to versions of a service that have been configured to receive traffic. This change is to reduce unexpected billing due to instances running old versions that are not intended to receive traffic.