Amazon Elastic Beanstalk node and npm non-standard install locations

Question

Amazon Beanstalk installs node and npm into really obscure places - and I'm not sure they won't change if EB decides to use a newer version of node, which would cause my application to break.

These are the locations for node and npm:

/opt/elasticbeanstalk/node-install/node-v0.8.24-linux-x64/bin/node
/opt/elasticbeanstalk/node-install/node-v0.8.24-linux-x64/bin/npm

I'm worried about the 0.8.24 part changing and I'd rather not grep for things in cron or monit scripts when trying to find something that is normally just /usr/bin/XXX.

how do I get a consistent filepath for these executables? and why does EB do this?

for reference, I tried setting the NodeVersion option in an .ebextensions/app.config, it had no effect on the install location.

I'm assuming those locations aren't in PATH?

Timothy Strimple
– Timothy Strimple

2013-08-13 16:33:53 +00:00
Commented Aug 13, 2013 at 16:33 — Timothy Strimple
– Timothy Strimple, Commented Aug 13, 2013 at 16:33
yes, that is correct, they are not

dubeegee
– dubeegee

2013-08-14 08:21:13 +00:00
Commented Aug 14, 2013 at 8:21 — dubeegee
– dubeegee, Commented Aug 14, 2013 at 8:21

Peter Johnson · Accepted Answer · 2013-09-25 17:09:50Z

63

You can add the most recent node and npm binaries to $PATH with a command like this:

PATH=$PATH:`ls -td /opt/elasticbeanstalk/node-install/node-* | head -1`/bin

I couldn't figure out how to prevent beanstalk commands from resetting the $PATH back again.

If you are so inclined you can probably create a symlink with a command similar to the above and use that as your reference point in cron scripts etc.

Agreed, it is very very annoying.

answered Sep 25, 2013 at 17:09

Peter Johnson

2,70322 silver badges14 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

spuder Over a year ago

Or just use the $NODE_HOME environment variable as suggested in dorianm's answer

Adiii Over a year ago

sudo ln -sf ls -td /opt/elasticbeanstalk/node-install/node-* | head -1/bin/node /bin/node

asaf am · Accepted Answer · 2015-08-17 12:54:04Z

31

Following Peter Johnson & Greg Tatum replies I created a symlink to the latest node executable:

container_commands:
  01_node_binary:
    command: "ln -sf `ls -td /opt/elasticbeanstalk/node-install/node-* | head -1`/bin/node /bin/node"

I find the latest version of the node install binary
Out of it I create a symlink in the /bin directory (which is part of the $PATH)

edited Aug 17, 2015 at 12:54

answered Jul 26, 2015 at 13:13

asaf am

1,39515 silver badges30 bronze badges

3 Comments

h-kippo Over a year ago

This script will fail next time when the app is deployed

asaf am Over a year ago

Thanks @h-kippo I updated it so it forcefully creates the symlink if it already exists (if this was the problem)

Eric Over a year ago

To clarify, this should go in a file like .ebextensions/nodepath.config, right?

dorianm · Accepted Answer · 2016-10-06 20:32:39Z

11

We had a similar issue with "node not found", trying to run node in container commands. After running ps aux on the EC2 instance we saw that EB has access to the $NODE_HOME env var:

su -s /bin/sh -c PATH=$PATH:$NODE_HOME/bin $EB_NODE_COMMAND 2>&1 nodejs

This can be used in .ebextensions, e.g.:

container_commands:
  your_node_script:
    command: 'env PATH="$PATH:$NODE_HOME/bin" ./bin/your_node_script'

(thanks to Alan Grow)

answered Oct 6, 2016 at 20:32

dorianm

2532 silver badges7 bronze badges

3 Comments

pscl Over a year ago

This seems more robust than the accepted answer in that it uses the node version setting rather than just picking the most recently installed version (or whatever arbitrary sort order)

mpyw Over a year ago

command: 'env PATH="$PATH:$NODE_HOME/bin" sh -c 'npm run build' works fine. thanks

Pherrymason Over a year ago

This does not look like it works for me, as NODE_HOME seems to not be set :(

Greg Tatum · Accepted Answer · 2015-05-07 17:01:28Z

3

I created the file /.ebextensions/node.config in my project folder to declare my node version and add symlinks to the /bin folder. More information about the .ebextensions folder can be found here: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customize-containers-ec2.html

option_settings:
  - option_name: NodeVersion
    value: 0.12.2
files:
  "/bin/node" :
    mode: "755755"
    content: "/opt/elasticbeanstalk/node-install/node-v0.12.2-linux-x64/bin/node"
  "/bin/npm" :
    mode: "755755"
    content: "/opt/elasticbeanstalk/node-install/node-v0.12.2-linux-x64/bin/npm"

answered May 7, 2015 at 17:01

Greg Tatum

1,23211 silver badges12 bronze badges

3 Comments

ariestav Over a year ago

This does allow me to run npm and node from any path when I've ssh'ed into my eb instance, but for some reason the command will never "take" an argument. For example, npm install results in just listing all the possible options for npm.

CherryDT Over a year ago

That's because these are evaluated as shell scripts, not symlinks. Try mode: "100755" instead.

GoGoris Over a year ago

According to the latest docs you have to start with "120xxx" to create a symlink: docs.aws.amazon.com/elasticbeanstalk/latest/dg/…

Fupslot · Accepted Answer · 2018-02-06 13:30:45Z

1

Amazon Elastic Beanstalk

Grand the access to node command

sudo su
vipw
nodejs:x:496:494::/tmp:/bin/bash (":wq" to save changes)
sudo su nodejs
PATH=$PATH:ls -td /opt/elasticbeanstalk/node-install/node-* | head -1/bin
node -v (enjoy :)

answered Feb 6, 2018 at 13:30

Fupslot

1251 silver badge5 bronze badges

1 Comment

spuder Over a year ago

Stack overflow isn't rendering the back ticks, which are required, (see Peter Johnsons answer)

Collectives™ on Stack Overflow

Amazon Elastic Beanstalk node and npm non-standard install locations

5 Answers 5

2 Comments

3 Comments

3 Comments

3 Comments

Amazon Elastic Beanstalk

Grand the access to node command

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

2 Comments

3 Comments

3 Comments

3 Comments

Amazon Elastic Beanstalk

Grand the access to node command

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related