Help Center>
GaussDB>
FAQs>
Database Connections>
What Should I Do If the ECS and GaussDB Instance Are Deployed in Different VPCs and They Cannot Communicate with Each Other?
Updated on 2023-10-12 GMT+08:00
What Should I Do If the ECS and GaussDB Instance Are Deployed in Different VPCs and They Cannot Communicate with Each Other?
- Change the VPC hosting the ECS to the same as that hosting the GaussDB instance.
- Create a VPC peering connection to set up a network connection between the two VPCs.
Parent topic: Database Connections
Database Connections FAQs
- Can I Connect to GaussDB over SSL?
- What Should I Do If I Can't Connect to My GaussDB Instance?
- Can an External Server Access GaussDB Instances?
- How Can I Create and Connect to an ECS?
- What Should I Do If an ECS Cannot Connect to a GaussDB Instance Through a Private Network?
- What Should I Do If a Database Client Problem Causes a Connection Failure?
- What Should I Do If a GaussDB Database Problem Causes a Connection Failure?
- How Do My Applications Access a GaussDB Instance in a VPC?
- Do Applications Need to Support Reconnecting to the GaussDB Instance Automatically?
- Why Can't I Ping My EIP After It Is Bound to an Instance?
- Can I Access a GaussDB Instance Over an Intranet Connection Across Regions?
- Will My Access Be Restricted by Bandwidth When I Connect to My GaussDB Instance from an ECS over a Private Network?
- Why Did the New Password Not Take Effect After I Reset the Administrator Password?
- What Should I Do If the ECS and GaussDB Instance Are Deployed in Different VPCs and They Cannot Communicate with Each Other?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
