AWS AWSCloudFormation documentation change

Service: AWSCloudFormation · 2025-11-22 · Documentation low

File: AWSCloudFormation/latest/TemplateReference/aws-resource-elasticloadbalancingv2-listener.md

Summary

Added QUIC and TCP_QUIC protocol support documentation for Network Load Balancers, including protocol restrictions with dual-stack mode and a new QUIC listener configuration example

Security assessment

The change documents support for QUIC protocol which uses TLS 1.3 encryption by default, enhancing secure communication capabilities. While this adds security-related documentation about encrypted transport protocols, there is no evidence of addressing a specific security vulnerability.

Diff

diff --git a/AWSCloudFormation/latest/TemplateReference/aws-resource-elasticloadbalancingv2-listener.md b/AWSCloudFormation/latest/TemplateReference/aws-resource-elasticloadbalancingv2-listener.md
index 47dbfd116..2c7bc58aa 100644
--- a//AWSCloudFormation/latest/TemplateReference/aws-resource-elasticloadbalancingv2-listener.md
+++ b//AWSCloudFormation/latest/TemplateReference/aws-resource-elasticloadbalancingv2-listener.md
@@ -147 +147 @@ _Required_ : No
-The protocol for connections from clients to the load balancer. For Application Load Balancers, the supported protocols are HTTP and HTTPS. For Network Load Balancers, the supported protocols are TCP, TLS, UDP, and TCP_UDP. You can’t specify the UDP or TCP_UDP protocol if dual-stack mode is enabled. You can't specify a protocol for a Gateway Load Balancer.
+The protocol for connections from clients to the load balancer. For Application Load Balancers, the supported protocols are HTTP and HTTPS. For Network Load Balancers, the supported protocols are TCP, TLS, UDP, TCP_UDP, QUIC, and TCP_QUIC. You can’t specify the UDP, TCP_UDP, QUIC, or TCP_QUIC protocol if dual-stack mode is enabled. You can't specify a protocol for a Gateway Load Balancer.
@@ -153 +153 @@ _Required_ : No
- _Allowed values_ : `HTTP | HTTPS | TCP | TLS | UDP | TCP_UDP | GENEVE`
+ _Allowed values_ : `HTTP | HTTPS | TCP | TLS | UDP | TCP_UDP | GENEVE | QUIC | TCP_QUIC`
@@ -206,0 +207,2 @@ After you create your load balancer using [AWS::ElasticLoadBalancingV2::LoadBala
+  * Create a QUIC listener
+
@@ -443,0 +446,41 @@ The following example creates a UDP listener with a default action that forwards
+### Create a QUIC listener
+
+The following example creates a QUIC listener with a default action that forwards traffic to the specified target group. You can create the target group using [AWS::ElasticLoadBalancingV2::TargetGroup](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-elasticloadbalancingv2-targetgroup.html).
+
+#### YAML
+    
+    
+    myQUICListener:
+      Type: 'AWS::ElasticLoadBalancingV2::Listener'
+      Properties: 
+        LoadBalancerArn: !Ref myLoadBalancer
+        Protocol: QUIC
+        Port: 443
+        DefaultActions:
+          - Type: forward
+            TargetGroupArn: !Ref myTargetGroup
+
+#### JSON
+    
+    
+    {
+        "myUDPListener": {
+            "Type": "AWS::ElasticLoadBalancingV2::Listener",
+            "Properties": {
+                "LoadBalancerArn": {
+                    "Ref": "myLoadBalancer"
+                },
+                "Protocol": "QUIC",
+                "Port": 443,
+                "DefaultActions": [
+                    {
+                        "Type": "forward",
+                        "TargetGroupArn": {
+                            "Ref": "myTargetGroup"
+                        }
+                    }
+                ]
+            }
+        }
+    }
+