Timeline for What is the 'right way' to serve static content from my AWS S3 bucket on my ElasticBeanstalk deployment?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 10:32 | history | edited | CommunityBot |
Commonmark migration
|
|
| Jan 7, 2017 at 11:09 | history | edited | MrWhite | CC BY-SA 3.0 |
Suggested using a subdomain for the CDN/proxy
|
| Jan 7, 2017 at 11:05 | comment | added | MrWhite | For a reverse proxy it's AWS Elastic Beanstalk (the source) that would really need the proxy capability configured. However, the target (S3) could potentially reject the request. But I'm not sure exactly how this would be configured. You might also be able to code something yourself using CURL (ie. rewrite these URLs to your CURL script that makes the necessary request and returns the response to the client.) - however, I wonder what extra load this would place on the server and whether it might slow things down a bit? | |
| Jan 7, 2017 at 5:52 | comment | added | Abhishek Divekar | Hi, thanks for the response. The <base> element seems to be working, but the proxy is not set up in S3 by default. Any idea how to do this (without inadvertently breaking something else). | |
| Jan 5, 2017 at 8:59 | history | edited | MrWhite | CC BY-SA 3.0 |
Updated URL to CDN (used the wrong one from the question)
|
| Jan 5, 2017 at 8:53 | history | answered | MrWhite | CC BY-SA 3.0 |