Skip to content

CloudFront Low Upload Bandwidth Over HTTP/2

1

We observed an issue where the upload bandwidth to CloudFront over HTTP/2 is extremely low compared to HTTP/1.1.

Below is an easily reproducible case run on a t4g.nano instance in the us-west-2 region. The test endpoint used below (https://dqb2o7n407g3m.cloudfront.net/upload-test) is simply proxied to a dummy Node.js server we've set up on an EC2 instance that drains the request body and responds with status 200.

We've replicated the issue in various conditions, including residential and commercial connections, different operating systems (Windows, Mac, Linux), and various clients and browsers. We also did the same test using an Nginx reverse proxy instead of CloudFront, and the results showed similar upload speeds over HTTP/2 and HTTP/1.1. So this clearly indicates an issue with CloudFront.

System info:

$ uname -r
6.1.147-172.259.amzn2023.aarch64
$ curl -V
curl 8.11.1 (aarch64-amazon-linux-gnu) libcurl/8.11.1 OpenSSL/3.2.2 zlib/1.2.11 libidn2/2.3.2 libpsl/0.21.5 nghttp2/1.59.0
Release-Date: 2024-12-11
Protocols: file ftp ftps http https ipfs ipns
Features: alt-svc AsynchDNS GSS-API HSTS HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz PSL SPNEGO SSL threadsafe UnixSockets

Prepare a 200MB test file:

$ truncate -s 200M testfile

Uploading the test file over HTTP/2 takes nearly 10 times the time compared to over HTTP/1.1:

$ time curl -v --ipv4 --http1.1 --data-binary @testfile https://dqb2o7n407g3m.cloudfront.net/upload-test
* Host dqb2o7n407g3m.cloudfront.net:443 was resolved.
* IPv6: (none)
* IPv4: 54.230.125.213, 54.230.125.162, 54.230.125.172, 54.230.125.90
*   Trying 54.230.125.213:443...
* ALPN: curl offers http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/pki/tls/certs/ca-bundle.crt
*  CApath: none
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / x25519 / RSASSA-PSS
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.cloudfront.net
*  start date: May  5 00:00:00 2025 GMT
*  expire date: Apr 23 23:59:59 2026 GMT
*  subjectAltName: host "dqb2o7n407g3m.cloudfront.net" matched cert's "*.cloudfront.net"
*  issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M01
*  SSL certificate verify ok.
*   Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 2: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
* Connected to dqb2o7n407g3m.cloudfront.net (54.230.125.213) port 443
* using HTTP/1.x
> POST /upload-test HTTP/1.1
> Host: dqb2o7n407g3m.cloudfront.net
> User-Agent: curl/8.11.1
> Accept: */*
> Content-Length: 209715200
> Content-Type: application/x-www-form-urlencoded
> Expect: 100-continue
> 
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
< HTTP/1.1 100 Continue
< 
* upload completely sent off: 209715200 bytes
< HTTP/1.1 200 OK
< Transfer-Encoding: chunked
< Connection: keep-alive
< Date: Thu, 07 Aug 2025 05:23:19 GMT
< X-Cache: Miss from cloudfront
< Via: 1.1 6ba3abdaa02208a6c3f49daf91689ad2.cloudfront.net (CloudFront)
< X-Amz-Cf-Pop: HIO50-C2
< Alt-Svc: h3=":443"; ma=86400
< X-Amz-Cf-Id: aGORXYAmFpjbSW-q5DZB02PPYeKZ4IP10KLTTF1De37j5Y_Rrs3BYA==
< 
* Connection #0 to host dqb2o7n407g3m.cloudfront.net left intact

real    0m2.636s
user    0m0.219s
sys     0m0.524s
$ time curl -v --ipv4 --http2 --data-binary @testfile https://dqb2o7n407g3m.cloudfront.net/upload-test
* Host dqb2o7n407g3m.cloudfront.net:443 was resolved.
* IPv6: (none)
* IPv4: 54.230.125.90, 54.230.125.172, 54.230.125.162, 54.230.125.213
*   Trying 54.230.125.90:443...
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/pki/tls/certs/ca-bundle.crt
*  CApath: none
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / x25519 / RSASSA-PSS
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=*.cloudfront.net
*  start date: May  5 00:00:00 2025 GMT
*  expire date: Apr 23 23:59:59 2026 GMT
*  subjectAltName: host "dqb2o7n407g3m.cloudfront.net" matched cert's "*.cloudfront.net"
*  issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M01
*  SSL certificate verify ok.
*   Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 2: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
* Connected to dqb2o7n407g3m.cloudfront.net (54.230.125.90) port 443
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://dqb2o7n407g3m.cloudfront.net/upload-test
* [HTTP/2] [1] [:method: POST]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: dqb2o7n407g3m.cloudfront.net]
* [HTTP/2] [1] [:path: /upload-test]
* [HTTP/2] [1] [user-agent: curl/8.11.1]
* [HTTP/2] [1] [accept: */*]
* [HTTP/2] [1] [content-length: 209715200]
* [HTTP/2] [1] [content-type: application/x-www-form-urlencoded]
> POST /upload-test HTTP/2
> Host: dqb2o7n407g3m.cloudfront.net
> User-Agent: curl/8.11.1
> Accept: */*
> Content-Length: 209715200
> Content-Type: application/x-www-form-urlencoded
> 
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* upload completely sent off: 209715200 bytes
< HTTP/2 200 
< date: Thu, 07 Aug 2025 05:23:52 GMT
< x-cache: Miss from cloudfront
< via: 1.1 c3270a6ec9acbf35e35962d1054f78d4.cloudfront.net (CloudFront)
< x-amz-cf-pop: HIO50-C2
< alt-svc: h3=":443"; ma=86400
< x-amz-cf-id: ck-wCBiWcMq-K1e6cliNDROZ3b7cumLSQPs9tL83h3-dV7J9rdlwKw==
< 
* Connection #0 to host dqb2o7n407g3m.cloudfront.net left intact

real    0m21.847s
user    0m8.094s
sys     0m4.780s
  • Just to further clarify a few important aspects of the issue:

    • The term "bandwidth" in my original post may be a bit misleading. The actual problem is with the throughput over a single HTTP/2 connection. If we start multiple uploads in parallel, the link bandwidth can indeed be saturated. However, for applications that rely on a single long-lived HTTP/2 connection (like large file uploads), the degraded performance is a real concern.

    • To emphasize the severity of the problem: in the example test result shown above, uploading 200MB over HTTP/2 took ~22 seconds, which translates to ~70 Mbps. This compares to ~2.6 seconds over HTTP/1.1, or ~600 Mbps. 70 Mbps might still seem like an acceptable upload speed in some contexts. However, we've also performed the test on a 200 Mbps connection, and the HTTP/2 upload took over 90 seconds, which means throughput dropped to below 20 Mbps. This is a massive degradation compared to the 8 seconds it took over HTTP/1.1 using the same connection. This demonstrates that the issue scales poorly with available bandwidth, and becomes even more problematic on lower-speed connections where the upload performance over HTTP/2 can become unusably slow, despite there still being plenty of available link capacity.

  • We’ve done some additional testing to see how latency affects this behavior. On the same t4g.nano instance, we introduced 100 ms of delay to the link using: tc qdisc add dev ens5 root netem delay 100ms. With this setup, the HTTP/2 upload took a whooping 5 minutes, while the HTTP/1.1 upload took only 10 seconds. This again shows the issue worsens significantly over high-latency links like certain mobile connections. In these cases HTTP/2 uploads to CloudFront can become effectively unusable, while HTTP/1.1 remains performant.

asked a year ago532 views

1 Answer
0

Based on your test results, there's a significant performance difference when uploading large files to CloudFront over HTTP/2 versus HTTP/1.1. The HTTP/2 upload took approximately 21.8 seconds while the same file over HTTP/1.1 took only 2.6 seconds - nearly 10 times faster.

This issue appears to be specific to CloudFront's implementation of HTTP/2 for upload scenarios. Since you've tested the same configuration with Nginx as a reverse proxy and didn't see this performance discrepancy, it points to a CloudFront-specific limitation.

There are several potential reasons for this behavior:

  1. Flow control implementation: HTTP/2 implements flow control mechanisms that might be configured conservatively in CloudFront's edge locations, limiting upload bandwidth.

  2. Window size settings: HTTP/2 uses flow control windows that determine how much data can be in transit. CloudFront might have smaller window size settings for uploads over HTTP/2.

  3. Edge location configuration: The specific CloudFront edge location you're connecting to (HIO50-C2 in your logs) might have particular settings or limitations affecting HTTP/2 upload performance.

  4. Request handling differences: CloudFront might process HTTP/2 POST requests with large payloads differently than HTTP/1.1 requests.

Since you've already verified this issue across multiple client environments and compared against another reverse proxy implementation, this appears to be a limitation in CloudFront's HTTP/2 implementation specifically for upload scenarios.

For your use case, if upload performance is critical, you might need to:

  1. Force your applications to use HTTP/1.1 for upload operations to CloudFront
  2. Consider using direct uploads to S3 with pre-signed URLs for large files
  3. Implement a different CDN or reverse proxy for upload-heavy workloads

This behavior is likely related to how CloudFront optimizes for the more common download-heavy CDN use cases rather than large uploads.
Sources
Post request with form-data via Cloudfront | AWS re:Post

answered a year ago

  • We are hoping that CloudFront is the one-stop shop for optimizing both downloads and uploads globally. Even if CloudFront is primarily optimized for download-heavy use cases, a 10x performance difference is quite substantial and, frankly, unexpected from a mature CDN service like CloudFront. It would be ideal if this issue could be raised to someone in the CloudFront engineering team for investigation.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.