Help Center/
Well-Architected Framework/
Well-Architected Framework and Practices/
Resilience Pillar/
HA Design/
RES01 Redundancy/
RES01-03 Anti-Affinity for Cloud Servers
Updated on 2025-05-22 GMT+08:00
RES01-03 Anti-Affinity for Cloud Servers
ECSs that run the same service in an application must be deployed on different physical servers to prevent service interruptions caused by a physical server fault.
- Risk level
High
- Key strategies
- For multiple ECSs that bear the same service, anti-affinity needs to be configured for the group housing these ECSs so that they can be scheduled to different physical servers. This prevents all services from being unavailable due to the fault of a single physical server.
- If ECSs are automatically scaled using Auto Scaling (AS), anti-affinity needs to be configured for the ECS group. This prevents the ECSs automatically scaled using AS from running on the same physical server.
- If CCE cluster nodes or node pools use ECSs, you are advised to configure anti-affinity for the ECS group to prevent ECS nodes in the CCE cluster from running on the same physical server.
- Related cloud services and tools
- Elastic Cloud Server (ECS): ECS group
- Auto Scaling (AS)
- Cloud Container Engine (CCE)
Parent topic: RES01 Redundancy
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot