I put "localhost" as hostname in DBeaver instead of the RDS cluster DNS name I put initially and it works for me
You usually get this error when:
- You already have an interface VPC endpoint for the same service in your VPC.
- Your VPC is already associated with a private hosted zone that covers the intended service name. Here is more details: https://aws.amazon.com/premiumsupport/knowledge-center/vpc-interface-endpoint-domain-conflict/ To troubleshoot : Have you enabled DNS hostname and DNS resolution on your VPC? Also Do you have Inbound HTTPS traffic allowed on your security group rules? Please also make sure you put a correct custom policy for your endpoint ( the policy listed on the documentation is just an example but you'd need a broader policy that allow ec2messages, ssm, ssmmessages). Please update me with the following and I can help more.
Accessing Running Container on AWS to my local machineasked 4 months ago
connect to mysqlRDS instance from local workstationAccepted Answerasked 3 months ago
how to connect to private RDS from localhostasked a year ago
From docker container need to connect RDS - Using Session Managerasked 3 months ago
Can not connect EC2 Instance via My Ip RDP but Anywhere-IPv4 addressasked a year ago
migrate database from my local to AWSAccepted Answerasked 3 years ago
Cannot connect remotely to serverless Aurora MySQLasked 4 years ago
SageMaker notebook instance in VPC failed to connect to local databaseAccepted Answerasked 4 years ago
I cannot connect to AWS RabbitMQ from my local machineasked 10 months ago
Trying to copy a postgres instance from a local postgres server to an RDS instance via DMSasked 3 months ago