Where does Elastic Beanstalk store the nginx configuration file? And how does one modiy it?












0















In my Elastic Beanstalk instance, I am able to select Nginx to be the proxy in front of my instance.



However, it gives no indication of where the config file (i.e. /nginx/conf.d/proxy.conf) might be, nor how to make changes to it.



I found some documentation that mentions the conf file, but offers no information on how to see it live or make changes to it.



Does anyone know how to read and edit the nginx conf on an Elastic Beanstalk application?










share|improve this question



























    0















    In my Elastic Beanstalk instance, I am able to select Nginx to be the proxy in front of my instance.



    However, it gives no indication of where the config file (i.e. /nginx/conf.d/proxy.conf) might be, nor how to make changes to it.



    I found some documentation that mentions the conf file, but offers no information on how to see it live or make changes to it.



    Does anyone know how to read and edit the nginx conf on an Elastic Beanstalk application?










    share|improve this question

























      0












      0








      0








      In my Elastic Beanstalk instance, I am able to select Nginx to be the proxy in front of my instance.



      However, it gives no indication of where the config file (i.e. /nginx/conf.d/proxy.conf) might be, nor how to make changes to it.



      I found some documentation that mentions the conf file, but offers no information on how to see it live or make changes to it.



      Does anyone know how to read and edit the nginx conf on an Elastic Beanstalk application?










      share|improve this question














      In my Elastic Beanstalk instance, I am able to select Nginx to be the proxy in front of my instance.



      However, it gives no indication of where the config file (i.e. /nginx/conf.d/proxy.conf) might be, nor how to make changes to it.



      I found some documentation that mentions the conf file, but offers no information on how to see it live or make changes to it.



      Does anyone know how to read and edit the nginx conf on an Elastic Beanstalk application?







      amazon-web-services nginx configuration amazon-elastic-beanstalk






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 18 at 18:40









      CodyBugsteinCodyBugstein

      6,12731108221




      6,12731108221
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Generally you don't want to change the files on an Elastic Beanstalk instance. The advantage of that environment is that you can spin up new instances as needed and you don't need to touch them.



          You can customize quite a bit about Elastic Beanstalk machines using the ebextensions method. Basically this is a script and file structure that gives you the ability to change your environment. Be warned though that your best way of debugging this is to enable SSH into the machine and watch what the startup scripts are doing. I feel that Amazon hasn't documented this process very well and watching what it does is still the easiest way.



          I use the Java Elastic Beanstalk and have to change the port that is proxied from 5000 to 8080. I have a file that, in my environment, replaces the existing proxy file. In .ebextensions/nginx/conf.d/elasticbeanstalk in my Elastic Beanstalk distribution file I include the following as 00_application.conf:



          #
          # default is 404 - no need to allow anything else
          #
          location / {
          return 404;
          }

          #
          # this is our default url path prefix
          #
          location /integration {
          proxy_pass http://127.0.0.1:8080;
          proxy_http_version 1.1;

          proxy_set_header Connection $connection_upgrade;
          proxy_set_header Upgrade $http_upgrade;
          proxy_set_header Host $host;
          proxy_set_header X-Real-IP $remote_addr;
          proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
          }


          This is for a REST service that only exposed /integration. The key is that I had to get the initial file from logging into the machine to see how my environment was configured. Depending on the Elastic Beanstalk environment type you pick your setup may be different. In the Java world, for example, there is the Tomcat type and the Java application type and the configuration of the two is very different.






          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',
            autoActivateHeartbeat: false,
            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%2f54259742%2fwhere-does-elastic-beanstalk-store-the-nginx-configuration-file-and-how-does-on%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









            0














            Generally you don't want to change the files on an Elastic Beanstalk instance. The advantage of that environment is that you can spin up new instances as needed and you don't need to touch them.



            You can customize quite a bit about Elastic Beanstalk machines using the ebextensions method. Basically this is a script and file structure that gives you the ability to change your environment. Be warned though that your best way of debugging this is to enable SSH into the machine and watch what the startup scripts are doing. I feel that Amazon hasn't documented this process very well and watching what it does is still the easiest way.



            I use the Java Elastic Beanstalk and have to change the port that is proxied from 5000 to 8080. I have a file that, in my environment, replaces the existing proxy file. In .ebextensions/nginx/conf.d/elasticbeanstalk in my Elastic Beanstalk distribution file I include the following as 00_application.conf:



            #
            # default is 404 - no need to allow anything else
            #
            location / {
            return 404;
            }

            #
            # this is our default url path prefix
            #
            location /integration {
            proxy_pass http://127.0.0.1:8080;
            proxy_http_version 1.1;

            proxy_set_header Connection $connection_upgrade;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            }


            This is for a REST service that only exposed /integration. The key is that I had to get the initial file from logging into the machine to see how my environment was configured. Depending on the Elastic Beanstalk environment type you pick your setup may be different. In the Java world, for example, there is the Tomcat type and the Java application type and the configuration of the two is very different.






            share|improve this answer




























              0














              Generally you don't want to change the files on an Elastic Beanstalk instance. The advantage of that environment is that you can spin up new instances as needed and you don't need to touch them.



              You can customize quite a bit about Elastic Beanstalk machines using the ebextensions method. Basically this is a script and file structure that gives you the ability to change your environment. Be warned though that your best way of debugging this is to enable SSH into the machine and watch what the startup scripts are doing. I feel that Amazon hasn't documented this process very well and watching what it does is still the easiest way.



              I use the Java Elastic Beanstalk and have to change the port that is proxied from 5000 to 8080. I have a file that, in my environment, replaces the existing proxy file. In .ebextensions/nginx/conf.d/elasticbeanstalk in my Elastic Beanstalk distribution file I include the following as 00_application.conf:



              #
              # default is 404 - no need to allow anything else
              #
              location / {
              return 404;
              }

              #
              # this is our default url path prefix
              #
              location /integration {
              proxy_pass http://127.0.0.1:8080;
              proxy_http_version 1.1;

              proxy_set_header Connection $connection_upgrade;
              proxy_set_header Upgrade $http_upgrade;
              proxy_set_header Host $host;
              proxy_set_header X-Real-IP $remote_addr;
              proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
              }


              This is for a REST service that only exposed /integration. The key is that I had to get the initial file from logging into the machine to see how my environment was configured. Depending on the Elastic Beanstalk environment type you pick your setup may be different. In the Java world, for example, there is the Tomcat type and the Java application type and the configuration of the two is very different.






              share|improve this answer


























                0












                0








                0







                Generally you don't want to change the files on an Elastic Beanstalk instance. The advantage of that environment is that you can spin up new instances as needed and you don't need to touch them.



                You can customize quite a bit about Elastic Beanstalk machines using the ebextensions method. Basically this is a script and file structure that gives you the ability to change your environment. Be warned though that your best way of debugging this is to enable SSH into the machine and watch what the startup scripts are doing. I feel that Amazon hasn't documented this process very well and watching what it does is still the easiest way.



                I use the Java Elastic Beanstalk and have to change the port that is proxied from 5000 to 8080. I have a file that, in my environment, replaces the existing proxy file. In .ebextensions/nginx/conf.d/elasticbeanstalk in my Elastic Beanstalk distribution file I include the following as 00_application.conf:



                #
                # default is 404 - no need to allow anything else
                #
                location / {
                return 404;
                }

                #
                # this is our default url path prefix
                #
                location /integration {
                proxy_pass http://127.0.0.1:8080;
                proxy_http_version 1.1;

                proxy_set_header Connection $connection_upgrade;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                }


                This is for a REST service that only exposed /integration. The key is that I had to get the initial file from logging into the machine to see how my environment was configured. Depending on the Elastic Beanstalk environment type you pick your setup may be different. In the Java world, for example, there is the Tomcat type and the Java application type and the configuration of the two is very different.






                share|improve this answer













                Generally you don't want to change the files on an Elastic Beanstalk instance. The advantage of that environment is that you can spin up new instances as needed and you don't need to touch them.



                You can customize quite a bit about Elastic Beanstalk machines using the ebextensions method. Basically this is a script and file structure that gives you the ability to change your environment. Be warned though that your best way of debugging this is to enable SSH into the machine and watch what the startup scripts are doing. I feel that Amazon hasn't documented this process very well and watching what it does is still the easiest way.



                I use the Java Elastic Beanstalk and have to change the port that is proxied from 5000 to 8080. I have a file that, in my environment, replaces the existing proxy file. In .ebextensions/nginx/conf.d/elasticbeanstalk in my Elastic Beanstalk distribution file I include the following as 00_application.conf:



                #
                # default is 404 - no need to allow anything else
                #
                location / {
                return 404;
                }

                #
                # this is our default url path prefix
                #
                location /integration {
                proxy_pass http://127.0.0.1:8080;
                proxy_http_version 1.1;

                proxy_set_header Connection $connection_upgrade;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                }


                This is for a REST service that only exposed /integration. The key is that I had to get the initial file from logging into the machine to see how my environment was configured. Depending on the Elastic Beanstalk environment type you pick your setup may be different. In the Java world, for example, there is the Tomcat type and the Java application type and the configuration of the two is very different.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 18 at 22:47









                stdunbarstdunbar

                5,70561526




                5,70561526






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54259742%2fwhere-does-elastic-beanstalk-store-the-nginx-configuration-file-and-how-does-on%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

                    Liquibase includeAll doesn't find base path

                    How to use setInterval in EJS file?

                    Petrus Granier-Deferre