If you encounter problems when you create and deploy applications in EDAS, refer to the solutions in this topic.
How to choose between an ECS cluster and a Kubernetes cluster
When you create an application, the first step is to select a cluster type. You can select a suitable cluster type based on the following criteria:
If you are unsure which cluster type to select, select an ECS cluster.
Cluster type | Deployment mode | O&M cost | Integration with cloud native |
ECS cluster | One application is deployed on a single ECS instance. | The O&M is similar to traditional Linux operations. It has a low entry barrier and is easy to manage. | N/A |
Kubernetes cluster | One application is deployed on a single pod. Multiple pods can run on a single ECS instance. | Requires a basic understanding of and experience with virtualization, container technology, and Kubernetes clusters. | Natively integrates with cloud native technologies. One image can run in multiple locations. |
Why are only instance types available in a custom environment?
Symptom
On the Application Configuration page, only instance types are available for selection. VPCs and specific ECS instances are not displayed.
Possible cause
This issue occurs because no Virtual Private Cloud (VPC), microservices namespace, cluster, or Elastic Compute Service (ECS) instance has been created for the current account in the current region. As a result, you only need to select an instance type. EDAS then creates a default VPC, an ECS instance of the specified type, a default microservices namespace, and a cluster for you.
Solution
If you have specific requirements for networking, service isolation, or ECS, first create the VPC, microservices namespace, cluster, and ECS instances. Then, you can select these resources on the page to deploy your application.
Cluster import fails
Symptom
On the Application Configuration page, select Custom. In the Instance section, select Use Existing Instances, and then select Instances Not Imported To A Cluster. When you create the application, an error message appears that indicates the instance failed to be imported into the cluster. For example:
Failed to import the instance into the cluster. Only ECS instances that run 64-bit Aliyun Linux 2.1903 (Recommended) or 64-bit CentOS 6.9/7.2/7.3/7.4/7.6 can be imported into a cluster. Ensure that the operating system of the ECS instance that you want to import is supported.
Possible cause
The operating system of the selected ECS instance is not supported by EDAS.
Solution
Select another ECS instance. The operating system of the instance must be 64-bit Aliyun Linux 2.1903 or 64-bit CentOS 6.9/7.2/7.3/7.4/7.6.
How to change the application port
For applications deployed in an ECS cluster, you can change the application port by modifying the Tomcat port in the application configuration on the application details page.
For applications deployed in a Kubernetes cluster, you can change the application port only by specifying it in the code or by attaching a Server Load Balancer (SLB) instance.