Checks whether each elastic IP address (EIP) is associated with an Elastic Compute Service (ECS) instance or a NAT gateway.
Scenarios
This rule can be used to check whether an EIP is not associated with an ECS instance or a NAT gateway. This helps you prevent unnecessary costs generated by idle resources.
Risk level
Default risk level: low.
You can change the risk level as required when you apply this rule.
Compliance evaluation logic
- If each EIP is associated with an ECS instance or a NAT gateway, the evaluation result is compliant.
- If one or more EIPs are not associated with ECS instances or NAT gateways, the evaluation result is non-compliant. For more information about how to correct the non-compliant configuration, see Non-compliance remediation.
Rule details
| Item | Description |
| Rule name | eip-attached |
| Rule ID | eip-attached |
| Tag | ECS and Instance |
| Automatic remediation | Not supported |
| Trigger type | Configuration change |
| Supported resource type | EIP |
| Input parameter | None |
Non-compliance remediation
- For more information about how to release an idle EIP, see Release a pay-as-you-go EIP.
- For more information about how to associate an EIP with an ECS instance or a NAT gateway, see Associate EIPs with and disassociate EIPs from cloud resources.