Jekyll Deployed to AWS S3 Links Not Working











up vote
1
down vote

favorite












I created a Jekyll page and got it uploaded to AWS S3 through Travis. The links aren't working. For example:



https://s3.amazonaws.com/data-flood - doesn't work
https://s3.amazonaws.com/data-flood/index.html - works



When accessing specific files they work
https://s3.amazonaws.com/data-flood/images/picture1.jpeg - works



But accessing folders they don't work:
http://s3.amazonaws.com/data-flood/blog - doesn't work
index.html is in /blog/ but http://s3.amazonaws.com/data-flood/blog/index.html - works



Here's my working GitHub Pages: https://dighr.github.io/data-flood/



My GitHub Repo: https://github.com/richardt22/data-flood



Thanks in advance.










share|improve this question




























    up vote
    1
    down vote

    favorite












    I created a Jekyll page and got it uploaded to AWS S3 through Travis. The links aren't working. For example:



    https://s3.amazonaws.com/data-flood - doesn't work
    https://s3.amazonaws.com/data-flood/index.html - works



    When accessing specific files they work
    https://s3.amazonaws.com/data-flood/images/picture1.jpeg - works



    But accessing folders they don't work:
    http://s3.amazonaws.com/data-flood/blog - doesn't work
    index.html is in /blog/ but http://s3.amazonaws.com/data-flood/blog/index.html - works



    Here's my working GitHub Pages: https://dighr.github.io/data-flood/



    My GitHub Repo: https://github.com/richardt22/data-flood



    Thanks in advance.










    share|improve this question


























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I created a Jekyll page and got it uploaded to AWS S3 through Travis. The links aren't working. For example:



      https://s3.amazonaws.com/data-flood - doesn't work
      https://s3.amazonaws.com/data-flood/index.html - works



      When accessing specific files they work
      https://s3.amazonaws.com/data-flood/images/picture1.jpeg - works



      But accessing folders they don't work:
      http://s3.amazonaws.com/data-flood/blog - doesn't work
      index.html is in /blog/ but http://s3.amazonaws.com/data-flood/blog/index.html - works



      Here's my working GitHub Pages: https://dighr.github.io/data-flood/



      My GitHub Repo: https://github.com/richardt22/data-flood



      Thanks in advance.










      share|improve this question















      I created a Jekyll page and got it uploaded to AWS S3 through Travis. The links aren't working. For example:



      https://s3.amazonaws.com/data-flood - doesn't work
      https://s3.amazonaws.com/data-flood/index.html - works



      When accessing specific files they work
      https://s3.amazonaws.com/data-flood/images/picture1.jpeg - works



      But accessing folders they don't work:
      http://s3.amazonaws.com/data-flood/blog - doesn't work
      index.html is in /blog/ but http://s3.amazonaws.com/data-flood/blog/index.html - works



      Here's my working GitHub Pages: https://dighr.github.io/data-flood/



      My GitHub Repo: https://github.com/richardt22/data-flood



      Thanks in advance.







      amazon-web-services github amazon-s3 jekyll github-pages






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 1 at 22:53

























      asked Oct 31 at 19:56









      Richard Trinh

      143




      143
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          S3 cannot do extensionless urls on its own - so /data-flood won't work no matter what I don't think. But if you add a trailing slash it should work, but for some reason it is not.



          It looks like the url you are using is not serving files like a webserver - I think the correct url should be:



          http://data-flood.s3.amazonaws.com/index.html



          that almost works, but still the urls need an index.html added to them, I think this has something to do with the bucket policy but not sure.



          A normalish bucket policy for a website could look like:




          {"Version":"2008-10-17","Statement":[{"Sid":"PublicReadForGetBucketObjects","Effect":"Allow","Principal":{"AWS":"*"},"Action":"s3:GetObject","Resource":"arn:aws:s3:::data-flood/*"}]}



          not sure I got your arn correct but maybe.






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














             

            draft saved


            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53091051%2fjekyll-deployed-to-aws-s3-links-not-working%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            S3 cannot do extensionless urls on its own - so /data-flood won't work no matter what I don't think. But if you add a trailing slash it should work, but for some reason it is not.



            It looks like the url you are using is not serving files like a webserver - I think the correct url should be:



            http://data-flood.s3.amazonaws.com/index.html



            that almost works, but still the urls need an index.html added to them, I think this has something to do with the bucket policy but not sure.



            A normalish bucket policy for a website could look like:




            {"Version":"2008-10-17","Statement":[{"Sid":"PublicReadForGetBucketObjects","Effect":"Allow","Principal":{"AWS":"*"},"Action":"s3:GetObject","Resource":"arn:aws:s3:::data-flood/*"}]}



            not sure I got your arn correct but maybe.






            share|improve this answer

























              up vote
              0
              down vote













              S3 cannot do extensionless urls on its own - so /data-flood won't work no matter what I don't think. But if you add a trailing slash it should work, but for some reason it is not.



              It looks like the url you are using is not serving files like a webserver - I think the correct url should be:



              http://data-flood.s3.amazonaws.com/index.html



              that almost works, but still the urls need an index.html added to them, I think this has something to do with the bucket policy but not sure.



              A normalish bucket policy for a website could look like:




              {"Version":"2008-10-17","Statement":[{"Sid":"PublicReadForGetBucketObjects","Effect":"Allow","Principal":{"AWS":"*"},"Action":"s3:GetObject","Resource":"arn:aws:s3:::data-flood/*"}]}



              not sure I got your arn correct but maybe.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                S3 cannot do extensionless urls on its own - so /data-flood won't work no matter what I don't think. But if you add a trailing slash it should work, but for some reason it is not.



                It looks like the url you are using is not serving files like a webserver - I think the correct url should be:



                http://data-flood.s3.amazonaws.com/index.html



                that almost works, but still the urls need an index.html added to them, I think this has something to do with the bucket policy but not sure.



                A normalish bucket policy for a website could look like:




                {"Version":"2008-10-17","Statement":[{"Sid":"PublicReadForGetBucketObjects","Effect":"Allow","Principal":{"AWS":"*"},"Action":"s3:GetObject","Resource":"arn:aws:s3:::data-flood/*"}]}



                not sure I got your arn correct but maybe.






                share|improve this answer












                S3 cannot do extensionless urls on its own - so /data-flood won't work no matter what I don't think. But if you add a trailing slash it should work, but for some reason it is not.



                It looks like the url you are using is not serving files like a webserver - I think the correct url should be:



                http://data-flood.s3.amazonaws.com/index.html



                that almost works, but still the urls need an index.html added to them, I think this has something to do with the bucket policy but not sure.



                A normalish bucket policy for a website could look like:




                {"Version":"2008-10-17","Statement":[{"Sid":"PublicReadForGetBucketObjects","Effect":"Allow","Principal":{"AWS":"*"},"Action":"s3:GetObject","Resource":"arn:aws:s3:::data-flood/*"}]}



                not sure I got your arn correct but maybe.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered yesterday









                Ron

                769617




                769617






























                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53091051%2fjekyll-deployed-to-aws-s3-links-not-working%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Create new schema in PostgreSQL using DBeaver

                    Deepest pit of an array with Javascript: test on Codility

                    Costa Masnaga