1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
Hello.
Because of the timeout error, I thought that the GCP Compute Engine IP address might not be allowed in the inbound rules of the security group on the RDS side.
What kind of rules are set for RDS security group settings?
Also, does RDS have public access enabled?
https://repost.aws/knowledge-center/rds-connectivity-instance-subnet-vpc
If you want to access privately, I think you need to connect AWS and GCP with a VPN etc.
https://cloud.google.com/network-connectivity/docs/vpn/tutorials/create-ha-vpn-connections-google-cloud-aws
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 10 mesi fa
Hello,
Thank you for the help, I'm very new at all of this.
I was messing with the inbound security rules for the RDS, and I managed to get it to work. I added an inbound rule for "All TCP", and "0.0.0.0". However, this doesn't seem to me like it's extraordinarily safe.
Though this is mostly a side project, it does have a public-facing front, so I'm going to make sure there's no potential vulnerabilities with the security rules.
-Claire
As you know, this setting is not secure. If possible, configure MySQL's 3306 and IP addresses to only allow those from GCP Compute Engine.