Error P1001 Can't reach database server at AWS RDS (MySQL)

Bug description

I am trying to migrate my models to an AWS RDS (MySQL) database, but I am encountering this error:

Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": MySQL database "dbname" at "hostname.rds.amazonaws.com:3306"

MySQL database dbname created at hostname.rds.amazonaws.com:3306

Error: P1001

Can't reach database server at `hostname.rds.amazonaws.com`:`3306`

How to reproduce

Steps to reproduce the behavior:

1. Run npm install prisma --save-dev
2. Run prisma init and write a model
3. Run prisma migrate dev --name m1 --preview-feature

Expected behavior

I expect it to create a database table with Prisma Migrate. It does create the database, but not the table.

Prisma information

// .env

DATABASE_URL=mysql://username:[e-mail]:3306/dbname

// .schema.prisma

datasource db {
  provider = "mysql"
  url = env("DATABASE_URL")
}

generator client {
  provider = "prisma-client-js"
}

model ModelName {
  id                 Int               @default(autoincrement()) @id
  createdAt          DateTime          @default(now())
}

Environment & setup

• OS: Mac OS
• Database: MySQL
• Node.js version: v14.5.0
• Prisma version:

prisma               : 2.16.1
@prisma/client       : 2.16.1
Current platform     : darwin
Query Engine         : query-engine 8b74ad57aaf2cc6c155f382a18a8e3ba95aceb03 (at node_modules/@prisma/engines/query-engine-darwin)
Migration Engine     : migration-engine-cli 8b74ad57aaf2cc6c155f382a18a8e3ba95aceb03 (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine : introspection-core 8b74ad57aaf2cc6c155f382a18a8e3ba95aceb03 (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary        : prisma-fmt 8b74ad57aaf2cc6c155f382a18a8e3ba95aceb03 (at node_modules/@prisma/engines/prisma-fmt-darwin)
Studio               : 0.346.0

[ceefour]

I found the problem, this was due to the AWS RDS server latency is high (in different region than my location). See https://www.prisma.io/docs/concepts/database-connectors/mysql#arguments

Solution: Add ?connect_timeout=30&pool_timeout=30&socket_timeout=30 (or higher seconds) to DATABASE_URL

[armandoborge]

@janpio everything is working well with the SSL, thanks for your reply!