Updated on 2023-08-29 GMT+08:00

Preparing Required Resources

Overview

Before creating a DCS instance, prepare the required resources, including a VPC, a security group, security group rules, and a subnet. Each DCS instance is deployed in a VPC and bound to a specific subnet and security group, which provide an isolated virtual network environment and security protection policies which you can easily configure and manage.

If you already have a VPC, subnet, and security group, you can use them for all DCS instances you subsequently create.

Required Resources

The following table lists the resources required by a DCS instance.

Table 1 Dependency resources of a DCS instance

Resource

Requirement

Operations

VPC and subnet

Different DCS instances can use the same or different VPCs and subnets based on site requirements. Note the following when creating a VPC and subnet:

  • The VPC and the DCS instance must be in the same region.
  • Retain the default settings unless otherwise specified.

For details on how to create a VPC and subnet, see Creating a VPC. If you need to create and use a new subnet in an existing VPC, see Creating a Subnet for the VPC.

Security group

NOTE:

Security groups are required only by DCS Redis 3.0, 6.0 professional, and Memcached instances.

Different DCS instances can use the same security group or different security groups. Note the following when creating a security group:

  • Set Template to Custom.
  • After a security group is created, retain the default inbound and outbound rules.
  • To use DCS, you must add the security group rules described in Table 2. You can also add other rules based on site requirements.

For details on how to create a security group, see Creating a Security Group. For details on how to add rules to a security group, see Adding a Security Group Rule.

(Optional) EIP

NOTE:

EIPs are supported only by DCS Redis 3.0 instances.

If you want to access DCS through a public network, assign an EIP.

For details on how to assign an EIP, see Assigning an EIP.

Table 2 Security group rules

Direction

Protocol

Port

Source

Description

Inbound

TCP

36379

0.0.0.0/0

Access a DCS Redis 3.0 instance (with SSL encryption enabled) through a public network.

Inbound

TCP

6379

0.0.0.0/0

Access a DCS Redis 3.0 instance (with SSL encryption disabled) through a public network.

Inbound

TCP

6379

0.0.0.0/0

Access a DCS Redis 3.0 or 6.0 professional instance in a private network. (SSL encryption is not supported.)

Inbound

TCP

11211

0.0.0.0/0

Access a DCS Memcached instance.