Impact on IMS

To ensure that ECSs created using private images support customized configurations, you must install Cloud-Init or Cloudbase-Init before creating private images.

• For Windows OSs, download and install Cloudbase-Init.
• For Linux OSs, download and install Cloud-Init.

After Cloud-Init or Cloudbase-Init is installed in an image, Cloud-Init or Cloudbase-Init automatically configures initial ECS attributes when the ECS is created. For instructions about how to install Cloud-Init or Cloudbase-Init, see Image Management Service User Guide.

Impact on ECS

• When creating an ECS, if the selected image supports Cloud-Init, you can use user data injection to inject customized configuration, such as ECS login password, for initializing. For details, see section (Optional) Injecting User Data into ECSs.
• After Cloud-Init is supported, ECS login modes will be affected. For details, see the following sections:
  • Logging In to an ECS
  • What Is the cloudbase-init Account in Windows ECSs?
  • Why Was My Login to a Linux ECS with a Key File Unsuccessful?
  • Why Does the System Display a Message Indicating that the Password for Logging In to a Windows ECS Cannot Be Queried?
• After Cloud-Init is supported, you can view and use metadata to configure and manage running ECSs. For more information, see section Managing ECS Metadata.

Impact on AS

• When creating an AS configuration, you can use user data injection to specify ECS configurations for initialization. If the AS configuration has taken effect in an AS group, the ECSs newly created in the AS group will automatically initialize their configurations.
• For an existing AS configuration, if its private image has Cloud-Init or Cloudbase-Init not installed, the login mode of the ECSs created in the AS group where the AS configuration takes effect will be influenced. To resolve this issue, see section "How Does Cloud-Init Influence the AS Service?" in Auto Scaling User Guide.

For more information about AS, see Auto Scaling User Guide.

Notes

• When using Cloud-Init, enable DHCP in the VPC to which the ECS belongs.
• When using Cloud-Init, ensure that security group rules in the outbound direction meet the following requirements:
  • Protocol: TCP
  • Port Range: 80
  • Remote End: 169.254.0.0/16
  NOTE:

  If you use the default security group rules in the outbound direction, the preceding requirements are met, and the metadata can be accessed. Default security group rules in the outbound direction are as follows:

  • Protocol: ANY
  • Port Range: ANY
  • Remote End: 0.0.0.0/16