An ECS Must Have No More Than One EIP
Rule Details
Parameter |
Description |
---|---|
Rule Name |
ecs-multiple-public-ip-check |
Identifier |
An ECS Must Have No More Than One EIP |
Description |
If an ECS instance has multiple EIPs attached, this instance is non-compliant. |
Tag |
ecs |
Trigger Type |
Configuration change |
Filter Type |
ecs.cloudservers |
Rule Parameters |
None |
Application Scenarios
You are advised not to bind multiple NICs to an ECS because of:
- Increased network complexity: Multiple NICs may cause route configuration difficult. Network conflicts and communication interruptions may occur. Multiple NICs also increase the difficulties in network management and troubleshooting.
- Performance issues: Multiple NICs require more system resources, such as CPU and memory, which may affect server performance. Improper bandwidth allocation may cause some NICs to be overloaded while others are idle.
- Security risks: Multiple NICs increase the potential attack surface and security risks. Complex network configurations are prone to errors, which may cause security vulnerabilities.
- Increased costs: Multiple NICs increase your cloud service expanses, especially when the resources are billed by traffic or bandwidth. Idle NICs cause unnecessary costs.
Solution
Check whether your services require multiple EIPs. If not, unbind EIPs.
Rule Logic
- If an ECS has two or more EIPs attached, the ECS is non-compliant.
- If an ECS has no EIP or only one EIP attached, the ECS is compliant.
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.
For any further questions, feel free to contact us through the chatbot.
Chatbot