I have a server available at AWS and the client is asking to connect to their MariaDB database remotely which is available on their server that is accessible via VPN.
So, how is it possible to connect to a remote database from the web application hosted on my AWS server?
Thanks in advance.
I have an issue with postgres database in cloud foundry. Created service using cloud foundry market place. Application worked good until yesterday, and today not able to connect to database or ping it. I am not sure where to check service logs or how to restart postgres service in cloud foundry. Any one have some ideas please respond to this thread. Thanks. I can see below error in application logs.
Caused by: org.postgresql.util.PSQLException: The connection attempt failed.
Tried to ping database host IP address, but shows down.
So basically - I've enabled RDS Proxy (still in Preview) for my Aurora MySQL DB and the Proxy is created and available for use.
The Proxy uses a DB User/Pwd combination sourced from Secrets
Manager to connect to the MySQL DB.
The Proxy can be accessed without Authentication (IAM role based
authentication is supported but I've not configured it yet).
When I connect to the proxy endpoint it fails with "Failed to Connect to MySQL" on my MySQL client and on the Cloudwatch logs for the Proxy I see the following 2 lines for each connection attempt..
[INFO] [clientConnection=3488645722] New client connection from 10.XX.XX.XX:63344
[INFO] [clientConnection=3488645722] Client connection closed. Reason: Internal error.
Cloudwatch Metrics just reports increase in ClientConnectionsReceived metric for each connection attempt and no change to the ClientConnectionsClosed metric.
So basically I am clueless as to why the client connection is getting closed.. Any hints/clues would be much appreciated..
Try one of those:
Ensure your user is created in the RDS Database. Test that you able to connect directly with that user.
Ensure RDS proxy security group is whitelisted in the RDS security group.
On the secrets manager ensure you've selected the right RDS database.
I have Spring Boot java (Gradle) application deployed on Pivotal Cloud Foundry and I have Database connection with local Oracle SQL developer which is 18.2.0.183 version. After deploying the service to Cloud Foundry and creating user provided service in PCF to connect to my local DB, Cloud Foundry doesn't let me connect to my local Oracle Sql Developer DB. It throws this error:
org.springframework.jdbc.CannotGetJdbcConnectionException: Failed to obtain JDBC Connection; nested exception is java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection
So How can I properly send a Oracle config in user provided service so that it connects.
I am following the Django sample for GAE and have problem to connect to Cloud SQL instance by Proxy from Google Cloud Shell. Possibly related to permission setting since I see the request not authorized,
Other context,
"gcloud beta sql connect auth-instance --user=root" has no problem to connect.
I have a service account for SQL Proxy Client.
I possibly miss something. Could someone please shed some light? Thanks in advance.
Thanks in advance.
Proxy log:
./cloud_sql_proxy -instances=auth-158903:asia-east1:auth-instance=tcp:3306
2017/02/17 14:00:59 Listening on 127.0.0.1:3306 for auth-158903:asia-east1:auth-instance
2017/02/17 14:00:59 Ready for new connections
2017/02/17 14:01:07 New connection for "auth-158903:asia-east1:auth-instance"
2017/02/17 14:03:16 couldn't connect to "auth-158903:asia-east1:auth-instance": dial tcp 107.167.191.26:3307: getsockopt: connection timed out
Client Log:
mysql -u root -p --host 127.0.0.1
Enter password:
ERROR 2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet', system error: 0
I also try with credential file but still no luck,
./cloud_sql_proxy -instances=auth-158903:asia-east1:auth-instance=tcp:3306 -credential_file=Auth-2eede8ae0d0b.jason
2017/02/17 14:21:36 using credential file for authentication; email=sql-proxy-client#auth-158903.iam.gserviceaccount.com
2017/02/17 14:21:36 Listening on 127.0.0.1:3306 for auth-158903:asia-east1:auth-instance
2017/02/17 14:21:36 Ready for new connections
2017/02/17 14:21:46 New connection for "auth-158903:asia-east1:auth-instance"
2017/02/17 14:21:48 couldn't connect to "auth-158903:asia-east1:auth-instance": ensure that the account has access to "auth-158903:asia-east1:auth-instance" (and make sure there's no typo in that name). Error during get instance auth-158903:asia-east1:auth-instance: googleapi: **Error 403: The client is not authorized to make this request., notAuthorized**
I can reproduce this issue exactly if I only give my service account "Cloud SQL Client" IAM role. When I give my service account the "Cloud SQL Viewer" role as well, it can then connect. I suggest you try this and see if it helps.
It looks like a network connectivity issue.
Read this carefully if you use a private IP :
https://cloud.google.com/sql/docs/mysql/private-ip
Note that the Cloud SQL instance is in a Google managed network and the proxy is meant to be used to simplify connections to the DB within the VPC network.
In short: running cloud-sql-proxy from a local machine will not work, because it's not in the VPC network. It should work from a Compute Engine VM that is connected to the same VPC as the DB.
What I usually do as a workaround is use gcloud ssh from a local machine and port forward over a small VM in compute engine, like:
gcloud beta compute ssh --zone "europe-north1-b" "instance-1" --project "my-project" -- -L 3306:cloud_sql_server_ip:3306
Then you can connect to localhost:3306 (make sure nothing else is running or change first port number to one that is free locally)
The Cloud SQL proxy uses port 3307 instead of the more usual MySQL port 3306. This is because it uses TLS in a different way and has different IP ACLs. As a consequence, firewalls that allow MySQL traffic won't allow Cloud SQL proxy by default.
Take a look and see if you have a firewall on your network that blocks port 3307. To use Cloud SQL proxy, authorize this port for outbound connections.