AWS Certificate Authority
See original GitHub issueAWS is changing the certificate to connect to RDS. The deadline is March 5. Right now using the current certificate:
rds-ca-2015
My dialectOptions connection section looks like this:
"dialectOptions": {
"ssl": "Amazon RDS"
},
This of course no longer works after I update the certificate on RDS to the latest certificate:
rds-ca-2019
I have installed the certificates to the local store on the ubuntu machine as required by AWS.
Do I have to reference a .pem file directly? Or should this still work?
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Cloud CA Service – AWS Private Certificate Authority
AWS Private Certificate Authority (AWS Private CA) is a highly available, versatile CA that helps organizations secure their applications and devices using ...
Read more >What is AWS Private CA? - AWS Documentation - Amazon.com
With AWS Private CA, you can create your own CA hierarchy and issue certificates with it for authenticating internal users, computers, applications, services, ......
Read more >Creating a private CA - AWS Documentation
Learn about ways to create a private CA. ... For the latest AWS Private CA pricing information, see AWS Private Certificate Authority Pricing...
Read more >AWS Private CA Pricing
With AWS Private Certificate Authority (AWS Private CA), you pay a monthly fee for the operation of each private CA, the private certificates...
Read more >Certificate Authority | AWS Security Blog
AWS Certificate Manager (ACM) Private Certificate Authority (CA) now offers the option for managing online root CAs and a full online PKI hierarchy....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
In case it’s related - there is an open issue at https://github.com/mysqljs/mysql/issues/2288 suggesting that module’s ssl_profiles.js file may need to be updated with the RDS 2019 and 2015 combined certificates. It’s that profile that loads when “Amazon RDS” string is referenced, so I guess (but haven’t been able to prove) that if it doesn’t include the new certificates it won’t validate the SSL connection.
Updating dialect library should be enough, SSL setup is handled by dialect libraries directly.