2 Answers
- Newest
- Most votes
- Most comments
0
I solved this by manually setting the username and password when setting up the connection for Query Editor (see below). if you choose 'Secret Manager' for credential management, you can't use an existing secret - it always generates a new one for you with a random password. You won't be able to authenticate with it.
answered 17 days ago
0
Hello.
The username and password set in the secret manager must be set to match Aurora PostgreSQL.
You can edit it by following the steps in the document below.
https://docs.aws.amazon.com/secretsmanager/latest/userguide/manage_update-secret-value.html
Relevant content
- asked 20 days ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Thank you! I wasn't retrieving the secret first. Doing so, I saw that there was an error in the password and was able to change it. The rest of the credentials looked right.
However, I still can't connect. I was thinking I may be using the wrong value for 'name of the database'. I've tried
but I always get the same error as shown above. Thoughts?
Thanks again, --Bo
Try entering "postgres" in "Enter the name of the database" on the query editor settings screen shown in the image.
I tried that. It didn't work.
I'm using a username and password that work across every other sql connection tool. The username happens to be 'postgres'. I'm using 'postgres' as the database name, and I've confirmed that is the right name of the database.
The AWS-Aurora documentation confirms this approach.
I've tried connecting through the Secret Manager and through username and password directly.
I remember seeing something about Query Editor not working with Serverless V2. Is that accurate? I'm running out of ideas.
If you can use DataAPI, you should also be able to use the query editor, so I think you can use it with Aurora Serverless V2 PostgreSQL as well. https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless-v2.upgrade.html
Hi Riku, I enabled Data API but I can't use it. So far, I haven't been able to query my cluster in any of the many ways I've tried. I've looked at my VPC and its subnets, ACL, and security groups and they all look good.