데이터베이스 액세스 문제 해결

Teleport로 데이터베이스를 보호할 때 발생하는 일반적인 문제와 해결 방법입니다.

일반적인 문제와 해결 단계입니다. 연결 시도 실패 # 타임아웃 오류 # 데이터베이스 연결 시도가 **"dial tcp ... i/o timeout"**과 유사한 메시지와 함께 실패합니다. The Teleport Database Service requires connectivity to your database endpoints. Check that firewall rules (e.g., AWS security groups) allow connectivity between the Teleport Database Service and the database endpoint. Inbound firewall rules for the database must allow connections from the Teleport Database Service. Outbound firewall rules for the Teleport Database Service must allow connections to the database endpoint. Tip On the same host as the Teleport Database Service, try running nc to check if it can reach the database port. Database host: postgres-instance-1.sadas.us-east-1.rds.amazonaws.com Database port: 5432 $ nc -zv database-host database-port # Connection to postgres-instance-1.sadas.us-east-1.rds.amazonaws.com (172.31.24.172) 5432 port [tcp/postgresql] succeeded! Debugging connection timeout errors in AWS For deployments in AWS, it may be helpful to use AWS Reachability Analyzer to analyze the network path between the Teleport Database Service and the database. Identify the Elastic Network Interface (ENI) associated with the Teleport Database Service host. This can be found in the EC2 console . Identify the private IP address of the database. Create and analyze a network path: Set the path source to the ENI associated with the Teleport Database Service host. Set the path destination to the database IP. Check the analysis results to identify reachability issue