AWS Lambda (NodeJS) throws error when connecting RDS by Sequelize - node.js

Question

Base on aws-serverless-express repository on Github. I've made a connection to AWS RDS in order to CRUD data. I'm using Sequelize for ORM.
I've tested on local, actions work perfectly. But when it's deployed on AWS Lambda the error was thrown at Sequelize initialization (without it works normally)
Sequelize initial
const database = new Sequelize('databasename', 'root', 'password', {
host: 'XXXXXX.XXXXXX.us-east-1.rds.amazonaws.com',
port: 3306,
logging: console.log,
maxConcurrentQueries: 100,
dialect: 'mysql',
dialectOptions: {
ssl: 'Amazon RDS',
},
pool: { maxConnections: 5, maxIdleTime: 30 },
language: 'en',
});
Error logs was got from CloudWatch:
module initialization error: Error
at Object.fs.openSync (fs.js:646:18)
at Object.fs.readFileSync (fs.js:551:33)
at Object.Module._extensions..js (module.js:662:20)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/var/task/mysql2/lib/packets/ssl_request.js:3:23)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at /var/task/mysql2/lib/packets/index.js:4:16
at Array.forEach (<anonymous>)
at Object.<anonymous> (/var/task/mysql2/lib/packets/index.js:3:4)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
I fear error throws cause SSL connection problem, but I don't know how to figure out.
Below is my config on RDS MySql instance:
Network & Security
Security group: default
Inbound:
Type: All trafic
Protocol: All
Port Range: All
Source: sg-3c941877 (default)
Outbound:
Type: All trafic
Protocol: All
Port Range: All
Destination: 0.0.0.0/0
Public accessibility: Yes
Database options
IAM DB authentication: Disabled
In AWS Lambda I also added AWSLambdaVPCAccessExecutionRole Policy
Thanks in advance.