From 96a02299fd7732bf7acbc672d00b28b712953b55 Mon Sep 17 00:00:00 2001
From: Chris Lu <chris.lu@gmail.com>
Date: Thu, 1 Jan 2026 11:46:56 -0800
Subject: [PATCH] Revert "Updated S3 Nginx Proxy (markdown)"

This reverts commit 0bfcee97d3dd5022172ba01e734041fe7170e483.
---
 S3-Nginx-Proxy.md | 20 +-------------------
 1 file changed, 1 insertion(+), 19 deletions(-)

diff --git a/S3-Nginx-Proxy.md b/S3-Nginx-Proxy.md
index b8012f3..ee7701c 100644
--- a/S3-Nginx-Proxy.md
+++ b/S3-Nginx-Proxy.md
@@ -156,22 +156,4 @@ server {
 	ssl on;
 	ssl_certificate /{path_to_ssl_cert}/cert.pem;
 	ssl_certificate_key /{path_to_ssl_cert}/key.pem;
-}
-```
-
-## Kubernetes Ingress
-
-When using Kubernetes Ingress (nginx-ingress controller), you must disable request buffering to prevent signature verification failures on write operations (PUT, POST). Without this setting, nginx removes the `Transfer-Encoding: chunked` header that S3 clients include in their signature, causing 403 Forbidden errors on uploads while reads work fine.
-
-**Required Helm chart configuration:**
-
-```yaml
-s3:
-  ingress:
-    enabled: true
-    className: nginx
-    host: s3.example.com
-    annotations:
-      nginx.ingress.kubernetes.io/proxy-request-buffering: "off"
-      nginx.ingress.kubernetes.io/proxy-body-size: "0"
-```
+}
\ No newline at end of file