All Products
Search
Document Center

Elastic Compute Service:Overview

最終更新日:Mar 27, 2024

You can use deployment sets to deploy Elastic Compute Service (ECS) instances on different physical servers to ensure high availability of business on the instances and improve the disaster recovery capabilities of the underlying physical servers of the instances. Alternatively, you can deploy ECS instances in a centralized manner within the same network topology to reduce communication latency between the instances. This topic describes the definition, deployment strategies, limits, and configuration guide of deployment sets.

Deployment strategies

If you specify a deployment set when you create ECS instances, the instances are created and distributed based on the deployment strategy that you preset for the deployment set in the specified region.

Deployment sets support the following deployment strategies:

  • High availability strategy

    When you use the high availability strategy for a deployment set in a specified region, all ECS instances in the deployment set are distributed across different physical servers in the region. The high availability strategy applies to application architectures where ECS instances must be isolated from each other, and can significantly reduce the chances of service unavailability.

  • High availability group strategy

    When you use the high availability group strategy for a deployment set, the deployment set can be divided into up to seven deployment set groups. You can distribute multiple ECS instances in a deployment set to different deployment set groups based on your business requirements. ECS instances in different deployment set groups are strictly distributed to different physical servers. ECS instances in the same deployment set group may not be strictly distributed to different physical servers.

  • Low latency strategy

    • If you use the low latency strategy for a deployment set, ECS instances in the deployment set that reside in a zone are deployed to the same network topology in the zone to reduce network latency. In this case, multiple ECS instances may be scheduled to the same physical server, and high availability cannot be ensured.

    • You can call the DescribeDeploymentSetSupportedInstanceTypeFamily operation and set Strategy to LowLatency to query the ECS instance families that support the low latency strategy.

Important

If a supply shortage occurs in a specified region, you may be unable to create ECS instances or start pay-as-you-go instances that were stopped in economical mode in that region. In these cases, we recommend that you wait a while and then try again.

Deployment example

The following figure shows a typical example on how to use a deployment set to improve business reliability. In the deployment set, four ECS instances are distributed to four different physical servers.部署集概述

To maintain low communication latency between ECS instances in a deployment set, we recommend that you keep the network types of the instances the same. For example, you can select the same virtual private cloud (VPC) for the ECS instances when you create the instances.

Billing

You can use deployment sets free of charge. However, you are charged for the usage of resources, such as ECS instances, disks, snapshots, images, and public bandwidth, in deployment sets. For more information, see Billing overview.

Limits

Before you use deployment sets, take note of the following items:

  • Deployment sets cannot be merged.

  • Preemptible instances cannot be created in deployment sets.

  • Dedicated hosts cannot be created in deployment sets.

  • The number of ECS instances that can be created in a deployment set varies based on the deployment strategy that is adopted by the deployment set.

    • High availability strategy: In a deployment set that adopts the high availability strategy, you can create up to 20 ECS instances per zone. You can use the following formula to calculate the maximum number of ECS instances that you can create in a deployment set within a region: 20 × Number of zones within the region.

    • High availability group strategy: In a deployment set that adopts the high availability group strategy, you can create up to 7 deployment set groups per zone and up to 20 ECS instances per deployment set group. You can use the following formula to calculate the maximum number of ECS instances that you can create in a deployment set within a region: 7 × 20 × Number of zones within the region.

    • Low latency strategy: In a deployment set that adopts the low latency strategy, you can create ECS instances only in a single zone. Up to 20 ECS instances can be created in the zone.

  • Instances of the following instance families can be created in deployment sets:

    Note

    Some instance families support only specific deployment set strategies. You can call the DescribeDeploymentSetSupportedInstanceTypeFamily operation to query the instance families that support different deployment strategies.

    Deployment strategy

    Instance families that support the deployment strategy

    High availability strategy or high availability group strategy

    • g8i, g8y, g7se, g7a, g7, g7t, g7ne, g7nex, g6, g6e, g6a, g5, g5ne, sn2ne, sn2, and sn1

    • c8i, c8y, c7se, c7, c7t, c7nex, c7a, c6, c6a, c6e, c5, ic5, and sn1ne

    • r8y, r7, r7se, r7t, r7a, r6, r6e, r6a, re6, re6p, r5, re4, se1ne, and se1

    • hfc7, hfg7, hfr7, hfc6, hfg6, hfr6, hfc5, and hfg5

    • d3c, d2s, d2c, d1, d1ne, d1-c14d3, and d1-c8d3

    • i3g, i3, i2, i2g, i2ne, i2gne, and i1

    • ebmg5, ebmc7, ebmg7, ebmr7, sccgn6, scch5, scch5s, sccg5, and sccg5s

    • e, t6, xn4, mn4, n4, e4, n2, and n1

    • gn6i

    Low latency strategy

    • g8a, g8i, g8ae, and g8y

    • c8a, c8i, c8ae, and c8y

    • r8a, r8i, r8ae, and r8y

    • ebmc7, ebmg7, and ebmr7

  • Supply shortage may result in a failure to create ECS instances or start pay-as-you-go instances that were stopped in economical mode in a deployment set. For more information, see Economical mode.

For more information about the limits and quotas of deployment sets, see the Deployment set limits section in the "Limits" topic.

Configuration guide

Scenario

Operation in the ECS console

API operation

Create a deployment set

Create a deployment set

CreateDeploymentSet

Create an ECS instance in a deployment set

Create an ECS instance in a deployment set

RunInstances

Add an ECS instance to a deployment set or move an ECS instance from one deployment set to another deployment set.

Change the deployment set of an instance

ModifyInstanceDeployment

Change the name or description of a deployment set

Modify a deployment set

ModifyDeploymentSetAttribute

Delete a deployment set

Delete a deployment set

DeleteDeploymentSet