starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 09:55:51 +03:00

[GH-ISSUE #357] Adding AWS S3 bucket hosting as an option #307

New issue

Closed

opened 2026-02-26 06:32:12 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 06:32:12 +03:00

Owner

Originally created by @dpanesso on GitHub (Apr 10, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/357

Is your feature request related to a problem? Please describe.
We manage around 30 hosts on our nginx reverse proxy. About 1/3 of those are hosted on AWS S3. We need https on almost all of them and using something like Cloudfront to have SSL would be overkill.

Describe the solution you'd like
Add an option on the Proxy hosts to use S3 as a forward option. This would change the location block to use the options needed for it to work. Something like this is what we use:

        proxy_http_version     1.1;
        proxy_set_header       Connection "";
        proxy_set_header       Authorization '';
        proxy_set_header       Host bucket.s3-website-us-east-1.amazonaws.com;
        proxy_hide_header      x-amz-id-2;
        proxy_hide_header      x-amz-request-id;
        proxy_hide_header      x-amz-meta-server-side-encryption;
        proxy_hide_header      x-amz-server-side-encryption;
        proxy_hide_header      Set-Cookie;
        proxy_ignore_headers   Set-Cookie;
        proxy_intercept_errors on;
        add_header             Cache-Control max-age=31536000;
        proxy_pass             http://bucket.s3-website-us-east-1.amazonaws.com/;

The maximum length of the forward_host variable would also have to be increased as 50 is too small.

Describe alternatives you've considered
I considered using the custom location option but, the host parameter is set in the non editable section of proxy.conf

Additional context
This would be my proposal:

I have made some progress on development. I can open a PR to check out my progress. I would consider some additional validations for it to be complete.

Originally created by @dpanesso on GitHub (Apr 10, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/357 **Is your feature request related to a problem? Please describe.** We manage around 30 hosts on our nginx reverse proxy. About 1/3 of those are hosted on AWS S3. We need https on almost all of them and using something like Cloudfront to have SSL would be overkill. **Describe the solution you'd like** Add an option on the Proxy hosts to use S3 as a forward option. This would change the location block to use the options needed for it to work. Something like this is what we use: ``` proxy_http_version 1.1; proxy_set_header Connection ""; proxy_set_header Authorization ''; proxy_set_header Host bucket.s3-website-us-east-1.amazonaws.com; proxy_hide_header x-amz-id-2; proxy_hide_header x-amz-request-id; proxy_hide_header x-amz-meta-server-side-encryption; proxy_hide_header x-amz-server-side-encryption; proxy_hide_header Set-Cookie; proxy_ignore_headers Set-Cookie; proxy_intercept_errors on; add_header Cache-Control max-age=31536000; proxy_pass http://bucket.s3-website-us-east-1.amazonaws.com/; ``` The maximum length of the forward_host variable would also have to be increased as 50 is too small. **Describe alternatives you've considered** I considered using the custom location option but, the host parameter is set in the non editable section of proxy.conf **Additional context** This would be my proposal: ![image](https://user-images.githubusercontent.com/2687121/78966237-dee5c400-7ac4-11ea-8f9f-e512f7715bd4.png) I have made some progress on development. I can open a PR to check out my progress. I would consider some additional validations for it to be complete.

kerem

2026-02-26 06:32:12 +03:00

closed this issue
added the
enhancement

stale
labels

kerem commented

2026-02-26 06:32:12 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 30, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Mar 30, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 06:32:12 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 9, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (May 9, 2025): Issue was closed due to inactivity.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#307

No description provided.

Rows
Columns