- Newest
- Most votes
- Most comments
Hello.
As you recognize, it is a dynamic parameter, so I don't think a restart is necessary.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/mysql-ssl-connections.html
Just to be sure, is the parameter group set in the RDS correct?
Are you editing different parameter groups?
Hi,
According to the AWS documentation and MySQL documentation, you must set the require_secure_transport parameter value to ON (Not “1”) to require SSL/TLS for connections to your DB instance. Could you check it?
Since it's a boolean data type, AWS console shows a list with two values 1 and 0. There is no way to enter value manually. And I assume, being boolean, 1 should mean ON or true.
I have the same issue, and I have also rebooted the RDS instance.
SSL is not enforced when require_secure_transport is set to 1 ( which is ON).
I am facing the same issue. Even for PostgreSQL as well. Have anyone found the solution?
I am also facing the same issue. Even though the require_secure_transport = ON, I am able to connect to mysql without ssl-mode from my machine from command line. However, from the same machine, if I use DBeaver or a custom javascript program to connect to the same RDS without SSL, then i get the below error
Error connecting to the database: Error: Connections using insecure transport are prohibited while --require_secure_transport=ON
I'm facing the same issue with Aurora MySQL 3.05.2 cluster. It does not require ssl when require_secure_transport = ON
It was working correctly in Aurora MySQL 2.11.5.
Relevant content
- asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
Yes, I have set the right parameter group in RDS. I have already used the same parameter group to change the timezone and restarted and it worked fine.