SQL Server database access issue from AWS Lambda

Question

I'm getting this error while accessing SQL Server database from aws-lambda. Everything works fine from local machine.Only having access issue when executing the code from lambda.

ConnectionError: Failed to connect to 10.2.3.44\SQLSRVR code: ETIMEOUT

This is my code snippet, any help would be appreciated!

const { Sequelize } = require('sequelize');
const sequelize = new Sequelize('DBname', null, null, {
  dialect: 'mssql',
  host: '10.2.3.44',   //MSSQL Server IP sample
  dialectOptions: {
    authentication: {
      type: 'ntlm',
      options: {
        domain: 'addidas',
        userName: "uname",
        password: "pwd"
      }
    },
    options: {
      instanceName: 'SQLSRVR'
    }
  }
})
async function connect() {
    try {
      await sequelize.authenticate();
      console.log('Connection has been established successfully.');
    } catch (error) {
      console.error('Unable to connect to the database:', error);
    }
  }
connect();

Does your Lambda function have internet access if that database is outside of AWS? — Ermiya Eskandary
– Ermiya Eskandary, Commented Nov 6, 2021 at 7:26
Where is you ql server located? Do you have any firewall rules that allow your local machine but not other clients? For instance on azure you have to explicitly allow any IP address that is not within azure to be able to access the sql server. — derpirscher
– derpirscher, Commented Nov 6, 2021 at 8:24
Please Edit your question to provide more details. For example, where is the SQL Server hosted? Is it an Amazon RDS database? — John Rotenstein
– John Rotenstein, Commented Nov 6, 2021 at 9:05
You probably need this: docs.aws.amazon.com/lambda/latest/dg/configuration-vpc.html — kgiannakakis
– kgiannakakis, Commented Nov 6, 2021 at 9:12
10.2.3.44 is private address. Nothing on the internet knows how to get to it unless you do some kind of port forwarding from a public internet address. — Nick.Mc
– Nick.Mc, Commented Nov 6, 2021 at 9:44

roby.elan · Accepted Answer · 2021-11-10 13:52:20Z

1

It was because of the network restrictions only, as assumed. So had to assign lambdas in the same network which SQL server is hosted. Thanks for all the suggestions.

answered Nov 10, 2021 at 13:52

roby.elan

1441 silver badge11 bronze badges

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

Collectives™ on Stack Overflow

SQL Server database access issue from AWS Lambda

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related