Scaling configuration rules FAQ

Last Updated: Apr 23, 2018

What information should I provide for Auto Scaling troubleshooting?

When you open a ticket, we recommend that you provide your Auto Scaling activity ID (ScalingActivityId) and relevant logs to facilitate troubleshooting.

Can I add ECS instances that I have already created to a scaling group?

Yes. However, the ECS instances:

  • Must be in the same region of the scaling group. For more information, see Regions and zones.

  • Must be in the Running status. For more information, see ECS Instance life cycle.

  • Cannot exist in more than one scaling group.

Can I add existing subscription instances to scaling groups?

Yes, you can. Auto Scaling automatically creates Pay-As-You-Go or spot instances by default, and you can also add your existing Subscription or Pay-As-You-Go instances to a scaling group.

Can I add an ECS instance to more than one scaling group?

No, you cannot. This feature is not currently supported.

Can I create 8vCPU and 16vCPU ECS instances in a scaling group?

Yes, you can. Open a ticket to use more ECS instance types when you create ECS instances.

Is Auto Scaling vertical scalable?

No, it is not. Auto Scaling does not support automatically upgrade or downgrade the vCPU, memory, or bandwidth of an ECS instance.

Can I create periodic tasks in Auto Scaling?

Yes, you can. For more information, see Create a scheduled task.

When I remove an ECS instance from a scaling group and release the instance, can I save the ECS instance data?

No, you cannot. Therefore, do not establish application status information (for example, session) or related data (such as databases and logs) in an Auto Scaling ECS instances. We recommend that you save the status information to an independent state server (for example, ECS), database (for example, RDS), or standardized log storage (for example, Log Service).

If I disable a scaling group, are instances created by Auto Scaling released?

No. After you disable a scaling group (DisableScalingGroup), instances created by Auto Scaling are not automatically released.

Can I add different ECS instance types in an Auto Scaling groups?

No, you cannot. However, each scaling group can be set with a different configuration type.

Can I increase the maximum number of instances in the Auto Scaling service?

Yes, you can. The default maximum number of ECS instance in a scaling group is 1,000. Open a ticket for a higher instance quota.

Does Auto Scaling automatically include or exclude a new or removed ECS instances into or from the IP address whitelists of the configured RDS or Memcache?

Auto Scaling automatically includes a new or removed ECS instances into or from the IP address whitelists of a RDS. However, Memcache whitelists are not supported.

How can I make sure that manually added ECS instances are not removed from the scaling group?

  • For automatically created ECS instances, supposing that you want to retain the specified 100 ECS instances in a scaling group, and pay attention to the following when you Create a scaling configuration(CreateScalingConfiguration):

    • Set the minimum number of instances to greater than 100.

    • Set the first Removal Policy to The instances with the oldest configuration.

  • For manually created ECS instances, do not stop the specified ECS instance. Because the manually created and added ECS instances are not released if they are removed from a scaling group.

Note:Since manually added ECS instances were not created by a scaling group, therefore, Auto Scaling removes the automatically created ECS instances from the scaling group. Manually added ECS instances are removed only after all the automatically created ECS instances have been removed.

Thank you! We've received your feedback.