Help Center/ TaurusDB/ FAQs/ Database Connections/ What Should I Do If an ECS and a TaurusDB Instance Deployed in Different VPCs Cannot Communicate with Each Other?
Updated on 2025-07-22 GMT+08:00
What Should I Do If an ECS and a TaurusDB Instance Deployed in Different VPCs Cannot Communicate with Each Other?
When a TaurusDB instance and an ECS are deployed in different VPCs of the same region, they cannot communicate with each other through a private network. After a TaurusDB instance is created, you cannot change its VPC.
Solution
- Create a VPC peer connection.
- Change the VPC hosting the ECS to the same as that hosting the TaurusDB. For details, see Changing a VPC.
Parent topic: Database Connections
What is your overall rating for this page?
0
1
2
3
4
5
6
7
8
9
10
Very dissatisfiedVery satisfied
Thank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
