If you run Node on Lambda, you’re using Scott’s Node

Found a curious thing today, while messing with Lambda. I was looking at some data that (among other things) logs the config for the node process (process.config), and saw something interesting.

hi-scott

Hi, Scott!

If you want to see this yourself, create a simple lambda function that logs the process config:

'use strict';

exports.handler = (event, context, callback) => {
    console.log(process.config)
};

If you’re curious what this config contains:

The process.config property returns an Object containing the JavaScript representation of the configure options used to compile the current Node.js executable. This is the same as the config.gypi file that was produced when running the ./configure script. (source)

So that means that this Node.js executable was probably compiled by this “scottwis.” With the power of some very basic Googling, you can find the engineer who compiled it.

And he also compiled the Python, although I’m not totally sure what that means in this context:

hi-scott-python

Is this useful? Probably not. Was it interesting? YUP

Be Sociable, Share!

Tags: , , ,

No comments yet.

Leave a Reply