I can't connect to my Aurora Serverless V2 cluster
I've attempted to connect multiple ways through multiple tools. According to the AWS Aurora documentation, I should be able to connect to it using a username and password for the instance upon which it is based.
I can connect to the original Postgres database through standard SQL tools like DBVisualizer, VSCode's 'SQL Tools' plugin and Workbench. (orig. db instance circled in green, cluster in red).
When I try to connect to the cluster using the end point for the writer, my connections time out. If I use an AWS tool like 'Query Editor', I get an error that looks like an authentication failure "....Please check your user name, password, and database name..." AWS can certainly "see" my database. I do have Data API enabled for it.
Both are in the same VPC and are using the same subnets and security groups. The inbound rules allow for all traffic. Is there something I'm missing? I've spent 2 days on this, read and tried everything I can think of.
Any help greatly appreciated.
- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hello.
When I try to connect to the cluster using the end point for the writer, my connections time out. If I use an AWS tool like 'Query Editor', I get an error that looks like an authentication failure "....Please check your user name, password, and database name..." AWS can certainly "see" my database. I do have Data API enabled for it.
Are you trying to connect from a local environment using something like Workbench?
In that case, I think you need to enable public access.
https://repost.aws/knowledge-center/aurora-mysql-connect-outside-vpc
By the way, public access is not recommended for security reasons, so I recommend using port forwarding using Session Manager, which is introduced in the document below.
https://aws.amazon.com/jp/blogs/mt/use-port-forwarding-in-aws-systems-manager-session-manager-to-connect-to-remote-hosts/
Also, why not try changing the RDS user password once?
If you can connect after changing the password, the password specified in the query editor may be incorrect.
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Modifying.html#Aurora.Modifying.Password
Contenus pertinents
- demandé il y a un an
- demandé il y a 11 jours
AWS OFFICIELA mis à jour il y a 2 ans- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
Riku, thanks for your thoughtful answers.
Changing the Aurora master password to match the password of the primary db instance did allow me to connect through Query Editor.
However, I still can't connect from outside my local environment, even though Aurora's primary instance is in the same network environment as my provisioned instances. The VPC and its subnets are all public and the ACLs and SGs allow all traffic both ways. I can connect to the provisioned instance from my local environment.
My larger goal is to connect to my Aurora cluster through an AppSync GraphQl API. I have had no luck with that either.