Scenario 4: Accessing an ECS in the Same VPC from CAE Components

Scenario

In a VPC, CAE components (such as service components and data processing components) can access ECSs and their deployed resources, such as databases, file storage, and middleware services, using private IP addresses. No public network link is required.

This section describes how the CAE components access the ECS in the same VPC.

Restrictions

This function is available only in CN North-Beijing4, CN South-Guangzhou, CN East-Shanghai1, ME-Riyadh, TR-Istanbul, AF-Johannesburg, LA-Mexico City2, and LA-Sao Paulo1.

Prerequisites

You have created a component. You have created a component, cae-test.
You have purchased an ECS, and the VPC bound to the ECS must be the same as the VPC to which the CAE environment belongs. For details about how to purchase an ECS, see Introducing ECS Purchase Options.

Step 1: Obtain the Private IP Address of the ECS

Log in to the ECS console.
Find a running ECS. The VPC bound to the ECS must be the same as the VPC to which the CAE environment belongs. Copy the private IP address of the ECS. The example value in this practice is 172.16.xx.xx.

Step 2: Accessing the ECS Using CloudShell

Choose Instance List.
On the Component Configurations page, select the target component cae-test from the drop-down list in the upper part of the page.
Click Remote Login on the right of any instance, select /bin/sh, and click Confirm.
Run the following command to access the private IP address of the ECS:
```
curl -kv 172.16.xx.xx  # Initiate a network request.
```
Press Enter to access the ECS.