Connect to EC2 server through AWS lambda - node.js

Question

I have a shell script on my EC2 server and I want to trigger the same from AWS lambda function. Can anyone suggest how I can access the file in my lambda function. There is no connectivity issue between lambda and EC2.
I generated the private key with Putty gen and kept it in s3 bucket and using same key to connect(With this private key able to connect through putty).I have piece of code like this.
var driver, ssh;
driver = require('node-ssh');
ssh = new driver();
exports.handle = function(error, ctx, cb) {
ssh = new driver({
host: 'EC2 public ip',
username: 'uname',
privateKey : 'url of s3/privatekey.ppk'
});
ssh.connect().then(function() {
console.log('connected')
},function(error) {
console.log(error);
});
}
First I am trying to see if I can connect to my EC2 server and then I can run the shell script through ssh client. But connection is not happening.Getting below error.
{
"errorMessage": "config.host must be a valid string",
"errorType": "Error",
"stackTrace": [
"Object.<anonymous> (/var/task/node_modules/node-ssh/lib/helpers.js:15:13)",
"next (native)",
"step (/var/task/node_modules/node-ssh/lib/helpers.js:69:191)",
"/var/task/node_modules/node-ssh/lib/helpers.js:69:437",
"Object.<anonymous> (/var/task/node_modules/node-ssh/lib/helpers.js:69:99)",
"Object.normalizeConfig (/var/task/node_modules/node- ssh/lib/helpers.js:42:17)",
"/var/task/node_modules/node-ssh/lib/index.js:53:25",
"SSH.connect (/var/task/node_modules/node-ssh/lib/index.js:52:14)",
"exports.handle (/var/task/index.js:13:7)"
]
}

Answer 1

You would need something running on your EC2 instance to "receive" the request.
Some options:
Run a web server and call it from the Lambda function, or
Use the EC2 Run Command which uses an agent on the EC2 instance and can be called via the AWS API, or
Have the Lambda function push a message into an Amazon SQS queue and have the instance continually poll the queue
It would be much simpler if you could simply run the code in your Lambda function instead.

Answer 2

Posting answer to this question. Hope it will help.
package com.wb.mars.ingest;
import java.io.File;
import java.io.InputStream;
import java.io.OutputStream;
import java.io.PrintWriter;
import com.amazonaws.services.lambda.runtime.Context;
import com.amazonaws.services.lambda.runtime.RequestHandler;
import com.jcraft.jsch.ChannelExec;
import com.jcraft.jsch.JSch;
import com.jcraft.jsch.Session;
import com.wb.mars.ingest.CustomEventInput;
import com.wb.mars.ingest.CustomEventOutput;
public class EC2ConnectLambda implements RequestHandler<CustomEventInput,CustomEventOutput> {
public CustomEventOutput handleRequest(CustomEventInput input, Context context) {
context.getLogger().log("Input: " + input);
System.out.println("test");
try {
String command1 = "cd /home/ec2-user/mydir; ./runjar.sh";
JSch jsch = new JSch();
String user = "ec2-user";
String host = "*.*.*.*";
int port = 22;
//File file = new File( EC2ConnectLambda.class.getResource( "/Linux_EC2.pem" ).toURI() );
File file = new File( EC2ConnectLambda.class.getResource( "/mykey.pem" ).toURI() );
String privateKeyabsolutePath = file.getAbsolutePath();
jsch.addIdentity(privateKeyabsolutePath);
System.out.println("identity added ");
Session session = jsch.getSession(user, host, port);
System.out.println("session created.");
java.util.Properties config = new java.util.Properties();
config.put("StrictHostKeyChecking", "no");
session.setConfig(config);
session.connect();
System.out.println("session connected.....");
ChannelExec channel = (ChannelExec)session.openChannel("exec");
OutputStream o = channel.getOutputStream();
PrintWriter pw = new PrintWriter(o);
InputStream in = channel.getInputStream();
((ChannelExec) channel).setCommand(command1);
channel.connect();
// 4 - Clean up
channel.disconnect();
session.disconnect();
} catch (Exception e) {
System.err.println(e);
e.printStackTrace();
}
return new CustomEventOutput("lambdaInvoked");
}
}