Resource Orchestration Service:Deploy a Node.js development and test environment

What is Node.js

Resources to be created

Results obtained after deployment

After the template runs successfully, you get the following:

• A complete VPC network environment (VPC + vSwitch + security group).

• An ECS instance that runs CentOS 7 and is assigned a public IP address.

• The Node.js runtime and the npm package manager installed on the ECS instance.

• A Node.js test application that runs on the ECS instance so that you can verify the environment.

• The stack outputs provide the URL of the test page (WebsiteURL).

Method 1: Deploy with the ROS public template (recommended)

1. Log in to the ROS console.

2. In the left-side navigation pane, choose Templates > Public Templates.

3. Use the template keyword search box to find and select the public template Deploy a Node.js development and test environment.

4. On the template details page, click Create Stack.

5. On the Configure Parameters page, enter a Stack Name and configure the template parameters.

   Note

   You can change Nodejs URL to the URL of the latest LTS version.

6. After you configure the parameters, click Next: Check and Confirm, verify the configuration, and then click Create.

7. View the creation progress on the stack details page. When the stack status changes to CREATE_COMPLETE, all resources are created.

8. Click the Output tab to get the WebsiteURL.

9. Open the URL in a browser. If the Node.js test page appears, the deployment is successful.

Method 2: Deploy with ROS IaC Code

IaC Code is an AI infrastructure-as-code assistant for cloud infrastructure. It generates an ROS template from a natural language description and deploys the template. For instructions, see the IaC Code quick start.

Help me create an ECS instance and deploy a Node.js development and test environment.
Requirements:
1. Create a new VPC and vSwitch as the base network.
2. In the security group, allow inbound ports 3000 and 8080 (for the Node.js application) and port 22 (for SSH).
3. Use a CentOS 7 image for the ECS instance and assign a public IP address.
4. Use a UserData script to automatically install the Node.js v20 LTS version.
5. Configure the NODE_HOME environment variable and create global symbolic links for node, npm, and npx.
6. Create a Hello World test application and start it in the background.
7. Configure AssociationProperty for ZoneId and InstanceType for dynamic filtering.
8. Have the stack output the URL of the Node.js test page.

The deployment fails with the error "The specified InstanceType is not available"

Cause: The selected ECS instance type is out of stock in the specified zone.

Solutions:

• Change the zone and deploy the stack again.

• Check the available instance types for the target zone on the Elastic Compute Service (ECS) pricing page.

• A Node.js development and test environment consumes little memory, so an instance type with 1 vCPU and 1 GiB of memory is sufficient for basic development and testing.

The deployment succeeds, but the test page is inaccessible

Troubleshooting steps:

1. Check the security group: Make sure that the inbound rules of the security group allow the port that the application listens on, such as 8080 or 3000.

2. Log on to the ECS instance and check whether the Node.js process is running:

   ps -ef | grep node                  # View the Node.js process
   netstat -tlnp | grep 8080           # Confirm that the port is listening

3. If the process is not running, start it manually to view the error:

   cd /opt/nodeapp
   node app.js

4. View the UserData execution log:

   cat /var/log/messages | grep cloud-init