Conversation
github-actions
Bot
added
the
documentation
✅ Deploy Preview will be available once build job completes!
|
puneetsarna
reviewed
Jul 16, 2026
| | debug_points | NGINXaaS does not provide access to NGINX processes for debugging. | | ||
| | fastcgi_bind <br /> grpc_bind <br /> memcached_bind <br /> proxy_bind <br /> scgi_bind <br /> uwsgi_bind | Source IP specification for active-active deployments is not allowed. | | ||
| | quic_bpf | QUIC connection migration is not currently supported for active-active deployments. | | ||
| | ssl_ech_file | NGINXaaS does not use the OpenSSL ECH feature branch. | |
Contributor
There was a problem hiding this comment.
the reasoning in itself is slightly vague. Maybe add a link to the directive which has that support statement and links to the ECH branch
puneetsarna
reviewed
Jul 16, 2026
puneetsarna
reviewed
Jul 16, 2026
| ## July 20, 2026 | ||
| NGINXaaS is now running NGINX Plus 37.0 (PLS.37.0). | ||
|
|
||
| NGINXaaS for Google Cloud deployments have been automatically upgraded to NGINX Plus 37.0 (PLS.37.0). Please review the [NGINX Plus Release 37.0]({{< ref "/nginx/releases/#pls.37.0.2" >}}) Release Notes carefully. Please note that HTTP/1.1 is now the default protocol for upstreams, and keepalive is enabled by default for HTTP/1.1 upstreams. Additionally, due to the new upstream histogram metric, zone memory requirements have increased by 25%. |
Contributor
There was a problem hiding this comment.
- Is that increase in zone requirement permanent or is there a way, i.e., a customer always has to do so or is there a way to turn off that behavior?
- Do we have official documentation from NGINX as well around it?
- What happens if a customer does not follow the zone requirement guidance and goes with it anyway? do they get errors, does their traffic still work or prone to hit those errors?
puneetsarna
reviewed
Jul 16, 2026
|
|
||
| NGINXaaS for Google Cloud deployments have been automatically upgraded to NGINX Plus 37.0 (PLS.37.0). Please review the [NGINX Plus Release 37.0]({{< ref "/nginx/releases/#pls.37.0.2" >}}) Release Notes carefully. Please note that HTTP/1.1 is now the default protocol for upstreams, and keepalive is enabled by default for HTTP/1.1 upstreams. Additionally, due to the new upstream histogram metric, zone memory requirements have increased by 25%. | ||
|
|
||
| NGINX Plus 37.0 (PLS.37.0) introduces new configuration directives and changes to existing directives. NGINXaaS for Google Cloud does not support the `ssl_ech_file` directive. For more information, review the unsupported directives listed in [Disallowed configuration directives]({{< ref "/nginxaas/google/deploy/nginx-configuration/overview/#disallowed-configuration-directives" >}}). |
Contributor
There was a problem hiding this comment.
As I am reading through this doc and https://docs.nginx.com/nginx/releases/#intro, a question comes up on what a user will get as part of NGINXaaS. Is it the LTS release or CR model?
Contributor
Author
There was a problem hiding this comment.
Added LTS as part of the title
edarzins
requested changes
Jul 16, 2026
|
|
||
| For a complete list of allowed directives, see the [Configuration Directives List]({{< ref "/nginxaas/google/deploy/nginx-configuration/overview/#configuration-directives-list" >}}). | ||
|
|
||
|
|
Contributor
There was a problem hiding this comment.
Also need to note that we also upgraded F5 WAF for NGINX to version 5.13.3 -- release notes for that version are here: https://docs.nginx.com/waf/changelog/#f5-waf-for-nginx-5133
amudukutore
reviewed
Jul 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed changes
Announce NGINX Plus 37 availability and update directives list
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩