danyal2050

server {
        listen   80;
        server_name <domain>
        server_name_in_redirect off;

        access_log logs/<domain>.access.log;
        error_log logs/<domain>.error.log;

        gzip_static on;

danyal2050

First, we need to figure out what the actual error is.  This is obviously frustrating given that the error message is intentionally truncating it.

1) SSH in to your node (various guides available for this if you're not already familiar with this).
2) Run this command (basically an Elastic Beanstalk wrapper command for npm install I found in a blog post [1]):
   $ sudo /opt/elasticbeanstalk/containerfiles/ebnode.py --action npm-install 2
3) Find the actual error message in the output from the npm install.

Once you know the error, it should hopefully be fairly obvious how to fix it.  I've run into two different errors over the last couple days on Elastic Beanstalk:

The first was a dependency that was using the new "^X.Y.Z" version syntax, which is only supported in Node >= v0.10.26 (whereas Elastic Beanstalk only supports up to v0.10.21 as of today).  The solution here was easy: hardcode a dependency version *prior* to when that dependency adopted to the new syntax.

danyal2050

this was tested using windows10 pro

when cloning a git this error was produced
fatal: unable to access 'https://git-codecommit.us-east-1.amazonaws.com/v1/repos/RepositoryName': The requested URL returned error: 403

to fix add the following git configuration
git config --global credential.helper "!aws codecommit credential-helper $@"
git config --global credential.UseHttpPath true

check if git has system credential.helper by typing