1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Apparently what you are trying should work.
I will start with basic. From Instance in VPC 2 , do dig/nslookup to URL of Private Link to see if DNS resolution is working fine? If yes, then use CMD or terminal and try to telnet on privatelink URL with SQL port from instance in VPC 2 , for example privatelinkdnsname.regionnameet.com.aws PORTNUMBER to see if it connects or not
This will give some idea of the issue. Is SQL ports open INBOUND SG/ACL attached to ENI of Privatelink in VPC 2?
VPC Flowlogs in VPC 2 can be helpful to investigate further as well.
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 4 mesi fa
Thank you, Muhammad for your valuable advice.
Traffic was blocked on port 58090 because of missing Firewall inbound and outbound rules for port 58090 in VPC-2 instance. I was able to pinpoint this issue using telnet and powershell tnc.
Sorry, I must admit that I misprinted VPC-1 SLQ Server port number in my question. It is 58090, not 1433 as I originally wrote.
Cheers.