Help Center > > FAQs> Network Connection> Do DCS Instances Support Cross-VPC Access (When the Client and the DCS Redis or Memcached Instance Are in Different VPCs)?

Do DCS Instances Support Cross-VPC Access (When the Client and the DCS Redis or Memcached Instance Are in Different VPCs)?

Updated at: Apr 01, 2019 GMT+08:00

The following assumes that public access is disabled for DCS instances. Generally, VPCs are isolated from each other and ECSs cannot access DCS instances that belong to a different VPC from these ECSs.

However, by establishing VPC peering connections between VPCs, ECSs can access single-node and master/standby DCS instances across VPCs.

When using VPC peering connections to access DCS instances across VPCs, adhere to the following rules:

Table 1

Network Segment of DCS Instances

Network Segments Not Allowed for Clients

172.16.0.0/12 to 172.16.0.0/24

192.168.1.0/24

192.168.2.0/24

192.168.3.0/24

192.168.0.0/16 to 192.168.0.0/24

10.0.0.0/8 to 10.0.0.0/24

172.31.1.0/24

172.31.2.0/24

172.31.3.0/24

For more information on how to create and use VPC peering connections, see VPC Peering Connection.

Cluster DCS Redis instances do not support cross-VPC access. For example, ECSs in a VPC cannot access cluster DCS instances in another VPC by using VPC peering connections.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel