Arvind Kushwah Web Developer and Software Consultant

server {         listen 80 default_server;         listen [::]:80 default_server;         # SSL configuration         #         # listen 443 ssl default_server;         # listen [::]:443 ssl default_server;         #         # Self signed certs generated by the ssl-cert package         # Don't use them in a production server!         #         #root /usr/share/nginx/html;         server_name 108.174.155.117;         passenger_enabled on;         rails_env    production;         root         /home/app/test-runner/public;          error_page   500 502 503 504  /50x.html;         #location = /50x.html {         #    root   html;         #}         # Add index.php to the list if you are using PHP         index index.html index.htm index.nginx-debian.html;         #server_name _;          #server_name _;         #location / {                 # First attempt to serve request as file, then                 # as directory, then fall back to displaying a 404.         #       try_files $uri

The way I ended up doing this was: 1) Download AWSDevTools from http://aws.amazon.com/developertools/AWS-Elastic-Beanstalk/6752709412171743 2) Move to your git repo on the CLI 3) Run /Downloads/elasticbeanstalk-cli/AWSDevTools/ [Linux or Windows] /AWSDevTools-RepositorySetup.sh EDIT: 3a) git aws.config 4) Enter AWS Access Key, AWS Secret Key, AWS Region, and enter the existing name of your AWS Application and AWS Environment. 5) Now you can git add, git commit as usual, and use git aws.push to push to your EB environment 7) You can follow the steps above to add other environments. For example if you had production and staging environments, and then use git aws.push --environment to use the same repo to push to both environments. If you come across the error The specified module 'AWSDevTools' was not loaded on Windows, this is most likely because the AWSDevTools module is not at C:\Users\ USER \Documents\WindowsPowerShell\AWSDevTools\AWSDev