You can configure existing instances to use a private pool to increase the capacity usage of the private pool. You can also configure existing instances not to use a private pool so that the private pool can be used to create instances.
Background information
Some examples on how to work with private pools:
Assume that you have used a private pool to create instances and want to create more instances when resources are strained. You can configure the created instances not to use the private pool and then use the private pool to create new instances.
Assume that you do not want to use the private pool associated with a purchased capacity reservation to create instances but you want to use the private pool for existing instances. You can configure the existing instances to use the private pool. This helps improve resource utilization and reduce cost wastes.
Assume that you want to release existing instances to create new ones and want to purchase a capacity reservation to reserve resources. Your request to purchase a capacity reservation is rejected due to insufficient resources. You can set the private pool type to open for your existing instances so that the instances are deemed as matchable resources. Then, you can purchase a capacity reservation.
Procedure
You can configure a private pool only for pay-as-you-go instances.
Go to ECS console - Instance.
In the top navigation bar, select the region and resource group of the resource that you want to manage.
Click the ID of a pay-as-you-go instance. On the Instance Details tab, click All Actions in the upper-right corner. In the panel that appears, search for and click .
In the Configure Private Pool dialog box, configure whether to use a private pool and which private pool to use.
Manually specify a private pool ID: Set Private Pool Type to Target, and specify the ID of a dedicated or open private pool. This ID corresponds to an elastic assurance or a immediate capacity reservation.
Manually attach tags to match an open private pool: Set Private Pool Type to Open. Attach tags to the instance that match the tags of an elastic assurance or a capacity reservation. This allows the instance to use the corresponding open private pool. If an instance already matches an open private pool by tag and you need to trigger a rematch Modify the tags of an instance, enable economical mode for the instance, or stop and then start it. Simply restarting the instance does not trigger a rematch.
NoteIf you specify the ID of an open private pool and attach tags to the instance at the same time, the open private pool with the specified ID is used. For example, if you specify the ID of open private pool A and also attach tags that match open private pool B, open private pool A is used.
Automatically select an open private pool: Set Private Pool Type to Open. The system then automatically selects an untagged open private pool.
Do not use a private pool: Set Private Pool Type to None. No private pools are used, and only the public pool is used.
ImportantInstances can be removed from a private pool in the following two scenarios. If the system has insufficient inventory to replenish the pool, the pool's capacity is reduced. Perform these operations with caution.
Scenario 1: Change the pattern from Target to Open.
Scenario 2: Change the pattern from Target or Open to None.
Click OK.
What to do next
After you configure a private pool for an existing instance, you can check whether and which instances are associated with the private pool on the Private Pools tab. For more information, see View a private pool.