An elastic container instance includes infrastructure components such as vCPUs, memory, network, and storage. You can customize and change configurations of the elastic container instance in a quick manner. You have full control over the elastic container instance and do not need to manage or configure the underlying servers. You only need to provide the packaged container images to run the containers.
You can use multiple methods to create elastic container instances based on your business and usage scenarios. These methods correspond to different billing modes.
Specify the number of vCPUs and memory capacity
You are charged based on the specified vCPU and memory specifications. For vCPU and memory specifications that are not supported, the system adjusts the specifications and bills based on the new specifications.
You can specify the number of vCPUs and memory capacity for an elastic container instance or for containers in an elastic container instance.
Specify the number of vCPUs and memory capacity for containers in an elastic container instance
Specify the number of vCPUs and memory capacity for an elastic container instance
For more information, see Create an elastic container instance with the specified CPU and memory resources.
Specify the Elastic Compute Service (ECS) instance type
You are charged based on the specified ECS instance type. You can specify the ECS instance family to be used by the elastic container instance to grant its corresponding capabilities. For example, if you select the ecs.sn1ne instance family, the elastic container instance has the enhanced network capabilities that the instance family provides.
For more information, see the following topics:
You can use pay-as-you-go elastic container instances together with preemptible elastic container instances, reserved instances, and savings plans to reduce your costs based on your business needs.
Preemptible elastic container instances can be used for stateless and fault-tolerant business workloads. For more information, see Use preemptible instances.
For long-term stable business loads, we recommend that you use reserved instances or savings plans to offset the bills of elastic container instances. The following deduction methods are applied based on the billing modes of elastic container instances:
Elastic container instances billed based on vCPUs and memory
Only general-purpose savings plans are supported.
Elastic container instances billed based on ECS instance types
General-purpose savings plans, ECS compute savings plans, and reserved instances are supported.
Elastic Container Instance provides cloud resources for containers. When you create a large number of elastic container instances, some resources in the specified region and zone may be insufficient. We recommend that you specify multiple ECS instance types across multiple zones to ensure that the elastic container instances can be created. For more information, see the following topics:
If you do not connect Elastic Container Instance to Kubernetes clusters, you must manage the lifecycle of elastic container instances and process business loads based on the status of the elastic container instances to ensure business robustness and avoid resource waste. For more information, see Elastic container instance lifecycle.