You can create endpoint nodes within the VPC to facilitate access to ZOS from cloud servers within the same resource pool on the intranet. Cloud servers and ZOS are interconnected within the intranet, where access does not incur Internet traffic fees and ensures low latency and high security.

Advantages:

When cloud servers and ZOS are located within the same region or availability zone, network communications between them are conducted on the intranet by default. The advantages of intranet communications include:

• Low latency: Intranet communications eliminate the need for relay nodes necessary for data transfer over the Internet, ensuring low latency and rapid transfer speeds.

• High security: Intranet communications bypass the Internet, ensuring that data is physically protected within the network, minimizing the risks of malicious attacks and unauthorized access. This is essential for processing sensitive data and applications having high security requirements.

• Reduced costs: Intranet communications eliminate the need for Internet traffic fees associated with data transfer. This reduced costs, particularly in scenarios involving frequent transfer of large volumes of data within the intranet.

Before You Begin

• The cloud servers and ZOS reside in the same region or availability zone.

• The intranet access permissions of ZOS are properly configured, and the cloud servers can access ZOS using the intranet access address.

• The network configuration of the cloud server does not limit intranet communications. For example, there are no firewall rules or access control policies in place to restrict intranet access.

Notice for Use

• ZOS has been activated for the region.

• When accessing ZOS from the intranet, make sure that the cloud servers and ZOS reside in the same region.

Resource Pool Introduction

• The cloud servers in certain resource pools and ZOS are not interconnected through the intranet. To establish this connection, you can configure the VPC accordingly. In such cases, begin with the first step of the configuration process.

• By default, the resource pools where interconnection is established include Hong Kong 2 and Singapore 4. In these resource pools, cloud servers and ZOS are interconnected through the intranet. In such cases, no additional configurations are required. To confirm access to ZOS from a cloud server, proceed directly to step 3 in this topic.

Note:

You can use curl along with the intranet access address of ZOS on the cloud server to verify network connectivity.

Operation Steps

Step 1: Configuring the VPC and subnet

Before using a cloud server to access ZOS through the intranet, configure the VPC and subnet in the ZOS console.

On the homepage of the official eSurfing Cloud website, click Console , and enter your username and password to log in to the console.
In the upper part of the console, click , and select the desired resource pool node.
Choose Storage > Zettabyte Object Storage .
In the upper-right corner of the console, click Access Management (VPC) .
Click Create Endpoint . Select the VPC and subnet where the cloud server, intended to be interconnected with ZOS, resides, and finalize the configuration following the provided instructions.
Click Endpoint Management to view the configured VPC and subnet information.

Step 2: Restarting the cloud server NIC or the cloud server

Method 1: After configuring the VPC and subnet, you need to restart the cloud sever NIC or the cloud server for the ingress configuration to take effect.

For a Windows server, click the network icon in the lower-right corner, choose Network & Sharing Center > Change Adapter Options from the displayed menu, and disable and then enable the NIC that is in use.

For a Linux server, log in to the operating system and run the requisite command. For CentOS 7, run the command "systemctl restart network" to restart the NIC.

Method 2: Log in to the cloud server console, select the desired cloud server, and click the button to restart the server.

Step 3: Obtaining ZOS access information

Before using a cloud server to access ZOS, obtain the AccessKey (AK) and SecretKey (SK) for authentication, as well as the IP address.

Log in to the ZOS console, click the bucket name to access the bucket details, and obtain the information in the basic information section.

Step 4: Verifying network connectivity

To verify intranet connectivity for a Linux or Windows server, run the curl command followed by the ZOS intranet access IP address on the command line of the server. If the following information is returned, the connection is normal.

Note:

Ping commands are restricted within the intranet. Therefore, do not use ping statements to assess intranet connectivity.

Step 5: Logging in to the cloud server and accessing ZOS

Log in to the cloud server and install a client tool that is compatible with the S3 interface for accessing ZOS. This topic uses S3Browser in Windows as an example.

Download S3Browser from the official S3Browser website: https://s3browser.com. Then, install the tool by double-clicking the installation file and following provided instructions.
Configure the account for accessing ZOS. Open S3Browser, and choose Account > Add new account in the upper-left corner.
In the dialog box that appears, configure the account information.

Parameter	Description
Display name	Specify a custom name for account identification locally within the tool.
Account type	Select S3 Compatible Storage.
REST Endpoint	Enter the obtained IP address for accessing ZOS.
Access Key ID	Enter the obtained AccessKey for authentication when accessing ZOS.
Secret Key ID	Enter the obtained SecretKey for authentication when accessing ZOS.
Use secure transfer(SSL/TLS)	Do not select this item when using the IP address for intranet access. Select this item when using the IP address for Internet access.

After the parameters are set, click Add new account.
4. Create a bucket.
After the account is configured, click New Bucket in the upper-left corner of the tool to create a bucket.
5. Upload objects to the bucket.
In the upper-left dialog box, select the objects that you want to upload to the bucket, and click Upload.

Zettabyte Object Storage