How do I choose between an ECS cluster and a Kubernetes cluster?
Start with an ECS cluster if you are unsure. It works like a conventional Linux system with minimal learning overhead.
Choose a Kubernetes (ACK) cluster if you need cloud-native integration, such as running a single image across multiple services and regions. This option requires hands-on experience with virtualization, containerization, and Kubernetes.
| ECS cluster | ACK cluster | |
|---|---|---|
| Choose this if | You want a familiar Linux-style environment with minimal setup | You need cloud-native integration across multiple services and regions |
| Deployment model | One application per ECS instance | One application per pod; multiple pods per ECS instance |
| IaaS billing | Based on ECS instance specifications. See Billing overview. | Based on the Container Service for Kubernetes (ACK) clusters in use. See Billing. |
| PaaS billing | Based on the ECS instances that run your applications. See Billing overview. | Based on the pods that run your applications. See Billing overview. |
| O&M complexity | Low. Similar to conventional Linux administration. | Higher. Requires basic knowledge and experience in virtualization, containerization, and Kubernetes. |
| Cloud-native integration | N/A | Kubernetes clusters can be integrated with cloud-native services. One image can run in multiple services and regions. |
Why does the custom environment only show instance specifications?
This happens when no VPC, microservices namespace, cluster, or ECS instance exists in the current region under the current account.
Select an instance specification and proceed. EDAS automatically creates a default VPC, a default microservices namespace and cluster, and an ECS instance with the specification you selected.
If you have specific requirements for network isolation, service isolation, and instance configuration, create a VPC, microservices namespace, cluster, and ECS instance first. These resources then appear in the Configurations step.
This applies when you select Custom Environment in the Configurations step and only instance specifications are displayed, without VPC or ECS instance information.
Why does adding an ECS instance to a cluster fail?
The ECS instance OS is not supported by EDAS. This error occurs when you select Custom Environment > Instance Source > Use Existing Instance > Instance not Imported to Any Cluster in the Configurations step.
Select an ECS instance that runs one of the following operating systems:
-
64-bit Alibaba Cloud Linux 2.1903
-
64-bit CentOS 7.2, 7.3, 7.4, or 7.6
How do I change an application port?
The method depends on the cluster type:
-
ECS cluster: Change the Tomcat port in the application settings on the application details page. If the new port does not take effect, see Why does the Tomcat port that I configured not take effect?.
-
Kubernetes cluster: Change the port only in the application code, or configure a Server Load Balancer (SLB) instance for the application.
Technical support
If you have questions when creating applications, join the official DingTalk group (group ID: 21958624) for technical support.