Support for Java 25 runtime is in General Availability.
]]>Support for Java 25 runtime is in Preview.
]]>Support for TLS version 1.2 and later, along with a corresponding secure set of cipher suites, is in General Availability (GA).
]]>To increase security, starting in March 2025, support for Transport Layer Security (TLS) version 1.1 and earlier is deprecated. Update your application settings in the App Engine flexible environment to use TLS version 1.2 and later, along with a corresponding secure set of cipher suites (Preview).
]]>Container Registry is now shut down. We recommend that you use Artifact Registry for storing and managing container images. By default, new deployments created after March 5, 2025, use Artifact Registry instead of Container Registry for storing application build images. For more information, see Migrate App Engine container images to Artifact Registry.
]]>Java 11 has reached end of support. You cannot re-deploy versions that use runtimes after their end of support date. We recommend that you upgrade your app to use the latest version of Java.
]]>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:
Editor role to the App Engine default
services accounts by default.If you are impacted by this change, you can do the following:
Java 21 is now generally available.
]]>A warning message now appears before you publish a container image to a public repository.
]]>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 Java runtime now supports using Maven wrappers for managing your project's dependency on Maven.
]]>Java 11 and 17 are now generally available. These versions require you to specify an operating system version in your app.yaml. Learn more.
]]>You can now use ssh to log in to App Engine flexible environment instances that use only internal IP addresses.
The Java runtime versions 11 and 17 are now available in preview, and are built on modern and secure operating systems (Ubuntu 18 and 22). These new runtime versions use Google Cloud's buildpacks and require updates to your app.yaml. Learn more.
]]>You can now use any configured service account in your Cloud project as the app-level default service account, while creating and updating your App Engine applications.
]]>The option to set IP mode to internal for App Engine flexible environment instances is now generally available.
You can now disable external ephemeral IP addresses for App Engine Flex services. Read our documentation to learn how. This feature is at the Preview launch stage.
]]>Specifying a user-managed service account for each App Engine version during deployment is now generally available.
]]>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 internal services to the App Engine flexible environment no longer originate from 10.0.0.1. The IP ranges are as follows:
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 both 0.1.0.1 and 10.0.0.1.0.1.0.2. Previously, these requests came from both 0.1.0.2 and 10.0.0.1.0.1.0.40. Previously, these requests came from both 0.1.0.40 and 10.0.0.1.For more information, see Understanding the App Engine firewall.
]]>App Engine is now available in the us-west1 (Oregon), asia-southeast1 (Singapore), and asia-east1 (Taiwan) regions.
App Engine is now available in the europe-central2 region (Warsaw).
You can use network ingress controls so your app only receives requests that are sent from your project's VPC or that are routed through the Cloud Load Balancing load balancer. This feature is now generally available.
]]>You can use network ingress controls so your app only receives requests that are sent from your project's VPC or that are routed through the Cloud Load Balancing load balancer.
]]>External HTTP(S) Load Balancing is now supported for App Engine via Serverless network endpoint groups. Notably, this feature allows you to use Cloud CDN with App Engine.
This feature is available in Beta.
App Engine is now available in the asia-southeast2 region (Jakarta).
To get a fine-grained view of billing data for each resource used by your App Engine services, you can apply labels to the services, export your billing data to BigQuery, and run queries. For more information, see Labeling App Engine resources.
]]>App Engine is now available in the us-west4 region (Las Vegas, NV).