Serving websites from S3

luislavena · May 19, 2011, 12:40am

Hi guys, I’ve tried to ask pretty much everywhere, but no solution until
now. I’m quite sure I’m doing something wrong here, but to be honest I’m
not able to catch it.

I’m rewriting urls from test.foo.com to
bar.foo.com.s3.amazonaws.com/test, and everything works like a charm. If
I point the browser to test.foo.com/index.html nginx serves my static
website exactly as I want. The problem I’m facing now is that I’m not
able to have nginx serve my index.html by default, while retrieving
test.foo.com/

I’ve tried both try_files and index so far, with no result. I’ve also
tried to catch 404s and serve my index.html page (even though I guess
this is a bad practice).

This is what I have right now:

gist.github.com

https://gist.github.com/ngw/9a1ca5095392fb083f05

gistfile1.txt

server {

        listen   80; ## listen for ipv4
        listen   [::]:80 default ipv6only=on; ## listen for ipv6

        server_name "~^(.+)\.stylej\.am$";

        access_log  /var/log/nginx/stylejam-star.access.log;

        set $subdomain $1;

This file has been truncated. show original

Can someone help me? I’m a bit out of ideas.

What is really strange to me is that (real example)
http://test.stylej.am/ answers with a 404, I really have no idea why
try_files doesn’t work… Maybe $url/index.html is not right and I
should use another syntax?

ngw

Nicholas_W · May 19, 2011, 11:17am

On Wed, 2011-05-18 at 15:40 -0700, Nicholas W. wrote:

retrieving test.foo.com/

Can someone help me? I’m a bit out of ideas.

What is really strange to me is that (real example)
http://test.stylej.am/ answers with a 404, I really have no idea why
try_files doesn’t work… Maybe $url/index.html is not right and I
should use another syntax?

You know that Amazon added support for index files to S3?

Try_files does not work because it looks for acrual files on your file
system, and thats not where S3 is! You can use two locations, one to
match just / and one to match all other files.

Justin