Why does fastly trigger a 307 redirect from s3 regional (non-standard) bucket

Comments

3 comments

  • Joe Garrison

    Hi Chris, thanks for reaching out to Fastly Support! I've provided a document below that should fix the issue you're having. Take a look at that and let me know if you have any questions.

     

    Link here [https://docs.fastly.com/en/guides/amazon-s3#following-redirects-to-s3-objects-and-caching-s3-responses ]

    0
    Comment actions Permalink
  • Chris Roebuck

    Hi Joe,

     

    Yes I'd seen that article and have tried it in my vcl. I think that article describes serving content from a bucket in only one region. 

     

    If you try to serve content from a bucket in a non-standard region it seems that s3 now sends a 307 redirect to the region specific endpoint when trying to use the global endpoint. So it seems we need a backend per region to get around this.

    0
    Comment actions Permalink
  • Joe Garrison

    Can you submit this as a ticket so we can look at your current configuration in more detail?

    0
    Comment actions Permalink

Please sign in to leave a comment.